Re: [ovs-dev] [PATCH 02/23] doc: Convert committer-grant-revocation to rST

[Russell Bryant]

On Sun, Oct 30, 2016 at 2:29 PM, Stephen Finucane  wrote:

> Signed-off-by: Stephen Finucane 
> ---
>  Documentation/automake.mk|   2 +-
>  Documentation/committer-grant-revocation.md  | 356
> 
>  Documentation/committer-grant-revocation.rst | 398
> +++
>  MAINTAINERS.rst  |   2 +-
>  4 files changed, 400 insertions(+), 358 deletions(-)
>  delete mode 100644 Documentation/committer-grant-revocation.md
>  create mode 100644 Documentation/committer-grant-revocation.rst
>

I made one very small fix to this one.  I'll apply it in a larger batch in
a little while.

diff --git a/Documentation/committer-grant-revocation.rst
b/Documentation/committer-grant-revocation.rst
index 5d6435b..5b3c975 100644
--- a/Documentation/committer-grant-revocation.rst
+++ b/Documentation/committer-grant-revocation.rst
@@ -51,7 +51,7 @@ the following in their interaction with the project:

   - Submissions are free of obvious critical defects
   - Submissions do not typically require many iterations of improvement
- to be accepted
+to be accepted

 - Consistent participation in code review of other's patches, including
   existing committers, with comments consistent with the overall project



-- 
Russell Bryant
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] [PATCH 02/23] doc: Convert committer-grant-revocation to rST

[Stephen Finucane]

Signed-off-by: Stephen Finucane 
---
 Documentation/automake.mk|   2 +-
 Documentation/committer-grant-revocation.md  | 356 
 Documentation/committer-grant-revocation.rst | 398 +++
 MAINTAINERS.rst  |   2 +-
 4 files changed, 400 insertions(+), 358 deletions(-)
 delete mode 100644 Documentation/committer-grant-revocation.md
 create mode 100644 Documentation/committer-grant-revocation.rst

diff --git a/Documentation/automake.mk b/Documentation/automake.mk
index d709e77..2f728bd 100644
--- a/Documentation/automake.mk
+++ b/Documentation/automake.mk
@@ -1,6 +1,6 @@
 docs += \
Documentation/committer-responsibilities.md \
-   Documentation/committer-grant-revocation.md \
+   Documentation/committer-grant-revocation.rst \
Documentation/group-selection-method-property.txt \
Documentation/OVSDB-replication.md \
Documentation/release-process.md
diff --git a/Documentation/committer-grant-revocation.md 
b/Documentation/committer-grant-revocation.md
deleted file mode 100644
index 83b703c..000
--- a/Documentation/committer-grant-revocation.md
+++ /dev/null
@@ -1,356 +0,0 @@
-OVS Committer Grant/Revocation Policy
-=
-
-An OVS committer is a participant in the project with the ability
-to commit code directly to the master repository. Commit access
-grants a broad ability to affect the progress of the project as
-presented by its most important artifact, the code and related
-resources that produce working binaries of Open vSwitch. As such
-it represents a significant level of trust in an individual's
-commitment to working with other committers and the community at
-large for the benefit of the project. It can not be granted
-lightly and, in the worst case, must be revocable if the trust
-placed in an individual was inappropriate.
-
-This document suggests guidelines for granting and revoking commit
-access. It is intended to provide a framework for evaluation of such
-decisions without specifying deterministic rules that wouldn't be
-sensitive to the nuance of specific situations. In the end the
-decision to grant or revoke committer privileges is a judgment call
-made by the existing set of committers.
-
-Granting Commit Access
---
-
-Granting commit access should be considered when a candidate has
-demonstrated the following in their interaction with the project:
-
-* Contribution of significant new features through the patch
-  submission process where:
-  * Submissions are free of obvious critical defects
-  * Submissions do not typically require many iterations of
-improvement to be accepted
-* Consistent participation in code review of other's patches,
-  including existing committers, with comments consistent with the
-  overall project standards
-* Assistance to those in the community who are less knowledgeable
-  through active participation in project forums such as the
-  ovs-discuss mailing list.
-* Plans for sustained contribution to the project compatible with
-  the project's direction as viewed by current committers.
-* Commitment to meet the expectations described in the
-  "Expectations of Developer's with Open vSwitch Access"
-
-The process to grant commit access to a candidate is simple:
-
-* An existing committer nominates the candidate by sending an
-  email to all existing committers with information
-  substantiating the contributions of the candidate in the areas
-  described above.
-* All existing committers discuss the pros and cons of granting
-  commit access to the candidate in the email thread.
-* When the discussion has converged or a reasonable time has
-  elapsed without discussion developing (e.g. a few business days)
-  the nominator calls for a final decision on the candidate with a
-  followup email to the thread.
-* Each committer may vote yes, no, or abstain by replying to the
-  email thread. A failure to reply is an implicit abstention.
-* After votes from all existing committers have been collected or a
-  reasonable time has elapsed for them to be provided (e.g. a
-  couple of business days) the votes are evaluated. To be granted
-  commit access the candidate must receive yes votes from a
-  majority of the existing committers and zero no votes. Since a
-  no vote is effectively a veto of the candidate it should be
-  accompanied by a reason for the vote.
-* The nominator summarizes the result of the vote in an email to
-  all existing committers.
-* If the vote to grant commit access passed, the candidate is
-  contacted with an invitation to become a committer to the project
-  which asks them to agree to the committer expectations
-  documented on the project web site.
-* If the candidate agrees access is granted by setting up commit
-  access to the repos on github.
-
-Revoking Commit Access
---
-
-There are two situations in which