Skip to content

Latest commit

 

History

History
112 lines (80 loc) · 6.44 KB

CONTRIBUTING.md

File metadata and controls

112 lines (80 loc) · 6.44 KB
Raw

🎇Contributing Guidelines

This documentation contains a set of guidelines to help you during the contribution process.

I'm happy to welcome all the contributions from anyone willing to add new scripts to this repository. Thank you for helping out and remember, no contribution is too small.

💻Before Contributing

Welcome to neha07kumari/Thief_Detection. Before sending your pull requests, make sure that you read the whole guidelines. If you have any doubt on the contributing guide, please feel free to reach out.

🙌Contribution

Any contribution is accepted, from minor changes to implementing complex scripts. Please read this section if you are contributing your work.

🔖Steps to Contribute

Following are the steps to guide you:

  • Step 1: Fork the repo and Go to your Git terminal and clone it on your machine.
  • Step 2: Add a upstream link to main branch in your cloned repo 
    git remote add upstream https://github.com/neha07kumari/Thief_Detection.git
  • Step 3: Keep your cloned repo upto date by pulling from upstream (this will also avoid any merge conflicts while committing new changes) 
    git pull upstream main https://github.com/neha07kumari/Thief_Detection.git
  • Step 4: Create your feature branch (This is a necessary step, so don't skip it) 
    git checkout -b <feature-name>
  • Step 5: Commit all the changes (Write commit message as "Small Message") 
    git commit -m "Write a meaningfull but small commit message"
  • Step 6: Push the changes for review 
    git push origin <branch-name>
  • Step 7: Create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)

🔨Note:

  • Do not edit/delete someone else's script in this repository. You can only insert new scripts in this repository.
  • Give a meaningful name to whatever file or folder you are adding.
  • To state an example, folder name should be as "Images" and file name should be "front_image.jpg"

🔑Guidelines

  1. Welcome to this repository, if you are here as open source program participant/contributor.
  2. Participants / contributors have to comment on issues they would like to work on, and mentors or the PA will assign you.
  3. Issues will be assigned on a first-come, first-serve basis.
  4. A form will be provided where in you can add out your issues you like to work on with respect to this project. If the issue seems relevant and worth adding, an issue would be created with a link for you to claim an issue by expressing your interest over it with a pointed description on how would you implement.
  5. Participants / Contributors are not allowed to open their issues as it needs to be verified and labelled by a mentor or PA. Please discuss your issues with the team once before you add it up in the form or before working.
  6. Work on the issues after it gets assigned to you. Without issue assignment, PR won't be counted.
  7. Each participant / contributor will be assigned 1 issue (max) at a time to work.
  8. Participants are expected to follow project guidelines and coding style. Structured code is one of our top priority.
  9. Try to explain your approach to solve any issue in the comments. This will increase the chances of you being assigned.
  10. Please don't pick up an issue already assigned to someone else.
  11. Pull requests will be merged after being reviewed by a mentor and PA.
  12. It might take a day or two to review your pull request. Please have patience and be nice.
  13. Participants / contributors have to complete issues before the decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to another person in the queue.
  14. While making PRs, use the PR template and don't forget to add a description of your work.
  15. Include issue number (Fixes:issuenumber) in your commit message while creating a pull request.
  16. Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
  17. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.

🧲Pull Requests Review Criteria

  1. Please fill the PR Template properly while making a Pull Request.
  2. You must add your script into the respective places.
  3. Your work must be original, written by you not copied from other resources.
  4. Follow the proper style guides for your work.
  5. For any queries or discussions, please feel free to join and drop a message over Discord channel.
  6. Do not update the README.md and CONTRIBUTING.md.

📖Resources

  1. Markdown : Markdown is a lightweight markup language like HTML, with plain text formatting syntax.
  1. Git : Git is a distributed version-control system for tracking changes in source code during software development. It is designed for coordinating work among programmers, but it can be used to track changes in any set of files.

🤔Need more help?

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

😇Tip from me

It always takes time to understand and learn. So, do not worry at all. I know you can do this**!💪