Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-11-01 14:45:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
d81e0107b7
gecko-dev/servo/CONTRIBUTING.md
Josh Matthews 528137b9d7 servo: Link to instructions that don't mention critic. 
Source-Repo: https://github.com/servo/servo
Source-Revision: 9b939546a660fb24985e54aba1c2c47d1cf057a4
2015-09-18 11:48:21 -04:00

1.8 KiB
Raw Blame History

Contributing to Servo

Servo welcomes contribution from everyone. Here are the guidelines if you are thinking of helping us:

Contributions

Contributions to Servo or its dependencies should be made in the form of GitHub pull requests. Each pull request will be reviewed by a core contributor (someone with permission to land patches) and either landed in the main tree or given feedback for changes that would be required. All contributions should follow this format, even those from core contributors.

If you're looking for easy bugs, have a look at the E-Easy issue tag on GitHub.

Pull Request Checklist

  • Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes.

  • Don't put submodule updates in your pull request unless they are to landed commits.

  • If your patch is not getting reviewed or you need a specific person to review it, you can @-reply a reviewer asking for a review in the pull request or a comment, or you can ask for a review in #servo on irc.mozilla.org.

  • Add tests relevant to the fixed bug or new feature. For a DOM change this will usually be a web platform test; for layout, a reftest. See our testing guide for more information.

For specific git instructions, see GitHub workflow 101.

Conduct

We follow the Rust Code of Conduct.

Communication

Servo contributors frequent the #servo channel on irc.mozilla.org.

You can also join the dev-servo mailing list.