Create a guide for contributing about hydrus

[nityanandagohain]

can I work on this

[Mec-iS]

https://github.com/mapbox/mercantile/blob/master/CODE_OF_CONDUCT.md

Check Contributor Covenant for reference.

[Mec-iS]

@nityanandagohain These could be two different documents:

• CODE_OF_CONDUCT.md
• CONTRIBUTING.md

[nityanandagohain]

@Mec-iS there is already a code of conduct https://github.com/HTTP-APIs/hydrus/blob/master/.github/CODE_OF_CONDUCT.md

[chrizandr]

I would actually prefer that everyone contributes to the guidelines here and we discuss it before someone starts working on it.

[nityanandagohain]

This is what I have managed till now

Contribution Best Practices

Feature Requests and Bug Reports

• Some newcomers are not accustomed to issue trackers and might try to inform developers on the mailing list, chat or even write private emails about bugs and features, but the right place to do this is: The issue tracker of a project.

• Any bug or feature, please open an issue in the issue tracker right away and indicate if you want to work on it yourself.

• Please include all relevant information when you submit an issue and wherever possible a link, information about the code that has issues and a screenshot.

• When you file a bug report on the issue tracker, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.

Branching

• Always work on a newbranch, never work on the master branch.

• Always keep your branch updated. There are many people who contribute to a repository.

Commits

• Write clear meaningful git commit messages. (How to Write a Git Commit Message)

• Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (Closing Issues via Pull Requests)

Pull Request

• Always send pull request to upstream/develop branch and not to the master branch.
• Write a good pull request (Perfect Pull Request)

[nityanandagohain]

@Mec-iS should i combine "points people need to keep in mind while adding bugs or patches to the repository."
and code of conduct . Because @chrizandr stated about that the quoted line. help me out