This is an automated email from the ASF dual-hosted git repository. bennoe pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/mesos.git
commit 393a020711a6f6bed436d013ad48cc5f319deb7b Author: Benno Evers <[email protected]> AuthorDate: Mon Mar 25 10:51:32 2019 +0100 Clarified timeline for advanced contributions. The previous wording heavily implied some automation that would update JIRA on every change to `contributors.yaml`. This commit clarifies that account status changes require manual action by an administrator. Review: https://reviews.apache.org/r/70293 --- docs/advanced-contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/advanced-contribution.md b/docs/advanced-contribution.md index 28a3141..4184f4b 100644 --- a/docs/advanced-contribution.md +++ b/docs/advanced-contribution.md @@ -43,7 +43,7 @@ Here is the standard procedure for proposing and making changes to Mesos: 3. Issues marked with the "[newbie](https://issues.apache.org/jira/browse/MESOS-1?jql=project%20%3D%20MESOS%20AND%20status%20%3D%20Accepted%20AND%20labels%20%3D%20newbie)" label can be good candidates for "starter" projects. You can also look for the labels "newbie++", "beginner", and "beginners". 4. When identifying a JIRA issue to work on, it is recommended to work on items that are relevant to the next release. Selecting work items important for the next release increases the priority for reviewers during the contribution process. See the tracking ticket for the release to figure out the high priority projects or ask the release manager to guide you. 2. Assign the JIRA to yourself. - 1. You will be able to assign the JIRA to yourself as soon as your pull request with additions to the contributors.yaml file is merged. + 1. You will be able to assign the JIRA to yourself as soon as a JIRA admin updates your account to 'contributor' status. This will usually be done soon after your pull request with additions to the contributors.yaml file is merged. 3. Formulate a plan for resolving the issue. Guidelines to consider when designing a solution can be found in the [effective-code-reviewing](effective-code-reviewing.md) document. It is important to discuss your proposed solution within the JIRA ticket early in the resolution process in order to get feedback from reviewers. Early discussions will help: 1. ensure the solution will be scoped in a consumable fashion; 2. eliminate duplicate work with other contributions; and
