Skip to content

Latest commit

 

History

History
272 lines (221 loc) · 10.2 KB

CONTRIBUTING.md

File metadata and controls

272 lines (221 loc) · 10.2 KB

Contributing Guidelines

This documentation contains a set of guidelines to help you during the contribution process.
We are happy to welcome all the contributions from anyone willing to improve/add new projects (doesn't matter which language) to this Repository.

# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
  overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or
  advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
  address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Enforcement Responsibilities

Project maintainers are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Project maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
[email protected].
All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.


## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.

Before contributing please ensure your pull request adheres to the following guidelines:

STEP-0 : Key Points to remember :

  • Look at the previous work and get some idea from them Previous
  • Suppose you want to contribute your work to one particular domain then first check is there any works exits with the same language or not.
  • If Yes, that your work is already exits with the same programming language and if your solution is different technique then add your solution with same name but change question number like _01)_Reverse.py already present then you should write _01)_1_Reverse.py and your solution technique alredy present then don't put your solution.
  • If there is no such work then make sure you enter your particular domain and create one folder and folder name should be your domain name .
  • Please don't add any License under your work. This repo already under MIT License.

STEP-1 : Flow :

Tree of Index

.
├── ...
├── 𝑴𝒊𝒔𝒄𝒆𝒍𝒍𝒂𝒏𝒆𝒐𝒖𝒔 𝑺𝒕𝒖𝒇𝒇
|   ├── Aptitude & Reasoning              
|   |   └── ...
|   |
|   ├── Basic Programming MCQs
|   |   └── ...
|   |
|   ├── Puzzles
|   |   └── ...
|   |
|   └── ...
|
|
└── 𝑫𝑺𝑨
|   ├── Data Structures              
|   |   └── ...
|   |
|   ├── Algorithms
|   |   └── ...
|   |
|   ├── 450 DSA by @Love Babbar
|   |   └── ...
|   |
|   ├── FAANG Interview Questions
|   |   ├── Facebook
|   |   ├── Amazon
|   |   ├── Apple
|   |   ├── Netflix
|   |   ├── Google
|   |   ├── Others
|   |   └── ...
|   |
|   └── ...
|
|
└── 𝑪𝒐𝒎𝒑𝒆𝒕𝒊𝒕𝒊𝒗𝒆 𝑷𝒓𝒐𝒈𝒓𝒂𝒎𝒎𝒊𝒏𝒈
|   ├── HackerRank              
|   |   └── ...
|   |
|   ├── GeeksforGeeks
|   |   └── ...
|   |
|   ├── HackerEarth
|   |   └── ...
|   |
|   ├── CodeChef              
|   |   └── ...
|   |
|   ├── CodeForce
|   |   └── ...
|   |
|   ├── LeetCode
|   |   └── ...
|   |
|   ├── InterviewBit
|   |   └── ...
|   |
|   └── ...
|
|
└── 𝑻𝒆𝒄𝒉𝒏𝒊𝒄𝒂𝒍 𝑺𝒖𝒃𝒋𝒆𝒄𝒕
|   ├── Object Oriented Programming (OOPs)              
|   |   └── ...
|   |
|   ├── Operating System (OS)
|   |   └── ...
|   |
|   ├── Database Management System (DBMS)
|   |   └── ...
|   |
|   ├── Structured Query Language (SQL)              
|   |   └── ...
|   |
|   ├── Computer Network (CN)
|   |   └── ...
|   |
|   ├── Interview Questions
|   |   └── ...
|   |
|   └── ...
|
|
└── 𝑳𝒐𝒘 𝑳𝒆𝒗𝒆𝒍 𝑫𝒆𝒔𝒊𝒈𝒏   
   └── ...
|
|
└── 𝑷𝒓𝒐𝒋𝒆𝒄𝒕
|   ├── Machine Learning & Data Science              
|   |   └── ...
|   |
|   ├── Internet of Things (IoT)
|   |   └── ...
|   |
|   ├── Web Development
|   |   └── ...
|   |
|   ├── Mobile Development              
|   |   └── ...
|   |
|   └── ...
└── ...

STEP-2 : Contributing

We'd love your contributions! Kindly follow the steps below to get started:

  1. Star this repository.

  2. Fork this repository.

  3. Clone the forked repository.

git clone https://github.com/<your-github-username>/The-Complete-FAANG-Preparation 
  1. Navigate to the project directory.
cd The-Complete-FAANG-Preparation
  1. Create a new branch.
git checkout -b <your_branch_name>
  1. Make changes.

  2. Stage your changes and commit

git add -A

git commit -m "<your_commit_message>"
  1. Push your local commits to the remote repo.
git push -u origin <your_branch_name>
  1. Create a Pull-Request to develop !

  2. Congratulations! 🎉 Sit and relax, you've made your contribution to The Complete FAANG Preparation. ✌️ ❤️ 💥

Note :

  • New categories, or improvements to the existing categorisation, are always welcome.
  • If you have any idea or suggestions then check this Discussion Tab. and put your idea or suggestions🏆

Discussion Tab

Need more help?🤔

You can refer to the following articles on basics of Git and Github and also contact the Project Admin, in case you are stuck: