Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Fri, 18 Nov 2011 20:26:57 -0000
Message-ID: <20111118202657.2305.30940@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Update_of_=22Git=5FAt=5FApache=5FGuide=22_by?=
 =?utf-8?q?_JanLehnardt?=
Auto-Submitted: auto-generated

Dear Wiki user,

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

The "Git_At_Apache_Guide" page has been changed by JanLehnardt:
http://wiki.apache.org/couchdb/Git_At_Apache_Guide?action=3Ddiff&rev1=3D6&r=
ev2=3D7

  For understanding the technical aspects of GIT and SVN please read [[SVNv=
sGIT]]. This will help you to grok the design decissions
  =

  =3D=3D Project Structure =3D=3D
-  1. Each project should get one PMC-private GIT repository which conains =
confidential legal stuff like trademark contracts, creds for community acco=
unts like twitter, etc
+  1. Each project should have a way to share PMC-private code. This can be=
 a separate repo or just branches secured by naming convention (e.g. branch=
es/private/...). It is for confidential legal stuff like trademark contract=
s, creds for community accounts like twitter, etc
   1. Each project has at least one GIT repository which contains the main =
project and is read/writable for all committers
   1. Some projects might need additional GIT repositories containing proje=
ct parts which have a completely separated lifecycle from the main project.=
 This can be various build-tools (checkstyle-rules, project specific maven-=
plugins which are needed to build the project) or the project site. This is=
 needed because a GIT branch and tag always affects the whole repository
 =20