[Couchdb Wiki] Update of "GitSuccessCriterias" by RandallLeeds

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "GitSuccessCriterias" page has been changed by RandallLeeds:
http://wiki.apache.org/couchdb/GitSuccessCriterias?action=diff&rev1=1&rev2=2

Comment:
Taking a shot at clarifying author/committer distinction.

  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.
  
   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 commiters and autors must be authenticated. It must not be possible to fake the authorId and thus tamper the commit history
+  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. 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 as 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.