From bde4087c5e4cd3fd41d0c994269b31f5dc3d6ce2 Mon Sep 17 00:00:00 2001 From: gracjan Date: Sun, 25 Jan 2015 14:20:07 +0100 Subject: [PATCH] Update link to bors --- Note-development-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Note-development-policy.md b/Note-development-policy.md index ed4eee5..5c9222a 100644 --- a/Note-development-policy.md +++ b/Note-development-policy.md @@ -2,7 +2,7 @@ Development policy for Rust. ## Contributions and commit access -We request that contributions are made via pull request and review. Note that **all patches from all contributors get reviewed**. After a pull request is made other contributors will offer feedback, and if the patch passes review someone with official review privileges will accept it with an "r+" comment. Upon successful review, pull requests are tested and merged automatically by our integration bot, [bors](http://buildbot.rust-lang.org/bors/bors.html). When pull requests fail integration testing authors are expected to update their pull requests to address the failures until the tests pass and the pull request merges successfully. +We request that contributions are made via pull request and review. Note that **all patches from all contributors get reviewed**. After a pull request is made other contributors will offer feedback, and if the patch passes review someone with official review privileges will accept it with an "r+" comment. Upon successful review, pull requests are tested and merged automatically by our integration bot, [bors](http://buildbot.rust-lang.org/homu/queue/rust). When pull requests fail integration testing authors are expected to update their pull requests to address the failures until the tests pass and the pull request merges successfully. Those with review privileges or direct push access are required to [file a Mozilla "committer agreement"](https://www.mozilla.org/hacking/notification/). This is a short (1-page) legal agreement that asserts certain claims of originality, absence of conflict with other agreements, and similar terms associated with licensing and authorization. If you already have Level 1 or higher commit rights within the Mozilla project, you have already filled out such a form. **Committer agreements are generally only required for reviewers and those with direct push access to the master repository**, though we will occasionally also request agreements for large, non-trivial contributions. If you would like to be a reviewer then please discuss it with one of the [core contributors](Note-core-team) through IRC or email.