| 1 |
# Contributing |
| 2 |
|
| 3 |
Contributions are very much welcome. Here are the guidelines if you are thinking of helping us: |
| 4 |
|
| 5 |
## Contributions |
| 6 |
|
| 7 |
Contributions should be made in the form of GitHub pull requests. |
| 8 |
Each pull request will be reviewed by a core contributor (someone with |
| 9 |
permission to land patches) and either landed in the main tree or |
| 10 |
given feedback for changes that would be required. |
| 11 |
|
| 12 |
Should you wish to work on an issue, please claim it first by commenting on |
| 13 |
the GitHub issue that you want to work on it. This is to prevent duplicated |
| 14 |
efforts from contributors on the same issue. |
| 15 |
|
| 16 |
## Pull Request Checklist |
| 17 |
|
| 18 |
- Branch from the master branch and, if needed, rebase to the current master |
| 19 |
branch before submitting your pull request. If it doesn't merge cleanly with |
| 20 |
master you may be asked to rebase your changes. |
| 21 |
|
| 22 |
- Commits should be as small as possible, while ensuring that each commit is |
| 23 |
correct independently (i.e., each commit should compile and pass tests). |
| 24 |
|
| 25 |
- If your patch is not getting reviewed or you need a specific person to review |
| 26 |
it, you can @-reply a reviewer asking for a review in the pull request or a |
| 27 |
comment. |
| 28 |
|
| 29 |
- Whenever applicable, add tests relevant to the fixed bug or new feature. |
| 30 |
|
| 31 |
For specific git instructions, see [GitHub workflow 101](https://github.com/servo/servo/wiki/Github-workflow). |
| 32 |
|
| 33 |
## Conduct |
| 34 |
|
| 35 |
We follow the [Rust Code of Conduct](http://www.rust-lang.org/conduct.html). |
| 36 |
For escalation or moderation issues, please contact Nical ([email protected]) instead of the Rust moderation team. |
| 37 |
|
| 38 |
## License |
| 39 |
|
| 40 |
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed dual MIT/Apache 2, without any additional terms or conditions. |