Gentoo Archives: gentoo-commits

From: "Tobias Heinlein (keytoaster)" <keytoaster@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/recruiters: index.xml
Date: Fri, 23 Jan 2009 18:41:55
Message-Id: E1LQQyX-0007ew-0P@stork.gentoo.org
1 keytoaster 09/01/23 18:41:53
2
3 Modified: index.xml
4 Log:
5 Adding common paste stuff and fixing some repodoc errors.
6
7 Revision Changes Path
8 1.66 xml/htdocs/proj/en/devrel/recruiters/index.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?rev=1.66&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?rev=1.66&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?r1=1.65&r2=1.66
13
14 Index: index.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml,v
17 retrieving revision 1.65
18 retrieving revision 1.66
19 diff -u -r1.65 -r1.66
20 --- index.xml 16 Jan 2009 20:16:44 -0000 1.65
21 +++ index.xml 23 Jan 2009 18:41:52 -0000 1.66
22 @@ -3,6 +3,8 @@
23 <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
24 <!DOCTYPE project SYSTEM "/dtd/project.dtd">
25
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml,v 1.66 2009/01/23 18:41:52 keytoaster Exp $ -->
27 +
28 <project>
29 <name>recruiters</name>
30 <longname>Gentoo Developer Recruiters</longname>
31 @@ -114,7 +116,7 @@
32 The new developer will have a mentoring and evaluation period of up to a month.
33 This will be determined by the recruiter based on feedback from the mentor.
34 During this mentoring period, the mentor is responsible for providing the <uri
35 -link="http://www.gentoo.org/proj/en/devrel/quiz">quiz</uri>. <!-- <uri
36 +link="http://www.gentoo.org/proj/en/devrel/quiz">quiz</uri>. <!-- <uri
37 link="http://www.gentoo.org/proj/en/devrel/copyright">copyright</uri> document
38 to the new developer. Copyright documents should be signed, scanned, and sent
39 to recruiters, or optionally GPG-signed. Hand signatures are preferred. See the
40 @@ -153,6 +155,43 @@
41 </extrachapter>
42
43 <extrachapter>
44 +<title>Stuff to remember</title>
45 +<section>
46 +<title>When adding yourself to a bug</title>
47 +<body>
48 +
49 +<p>
50 +I will be your recruiter. Please send your quizzes to recruiters@g.o
51 +when approved by your mentor. Always add a comment to this bug when you send
52 +something to that address. When the quizzes are sent please contact me by IRC
53 +or email to schedule the first review session. If you think that recruiters
54 +aren't paying attention to this bug at any later point in time, it's your job
55 +to ping us on IRC if you don't want any delays.
56 +</p>
57 +
58 +</body>
59 +</section>
60 +<section>
61 +<title>For review session</title>
62 +<body>
63 +
64 +<p>
65 +I will go through your answers, find out errors and ask some extras related
66 +and unrelated to the quiz questions. Take your time, it's supposed to be a
67 +learning experience as much as a test of your skills. But just tell me if
68 +you can't absolute find something so that you don't use too much time.
69 +</p>
70 +
71 +<p>
72 +After the sessions you are asked to submit a fixed versions of the quizzes so
73 +logging the session might be prudent.
74 +</p>
75 +
76 +</body>
77 +</section>
78 +</extrachapter>
79 +
80 +<extrachapter>
81 <title>Steps for adding a new developer</title>
82 <section>
83 <title>1. Adding the new developer to LDAP</title>
84 @@ -345,7 +384,7 @@
85 <section>
86 <title>2. Setting up the developer's gentooAccess</title>
87 <body>
88 -
89 +
90 <p>
91 In preparation of granting access to cvs and/or svn, the gentoo-core
92 mailing list or changing his bugzilla login name, you will need to poke one of
93 @@ -390,9 +429,11 @@
94 will trigger the creation of his account.
95 </p>
96
97 -<note>Try handing the dev-to-be the full commandline like
98 -<c>ssh hyakuhei@××××××××××.org</c>, in order to minimize
99 -mistakes and/or misconfigurations.</note>
100 +<note>
101 +Try handing the dev-to-be the full commandline like
102 +<c>ssh hyakuhei@××××××××××.org</c>, in order to minimize mistakes and/or
103 +misconfigurations.
104 +</note>
105
106 </body>
107 </section>
108 @@ -424,8 +465,9 @@
109 </p>
110
111 <p>
112 -Point your browser at <uri>https://lists.gentoo.org/mlmmj/subscribers.cgi</uri>. Fill in the
113 -developer's <c>@gentoo.org</c> email adress and hit <b>Subscribe</b>.
114 +Point your browser at <uri>https://lists.gentoo.org/mlmmj/subscribers.cgi</uri>.
115 +Fill in the developer's <c>@gentoo.org</c> email adress and hit
116 +<b>Subscribe</b>.
117 </p>
118
119 </body>
120 @@ -451,8 +493,8 @@
121 </p>
122
123 <p>
124 -If you want to automatically give voice status (+v) in <c>#gentoo-dev</c> to a recruit,
125 -e.g. during his/her mentoring period, use the following command:
126 +If you want to automatically give voice status (+v) in <c>#gentoo-dev</c> to a
127 +recruit, e.g. during his/her mentoring period, use the following command:
128 </p>
129
130 <pre caption="Adding the developer to ChanServ's access list">
131 @@ -464,7 +506,7 @@
132 <section>
133 <title>8. Introducing the developer on gentoo-dev</title>
134 <body>
135 -
136 +
137 <p>
138 In order to announce the new developer, you as recruiter have the honour to
139 introduce him to the developer community. Write a brief introduction containing