couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "GitSuccessCriteria" by DaveCottlehuber
Date Fri, 18 Nov 2011 22:27:13 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "GitSuccessCriteria" page has been changed by DaveCottlehuber:
http://wiki.apache.org/couchdb/GitSuccessCriteria?action=diff&rev1=6&rev2=7

Comment:
comply with RFC2119. and sum engrish koretshuns.

  = Criteria for GIT @ ASF =
- This list describes all points which should be met for GIT to become a SCM which can finally
be used for ASF projects which like to use GIT.
+ 
+ This list describes all points which MUST be met for GIT to become an accepted SCM for ASF
projects.
+ 
+  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described
in [[http://www.ietf.org/rfc/rfc2119.txt|RFC 2119]].
  
   1. Technical
-    1. The preservation of the commit history must be guaranteed. It must be practically
impossible to delete any piece of commit history which made it into an official ASF release
+    1. The preservation of the commit history MUST be guaranteed. It SHOULD be practically
impossible to delete, tamper with, or alter any piece of commit history which made it into
an official ASF release.
-    1. The commiter of any change must be authenticated. It must not be possible to fake
the committer id and thus taint the commit history.
+    1. Changes MUST be submitted by an authenticated committer, over a secure connection.
It SHOULD not be possible to fake the committer id and thus taint the commit history.
-    1. In cases where the committer is not the author, the committer must ensure that the
author has granted the code to the ASF under the terms of the [[http://www.apache.org/licenses/LICENSE-2.0|Apache
License]] or that the contribution is sufficiently trivial to waive this requirement.
+   1. In cases where the committer is not the author, the committer is REQUIRED to ensure
that the author has granted the code to the ASF under the terms of the [[http://www.apache.org/licenses/LICENSE-2.0|Apache
License]] or that the contribution is sufficiently trivial to waive this requirement.
-    1. The single canonical project repository (repositories) must be hosted on ASF servers
under full control of the ASF infra team.
-    1. There must be no other legal problem because of the usage of GIT as canonical
-    1. The canonical GIT repo hosted at the ASF must be the repo to cut official ASF releases
from.
-    1. There must be backups from the repos.
-    1. There must be no blocking technical issue left with GIT restricting the community
  
-  2. Community
-    1. Clear guidelines for committers on handling of development branches, feature branches,
release branches and maintenance branches.
-    1. Clear guidelines for committers on handling security@ issues.
-    1. Clear guidelines on how to cut releases from git.
+    1. The single canonical project repository (repositories) MUST be hosted on ASF servers
under full control of the ASF infra team.
+    1. There must be no other legal problem because of the usage of GIT as canonical repository.
+    1. The canonical GIT repo hosted at the ASF MUST be the repo to cut official ASF releases
from.
+    1. ASF Infrastructure MUST provide backups of the repository.
+    1. A set of community policies or procedures SHALL be defined, and the community SHALL
review them to ensure that any impact due to GIT implementation is either mitigated or accepted.
  
+  2. Community Policies and Procedures
+    1. How committers are RECOMMENDED To handle branches, including development, feature,
official releases, and maintenance branches.
+    1. How to handle security@ issues, and what material SHOULD NOT be committed to the repository.
+    1. A documented and accepted Release procedure MUST be defined and followed.
+    1. It is RECOMMENDED that a clear community contribution process is made available.
+ 
+ 
+  == Relevant Mailing List dicussions ==
+  
+  The following are links to the official ASF CouchDB mailing list archives. You can click
on arrows in the right-hand side to view replies.
+  
+ [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/201109.mbox/%3C400B8FD70F37440E98F7D00632936DB9@gmail.com%3E|Disabling
svn access 2011/09/23]
+ 
+ [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/201109.mbox/%3CCAJ_m3YB13xYApF3mdW3CFQxHq9ym72Nv9T_MfYOEp=hkCTnHLA@mail.gmail.com%3E|Approval
from ASF to start the Git Experiment 2011/09/29] and [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/201108.mbox/%3C4E36D474.1090304@couchone.com%3E|continued].
+ 

Mime
View raw message