| 1 |
rane 08/10/01 17:08:39 |
| 2 |
|
| 3 |
Modified: handbook.xml |
| 4 |
Added: hb-introduction-staffers.xml |
| 5 |
Log: |
| 6 |
adding new staffer policy |
| 7 |
|
| 8 |
Revision Changes Path |
| 9 |
1.11 xml/htdocs/proj/en/devrel/handbook/handbook.xml |
| 10 |
|
| 11 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml?rev=1.11&view=markup |
| 12 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml?rev=1.11&content-type=text/plain |
| 13 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml?r1=1.10&r2=1.11 |
| 14 |
|
| 15 |
Index: handbook.xml |
| 16 |
=================================================================== |
| 17 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml,v |
| 18 |
retrieving revision 1.10 |
| 19 |
retrieving revision 1.11 |
| 20 |
diff -u -r1.10 -r1.11 |
| 21 |
--- handbook.xml 17 Aug 2007 20:22:08 -0000 1.10 |
| 22 |
+++ handbook.xml 1 Oct 2008 17:08:39 -0000 1.11 |
| 23 |
@@ -1,9 +1,9 @@ |
| 24 |
<?xml version='1.0' encoding='UTF-8'?> |
| 25 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 26 |
|
| 27 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml,v 1.10 2007/08/17 20:22:08 musikc Exp $ --> |
| 28 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/handbook.xml,v 1.11 2008/10/01 17:08:39 rane Exp $ --> |
| 29 |
|
| 30 |
-<book link="handbook.xml"> |
| 31 |
+<book link="/proj/en/devrel/handbook/handbook.xml"> |
| 32 |
<title>Gentoo Developer Handbook</title> |
| 33 |
|
| 34 |
<!-- Author names only --> |
| 35 |
@@ -58,6 +58,10 @@ |
| 36 |
<mail link="musikc@g.o">Chrissy Fullam</mail> |
| 37 |
</author> |
| 38 |
|
| 39 |
+ <author title ="Author"> |
| 40 |
+ <mail link="rane@g.o">Łukasz Damentko</mail> |
| 41 |
+ </author> |
| 42 |
+ |
| 43 |
<author title="Author"> |
| 44 |
<mail link="drobbins@g.o">Daniel Robbins (Retired) </mail> |
| 45 |
</author> |
| 46 |
@@ -124,8 +128,8 @@ |
| 47 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 48 |
<license/> |
| 49 |
|
| 50 |
- <version>1.0.3</version> |
| 51 |
- <date>2007-08-17</date> |
| 52 |
+ <version>2</version> |
| 53 |
+ <date>2008-10-01</date> |
| 54 |
|
| 55 |
<part> |
| 56 |
<title>Introduction</title> |
| 57 |
@@ -178,6 +182,15 @@ |
| 58 |
</abstract> |
| 59 |
<include href="hb-introduction-hierarchy.xml"/> |
| 60 |
</chapter> |
| 61 |
+ |
| 62 |
+ <chapter> |
| 63 |
+ <title>Staff member policy</title> |
| 64 |
+ <abstract> |
| 65 |
+ This section outlines recruitment and retirement policies for Gentoo |
| 66 |
+ staff members. |
| 67 |
+ </abstract> |
| 68 |
+ <include href="hb-introduction-staffers.xml"/> |
| 69 |
+ </chapter> |
| 70 |
</part> |
| 71 |
|
| 72 |
<part> |
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
1.1 xml/htdocs/proj/en/devrel/handbook/hb-introduction-staffers.xml |
| 77 |
|
| 78 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-staffers.xml?rev=1.1&view=markup |
| 79 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-staffers.xml?rev=1.1&content-type=text/plain |
| 80 |
|
| 81 |
Index: hb-introduction-staffers.xml |
| 82 |
=================================================================== |
| 83 |
<?xml version='1.0' encoding='UTF-8'?> |
| 84 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 85 |
|
| 86 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-introduction-staffers.xml,v 1.1 2008/10/01 17:08:39 rane Exp $ --> |
| 87 |
|
| 88 |
<sections> |
| 89 |
<version>1</version> |
| 90 |
<date>2008-09-13</date> |
| 91 |
|
| 92 |
<section> |
| 93 |
<title>Gentoo Staff Member policy</title> |
| 94 |
<subsection> |
| 95 |
<title>Introduction</title> |
| 96 |
<body> |
| 97 |
|
| 98 |
<p> |
| 99 |
Running a Linux distribution has multiple aspects and many of them aren't |
| 100 |
directly connected to coding. Every distribution needs people to run its |
| 101 |
servers, help its community, provide documentation, handle project's finances |
| 102 |
and legal issues and serve many other tasks. Their contributions are as |
| 103 |
important as code contributions. These developers are called staff members in |
| 104 |
Gentoo. |
| 105 |
</p> |
| 106 |
|
| 107 |
</body> |
| 108 |
</subsection> |
| 109 |
<subsection> |
| 110 |
<title>Types of staff members</title> |
| 111 |
<body> |
| 112 |
|
| 113 |
<p> |
| 114 |
The following list contains all types of staff members we are currently |
| 115 |
recruiting in Gentoo: |
| 116 |
</p> |
| 117 |
|
| 118 |
<ul> |
| 119 |
<li><uri link="/proj/en/infrastructure/">Gentoo Infrastructure</uri> project members</li> |
| 120 |
<li><uri link="/proj/en/gdp/">Gentoo Documentation</uri> editors and translators</li> |
| 121 |
<li><uri link="/news/en/gmn/">Gentoo Monthly Newsletter</uri> editors and translators</li> |
| 122 |
<li><uri link="/proj/en/forums/">Gentoo Forums</uri> global moderators and administrators</li> |
| 123 |
<li><uri link="/proj/en/devrel/">Gentoo Developer Relations</uri> members</li> |
| 124 |
<li><uri link="/proj/en/userrel/">Gentoo User Relations</uri> members</li> |
| 125 |
<li><uri link="/proj/en/pr/">Gentoo Public Relations</uri> members</li> |
| 126 |
<li><uri link="/proj/en/security/">Gentoo Security</uri> GLSA coordinators</li> |
| 127 |
<li><uri link="/proj/en/sunrise/">Gentoo Sunrise</uri> developers</li> |
| 128 |
<li><uri link="/foundation/en">Gentoo Foundation</uri> officers</li> |
| 129 |
</ul> |
| 130 |
|
| 131 |
<impo> |
| 132 |
If the project you want to contribute to as a staff member isn't on this list |
| 133 |
and you think it should, please contact <mail link="devrel@g.o">Developer |
| 134 |
Relations</mail> about policy change. |
| 135 |
</impo> |
| 136 |
|
| 137 |
</body> |
| 138 |
</subsection> |
| 139 |
<subsection> |
| 140 |
<title>How is staff member access different from ebuild developer access?</title> |
| 141 |
<body> |
| 142 |
|
| 143 |
<p> |
| 144 |
Access is assigned based on the responsibilities of the Staff Member. All |
| 145 |
Gentoo Developers are provided with an gentoo.org mail address, ssh access to |
| 146 |
dev.gentoo.org (for shell, ldap, public_html, etc) as well as cvs access to |
| 147 |
gentoo's web/project pages. As a staff member you will not be granted access to |
| 148 |
the ebuild tree, as ebuild developers are, but may be granted access to other |
| 149 |
area's based on your need and responsibilities. |
| 150 |
</p> |
| 151 |
|
| 152 |
</body> |
| 153 |
</subsection> |
| 154 |
<subsection> |
| 155 |
<title>How can I become a Gentoo staff member?</title> |
| 156 |
<body> |
| 157 |
|
| 158 |
<p> |
| 159 |
You have to work with members of the project you wish to help. You are invited |
| 160 |
to the team when your level of contributions and expertise justify you becoming |
| 161 |
a developer in that project. It may take time and may also require passing |
| 162 |
internal recruitment procedures within that project first. Those procedures are |
| 163 |
in place to ensure you know what your future function within Gentoo involves, |
| 164 |
they are created and maintained by the project itself. |
| 165 |
</p> |
| 166 |
|
| 167 |
<p> |
| 168 |
When you are ready, you will need to look for a mentor and a developer bug will |
| 169 |
be filed for you after your mentor has approved your <uri |
| 170 |
link="http://www.gentoo.org/proj/en/devrel/quiz/staff-quiz.txt">staff |
| 171 |
quiz</uri>. |
| 172 |
Once a recruiter has been assigned to your developer bug, both of you will need |
| 173 |
to schedule your review. Please see the <uri |
| 174 |
link="http://www.gentoo.org/proj/en/devrel/recruiters/mentor.xml">mentoring |
| 175 |
guide</uri> for more information. |
| 176 |
</p> |
| 177 |
|
| 178 |
<note> |
| 179 |
As a staff member who isn't going to work on ebuilds, you won't be asked |
| 180 |
technical questions about them. All that will be required from you at this stage |
| 181 |
of your recruitment is a good understanding of Gentoo internals. |
| 182 |
</note> |
| 183 |
|
| 184 |
</body> |
| 185 |
</subsection> |
| 186 |
<subsection> |
| 187 |
<title> |
| 188 |
I would like to be recruited as a staff member but also plan joining other |
| 189 |
projects in future |
| 190 |
</title> |
| 191 |
<body> |
| 192 |
|
| 193 |
<p> |
| 194 |
Every Gentoo developer can join any project (s)he wishes if developers |
| 195 |
of the project agree with that. Before you can start contributing to the |
| 196 |
ebuild tree though, you will have to apply for ebuild developer recruitment. |
| 197 |
This means you need a mentor, a history of technical contributions (bug fixes, |
| 198 |
overlays, etc...) and adequate training. Please contact recruiters about this. |
| 199 |
</p> |
| 200 |
|
| 201 |
</body> |
| 202 |
</subsection> |
| 203 |
<subsection> |
| 204 |
<title>How is retirement handled for staff members?</title> |
| 205 |
<body> |
| 206 |
|
| 207 |
<p> |
| 208 |
You have to either remain active within the project you have joined or move to |
| 209 |
other projects. If there are no projects within Gentoo you're active in, you are |
| 210 |
subject for retirement via <uri link="/proj/en/devrel/undertakers/">Gentoo |
| 211 |
Undertakers</uri> procedures. |
| 212 |
</p> |
| 213 |
|
| 214 |
</body> |
| 215 |
</subsection> |
| 216 |
</section> |
| 217 |
</sections> |
Archives