We welcome contribution from everyone. Here are the guidelines if you are thinking of helping us:
Contributions to JobScheduler should be made in the form of GitHub pull requests. Each pull request will be reviewed and either landed in the main tree or given feedback for changes that would be required. All contributions should follow this format.
Should you wish to work on an issue, please claim it first by commenting on the GitHub issue that you want to work on it. This is to prevent duplicated efforts from contributors on the same issue.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in JobScheduler by you, as defined in the Apache-2.0 license, shall be dual licensed as MIT/Apache-2.0, without any additional terms or conditions.
-
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.
-
Commits should be as small as possible, while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).
-
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.
-
Add tests relevant to the fixed bug or new feature.
We follow the Rust Code of Conduct. For escalation or moderation issues, please contact Lori (git at loriholden dot com) instead of the Rust moderation team.
Beyond opening tickets on the
job_scheduler project, I can be
found as lholden on irc.mozilla.org and I
frequent the #rust channel.