Repository: aurora Updated Branches: refs/heads/master 68c422551 -> 47c5f4d19
Clarifying documentation for new contributors by adding a step for them to ask for their JIRA id to get whitelisted. Due to spam bots, JIRA accounts need to be whitelisted before they can self-assign tasks. Reviewed at https://reviews.apache.org/r/52049/ Project: http://git-wip-us.apache.org/repos/asf/aurora/repo Commit: http://git-wip-us.apache.org/repos/asf/aurora/commit/47c5f4d1 Tree: http://git-wip-us.apache.org/repos/asf/aurora/tree/47c5f4d1 Diff: http://git-wip-us.apache.org/repos/asf/aurora/diff/47c5f4d1 Branch: refs/heads/master Commit: 47c5f4d19af7e944bcff63855b80d8bf0702d2b2 Parents: 68c4225 Author: Dmitriy Shirchenko <cald...@gmail.com> Authored: Mon Sep 19 14:13:25 2016 -0500 Committer: Joshua Cohen <jco...@apache.org> Committed: Mon Sep 19 14:15:41 2016 -0500 ---------------------------------------------------------------------- CONTRIBUTING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/aurora/blob/47c5f4d1/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 13ebbe4..1d6baa4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -16,8 +16,10 @@ both languages. There are issues in [Jira](https://issues.apache.org/jira/browse/AURORA) with the ["newbie" label](https://issues.apache.org/jira/issues/?jql=project%20%3D%20AURORA%20AND%20labels%20%3D%20newbie%20and%20resolution%3Dunresolved) -that are good starting places for new Aurora contributors; pick one of these and dive in! Once -you've got a patch, the next step is to post a review. +that are good starting places for new Aurora contributors; pick one of these and dive in! To assign +a task to yourself, first ask for your JIRA id to be whitelisted by either asking in IRC/Slack or by +emailing d...@apache.aurora.org. Once your JIRA account has been whitelisted you can assign tickets +to yourself. The next step is to prepare your patch and finally post it for review. ## Getting your ReviewBoard Account