You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by be...@apache.org on 2019/03/25 12:17:41 UTC

[mesos] branch master updated (4580834 -> aa0080e)

This is an automated email from the ASF dual-hosted git repository.

bennoe pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git.


    from 4580834  Updated operation feedback documentation.
     new 393a020  Clarified timeline for advanced contributions.
     new aa0080e  Updated advanced contributing guide.

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 docs/advanced-contribution.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)


[mesos] 02/02: Updated advanced contributing guide.

Posted by be...@apache.org.
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 aa0080e8ac76c771f2604c5ecbf28d53df151cfe
Author: Benno Evers <be...@mesosphere.com>
AuthorDate: Mon Mar 25 13:17:00 2019 +0100

    Updated advanced contributing guide.
    
    Removed the instruction to create a reviewboard account
    from the advanced contributing guide, since this instruction
    became impossible to follow for contributors.
    
    Review: https://reviews.apache.org/r/70129/
---
 docs/advanced-contribution.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/advanced-contribution.md b/docs/advanced-contribution.md
index 4184f4b..573138d 100644
--- a/docs/advanced-contribution.md
+++ b/docs/advanced-contribution.md
@@ -19,7 +19,12 @@ If you'd like to make significant contributions to Mesos, then you'll want to be
 ## Issue Tracking, Code Review, and Mailing Lists
 
 * We use [Apache Software Foundation JIRA](https://issues.apache.org/jira/browse/mesos/) to track and manage issues. If you don't already have an account, you'll need to create one.
-* We use [Apache Review Board](https://reviews.apache.org) for code reviews. If you don't already have an account, you'll need to create one (it's separate from your Apache JIRA account).
+
+* We use [Apache Review Board](https://reviews.apache.org) for code reviews.
+
+  **NOTE**: Apache Review Board currently does not allow creation of new accounts. We are aware of this and are looking into possible solutions;
+  in the meantime please coordinate with your shepherd on how to best transmit your patches.
+
     * A code review request should be created for every JIRA that involves a change to the codebase.
 * Once your JIRA and Review Board accounts are in place please go ahead and create a review or GitHub pull request with an entry for yourself in [contributors.yaml](https://github.com/apache/mesos/blob/master/docs/contributors.yaml) file.
     * The file is used to map contributions to the JIRA and Review Board accounts of their respective authors. We also use this mapping to track contributions of various organizations to Apache Mesos.


[mesos] 01/02: Clarified timeline for advanced contributions.

Posted by be...@apache.org.
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 <be...@mesosphere.com>
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