| 1 |
robbat2 08/10/12 09:53:37 |
| 2 |
|
| 3 |
Modified: policy.xml |
| 4 |
Log: |
| 5 |
update overlays policy draft to include SoC overlays and our already-existing external-style overlays. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.4 xml/htdocs/proj/en/overlays/policy.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/policy.xml?rev=1.4&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/policy.xml?rev=1.4&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/policy.xml?r1=1.3&r2=1.4 |
| 13 |
|
| 14 |
Index: policy.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/policy.xml,v |
| 17 |
retrieving revision 1.3 |
| 18 |
retrieving revision 1.4 |
| 19 |
diff -p -w -b -B -u -u -r1.3 -r1.4 |
| 20 |
--- policy.xml 16 Dec 2006 13:37:17 -0000 1.3 |
| 21 |
+++ policy.xml 12 Oct 2008 09:53:37 -0000 1.4 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/policy.xml,v 1.3 2006/12/16 13:37:17 genstef Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/overlays/policy.xml,v 1.4 2008/10/12 09:53:37 robbat2 Exp $ --> |
| 27 |
|
| 28 |
<guide link="/proj/en/overlays/policy.xml" lang="en"> |
| 29 |
<title>Gentoo Overlays Policy</title> |
| 30 |
@@ -8,6 +8,12 @@ |
| 31 |
<author title="Author"> |
| 32 |
<mail link="stuart@g.o">Stuart Herbert</mail> |
| 33 |
</author> |
| 34 |
+<author title="Author"> |
| 35 |
+ <mail link="jokey">Markus Ullmann</mail> |
| 36 |
+</author> |
| 37 |
+<author title="Author"> |
| 38 |
+ <mail link="robbat2">Robin H. Johnson</mail> |
| 39 |
+</author> |
| 40 |
|
| 41 |
<abstract> |
| 42 |
This is the policy document governing the Gentoo Overlays service. |
| 43 |
@@ -17,8 +23,8 @@ This is the policy document governing th |
| 44 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 45 |
<license/> |
| 46 |
|
| 47 |
-<version>Draft 1</version> |
| 48 |
-<date>2006-05-01</date> |
| 49 |
+<version>Draft 2</version> |
| 50 |
+<date>2008-10-12</date> |
| 51 |
|
| 52 |
<chapter> |
| 53 |
<title>Introduction</title> |
| 54 |
@@ -56,11 +62,9 @@ overlays.g.o hosts two types of overlay: |
| 55 |
<ul> |
| 56 |
<li>overlays for Gentoo project teams</li> |
| 57 |
<li>overlays for individual Gentoo developers</li> |
| 58 |
+ <li>overlays for Gentoo summer of code projects</li> |
| 59 |
+ <li>overlays for other Gentoo-specific projects that are external</li> |
| 60 |
</ul> |
| 61 |
-<p> |
| 62 |
-overlays.g.o does *not* host overlays owned by any other individuals at this |
| 63 |
-time. |
| 64 |
-</p> |
| 65 |
</body> |
| 66 |
</section> |
| 67 |
|
| 68 |
@@ -102,6 +106,33 @@ individual Gentoo developer who asked fo |
| 69 |
</p> |
| 70 |
</body> |
| 71 |
</section> |
| 72 |
+ |
| 73 |
+<section> |
| 74 |
+<title>Summer of Code Overlays</title> |
| 75 |
+<body> |
| 76 |
+<p> |
| 77 |
+"Summer of Code overlays" are overlays that were created for the express |
| 78 |
+purpose of hosting the development of a Google Summer of Code (SoC) project for |
| 79 |
+Gentoo. |
| 80 |
+</p> |
| 81 |
+<p> |
| 82 |
+Each "SoC overlay" will be named for the SoC project. Multiple overlays may |
| 83 |
+exist if required by the project. |
| 84 |
+</p> |
| 85 |
+<p> |
| 86 |
+As far as this policy is concerned, SoC overlays are owned by the SoC student. |
| 87 |
+</p> |
| 88 |
+</body> |
| 89 |
+</section> |
| 90 |
+ |
| 91 |
+<section> |
| 92 |
+<title>External Gentoo-specific overlays</title> |
| 93 |
+<body> |
| 94 |
+<p> |
| 95 |
+TODO |
| 96 |
+</p> |
| 97 |
+</body> |
| 98 |
+</section> |
| 99 |
</chapter> |
| 100 |
|
| 101 |
<chapter> |
| 102 |
@@ -110,7 +141,7 @@ individual Gentoo developer who asked fo |
| 103 |
<body> |
| 104 |
<ol> |
| 105 |
<li>Infra are responsible for the platform (hardware + o/s) that overlays.g.o is hosted on.</li> |
| 106 |
- <li>The overlays project team is responsible for administering the overlays.g.o service, including responsibility for the software used to deliver the service (e.g. svn, trac).</li> |
| 107 |
+ <li>The overlays project team is responsible for administering the overlays.g.o service, including responsibility for the software used to deliver the service (e.g. svn, trac, git, gitweb).</li> |
| 108 |
<li>Overlay owners are responsible for the contents of their overlays, and for the conduct of anyone who has commit access to their overlays.</li> |
| 109 |
<li>Any individual committing to an overlay is responsible for his/her own actions.</li> |
| 110 |
</ol> |
| 111 |
@@ -162,6 +194,22 @@ Developer overlays: |
| 112 |
<li>Any Gentoo dev can ask for commit access, with the agreement of the overlay's owner.</li> |
| 113 |
<li>Any non-dev can have commit access to a developer's overlay. The request for access has to come from the owner of the overlay.</li> |
| 114 |
</ul> |
| 115 |
+ |
| 116 |
+<p> |
| 117 |
+SoC overlays: |
| 118 |
+</p> |
| 119 |
+<ul> |
| 120 |
+ <li>The SoC student mentor and student will be provided with the overlay.</li> |
| 121 |
+ <li>Any non-dev can have commit access to a SoC's overlay. The request for access must come from either the SoC student or his mentor.</li> |
| 122 |
+</ul> |
| 123 |
+ |
| 124 |
+<p> |
| 125 |
+External overlays: |
| 126 |
+</p> |
| 127 |
+<ul> |
| 128 |
+ <li>TODO</li> |
| 129 |
+</ul> |
| 130 |
+ |
| 131 |
<p>Common Requirements For Non-Devs</p> |
| 132 |
<ul> |
| 133 |
<li>The non-dev is required to have registered their nick on Freenode IRC first, and must provide a valid email address for our records.</li> |
| 134 |
@@ -311,8 +359,8 @@ you've checked and made sure it meets th |
| 135 |
The only access to overlays.g.o is via these two mechanisms: |
| 136 |
</p> |
| 137 |
<ol> |
| 138 |
-<li>HTTP/HTTPS and Apache, and</li> |
| 139 |
-<li>rsync from dev.gentoo.org (coming in Phase 2)</li> |
| 140 |
+<li>HTTP/HTTPS and Apache</li> |
| 141 |
+<li>SSH to Gitosis for Git overlays</li> |
| 142 |
</ol> |
| 143 |
<p> |
| 144 |
The security mechanism for overlays.g.o is via HTTP basic auth, over SSL. We use both htpasswd and htgroup files to manage who can commit where. |
Archives