1 |
tommy 10/05/01 11:19:03 |
2 |
|
3 |
Modified: index.xml |
4 |
Log: |
5 |
Update recruiters page |
6 |
|
7 |
Revision Changes Path |
8 |
1.76 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.76&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?rev=1.76&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?r1=1.75&r2=1.76 |
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.75 |
18 |
retrieving revision 1.76 |
19 |
diff -u -r1.75 -r1.76 |
20 |
--- index.xml 12 Apr 2010 05:53:26 -0000 1.75 |
21 |
+++ index.xml 1 May 2010 11:19:03 -0000 1.76 |
22 |
@@ -3,13 +3,13 @@ |
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.75 2010/04/12 05:53:26 calchan Exp $ --> |
27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml,v 1.76 2010/05/01 11:19:03 tommy Exp $ --> |
28 |
|
29 |
<project> |
30 |
<name>recruiters</name> |
31 |
<longname>Gentoo Developer Recruiters</longname> |
32 |
|
33 |
-<date>2009-02-27</date> |
34 |
+<date>2010-04-30</date> |
35 |
|
36 |
<author title="Author"> |
37 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
38 |
@@ -235,88 +235,23 @@ |
39 |
|
40 |
<p> |
41 |
At first, start adding the new developer to LDAP. This requires you to |
42 |
-<c>ssh</c> to <c>dev.gentoo.org</c> and use the <c>perl_ldap</c> script |
43 |
-to create the new account. |
44 |
+<c>ssh</c> to <c>dev.gentoo.org</c> and use the <c>newdev-fill.sh</c> |
45 |
+script to create the new account. This script will ask you for all |
46 |
+needed information and will set the ldap attributes. You should have |
47 |
+your LDAP password by hand, you will be asked for it for every LDAP |
48 |
+change. |
49 |
</p> |
50 |
|
51 |
<pre caption="Creating the initial UID in LDAP"> |
52 |
# <i>ssh dev.gentoo.org</i> |
53 |
-# <i>perl_ldap -b user -c</i> |
54 |
-Enter LDAP Password: |
55 |
- |
56 |
-LDAP Perl interface v1.0 |
57 |
-[ou=devs] >> <i>A hyakuhei</i> |
58 |
-Adding LDAP user hyakuhei |
59 |
-Enter First Name: Robert |
60 |
-Enter Last Name: Clark |
61 |
-Enter LDAP Password: |
62 |
- |
63 |
-done! |
64 |
+# <i>newdev-fill.sh hyakuhei</i> |
65 |
</pre> |
66 |
- |
67 |
<p> |
68 |
-Afterwards, the new developer should look like this: |
69 |
-</p> |
70 |
- |
71 |
-<pre caption="Informations present in LDAP after addition"> |
72 |
-[ou=devs] >> <i>s hyakuhei</i> |
73 |
-Searching... |
74 |
------------------------------------------------------------------------- |
75 |
-dn:uid=hyakuhei,ou=devs,dc=gentoo,dc=org |
76 |
- |
77 |
- uid: hyakuhei |
78 |
- cn: Robert Clark |
79 |
- givenName: Robert |
80 |
- sn: Clark |
81 |
- userPassword: {crypt}$1$HP/3wW0V$XUMrrFeQDHiMSGDOIUAbi/ |
82 |
-shadowLastChange: 13520 |
83 |
- shadowMax: 99999 |
84 |
- shadowWarning: 15 |
85 |
- loginShell: /bin/bash |
86 |
- homeDirectory: /home/hyakuhei |
87 |
- gecos: Robert Clark |
88 |
- shadowInactive: 15 |
89 |
- shadowExpire: 14883 |
90 |
- gidNumber: 100 |
91 |
- uidNumber: 2159 |
92 |
- birthday: undefined |
93 |
- gentooLocation: undefined |
94 |
- gentooRoles: undefined |
95 |
- gentooJoin: 2007/01/07 |
96 |
- herd: undefined |
97 |
- gentooStatus: active |
98 |
- gpgkey: undefined |
99 |
- gpgfingerprint: undefined |
100 |
- objectClass: top |
101 |
- person |
102 |
- organizationalPerson |
103 |
- gentooDev |
104 |
- inetOrgPerson |
105 |
- posixAccount |
106 |
- shadowAccount |
107 |
- ldapPublicKey |
108 |
-</pre> |
109 |
- |
110 |
-<p> |
111 |
-Next step is to fill the remaining informations needed, for example |
112 |
-<c>birthday</c>, <c>gentooLocation</c> and those others listed as |
113 |
-<c>undefined</c>. |
114 |
Please be aware, that as of <b>17. December 2007</b>, all dates |
115 |
in LDAP should be spelled in ISO8601, meaning like this: YYYY/MM/DD |
116 |
(ie. 2007/12/18). |
117 |
</p> |
118 |
|
119 |
-<pre caption="Updating the attribute gentooLocation"> |
120 |
-[ou=devs] >> <i>u hyakuhei</i> |
121 |
-[hyakuhei, ou=devs] >> <i>M gentooLocation "Wales, UK"</i> |
122 |
-Modifying LDAP user hyakuhei |
123 |
-done! |
124 |
-</pre> |
125 |
- |
126 |
-<p> |
127 |
-Same scheme applies to all those other <c>undefined</c> elements. |
128 |
-</p> |
129 |
- |
130 |
<p> |
131 |
Afterwards it should look like this: |
132 |
</p> |
133 |
@@ -337,6 +272,8 @@ |
134 |
shadowWarning: 15 |
135 |
loginShell: /bin/bash |
136 |
homeDirectory: /home/hyakuhei |
137 |
+ mail: hyakuhei@g.o |
138 |
+ joe.dev@××××××××.com |
139 |
gecos: Robert Clark |
140 |
shadowInactive: 15 |
141 |
shadowExpire: 14883 |
142 |
@@ -358,61 +295,10 @@ |
143 |
gentooRoles: Security/log monitoring apps, Auditing |
144 |
gpgkey: 0x2217D168 |
145 |
gpgfingerprint: 4C01 D375 8AEF CB2D 3AED 3B2D 119C 7E35 2217 D168 |
146 |
-</pre> |
147 |
- |
148 |
-<p> |
149 |
-We then need to create the <c>sshPublicKey</c> attribute. |
150 |
-</p> |
151 |
- |
152 |
-<p> |
153 |
-This first method requires the public ssh-key of the developer somewhere on |
154 |
-<c>dev.gentoo.org</c> in order to import it this way into LDAP. |
155 |
-</p> |
156 |
- |
157 |
-<pre caption="Creating the attribute sshPublicKey (file method)"> |
158 |
-# <i>perl_ldap -b user -M sshPublicKey "$(<hyakuhei.pub)" hyakuhei</i> |
159 |
-Modifying LDAP user hyakuhei |
160 |
-done! |
161 |
-</pre> |
162 |
- |
163 |
-<p> |
164 |
-Another method assumes you'll copy and paste public ssh-key directly into |
165 |
-command line. For readability we had to split very long public key but, of |
166 |
-course, you don't need to split it and you can paste everything in one line. |
167 |
-</p> |
168 |
- |
169 |
-<pre caption="Creating the attribute sshPublicKey (copy+paste method)"> |
170 |
-[hyakuhei, ou=devs] >> <i>C sshPublicKey "ssh-dss \ |
171 |
-AAAAB3NzaC1kc3MAAACBAKmRjZ21SqPHwRXgkWDVuLfSZ5FOSV26xaV3Fnsc68r9caDWMZyD8PAJfX\ |
172 |
-UeDXYOcUt4F3ZB+VL3DQSGg4ZEf4XVoNIOVnu87QaQyMJYT+u2EPsTJv99HZJM+tGT/ng6JfnRMWYd\ |
173 |
-EDAUJ6iKZLNPKt+KWH7KprlHxRUJzd1MpbsVAAAAFQD9i0iTAesG4A1PJwT232+6IxtDlwAAAIEAoV\ |
174 |
-tcO/ef4pd5WdJaeneOlmaFEF+P3lBbkaomT5oFv4GI+0BS3b+C9gOV+akDpu3Fn5JREwN665P+Cnid\ |
175 |
-2y3FVZY77CazbfHBpVX6elTndo1wxRYE02GxMkhqWpuMkcMChdRjhRrcLHzAh6wO64r/wd5ofciBxu\ |
176 |
-P2+ilWT151frgAAACAda4optpsYWmoSwIiLqfjr+Akxvzn9LWDcJ4LI4U8wakiHgBEGlhiIE7zrmS4\ |
177 |
-ZEp8vGKv/Rhk3fOU96eUsoWFyMYtYFtCv5hQBJrqhC5Ur3dvjVzbracSZytn2xrTc+AEngPXu55WN2\ |
178 |
-ebq/LMMTQV0Sq2wbDc7g9Jkxr4apAGDIM= hyakuhei@g.o"</i> |
179 |
-Modifying LDAP user hyakuhei |
180 |
-done! |
181 |
-</pre> |
182 |
- |
183 |
-<p> |
184 |
-We also need to add an external, i.e. non-<c>@gentoo.org</c>, email address. It |
185 |
-can be done with the exact same two methods as for the attribute sshPublicKey |
186 |
-above. For example: |
187 |
-</p> |
188 |
- |
189 |
-<pre caption="Adding an external email address."> |
190 |
-[hyakuhei, ou=devs] >> <i>C mail "joe.dev@××××××××.com"</i> |
191 |
-Modifying LDAP user hyakuhei |
192 |
-done! |
193 |
-</pre> |
194 |
- |
195 |
-<p> |
196 |
-We are done now with adding the developer to LDAP, lets quit now. |
197 |
-</p> |
198 |
- |
199 |
-<pre caption="Quitting"> |
200 |
-[hyakuhei, ou=devs] >> <i>quit</i> |
201 |
+ gentooMentor: his-mentor |
202 |
+ gentooDevBug: 012345 |
203 |
+ sshPublicKey: ssh-dss \ |
204 |
+AAAAB3NzaC1kc3MAAACBAKmRjZ21SqPHwRXgkWDVuLfSZ5FOSV26xaV3Fnsc68r9caDWMZyD8PAJfXUeDXYOcUt4F3ZB+VL3DQSGg4ZEf4XVoNIOVnu87QaQyMJYT+u2EPsTJv99HZJM+tGT/ng6JfnRMWYdEDAUJ6iKZLNPKt+KWH7KprlHxRUJzd1MpbsVAAAAFQD9i0iTAesG4A1PJwT232+6IxtDlwAAAIEAoVtcO/ef4pd5WdJaeneOlmaFEF+P3lBbkaomT5oFv4GI+0BS3b+C9gOV+akDpu3Fn5JREwN665P+Cnid2y3FVZY77CazbfHBpVX6elTndo1wxRYE02GxMkhqWpuMkcMChdRjhRrcLHzAh6wO64r/wd5ofciBxuP2+ilWT151frgAAACAda4optpsYWmoSwIiLqfjr+Akxvzn9LWDcJ4LI4U8wakiHgBEGlhiIE7zrmS4ZEp8vGKv/Rhk3fOU96eUsoWFyMYtYFtCv5hQBJrqhC5Ur3dvjVzbracSZytn2xrTc+AEngPXu55WN2ebq/LMMTQV0Sq2wbDc7g9Jkxr4apAGDIM= hyakuhei@g.o" |
205 |
</pre> |
206 |
|
207 |
</body> |
208 |
@@ -509,23 +395,31 @@ |
209 |
</body> |
210 |
</section> |
211 |
<section> |
212 |
-<title>7. Giving the developer operator status in #gentoo-dev</title> |
213 |
+<title>7. Setting the developer cloack to gentoo/developer/account</title> |
214 |
<body> |
215 |
|
216 |
<p> |
217 |
-Every developer gets operator status (+o) in <c>#gentoo-dev</c>. In order to do |
218 |
-that, you'll have to use FreeNode's ChanServ. Use the following command: |
219 |
+ Every developer should get a cloak in the form @gentoo/developer/account, |
220 |
+ where in most cases the account is the same as the nickname he uses. |
221 |
+</p> |
222 |
+<p> |
223 |
+ You need to ping our group contacts (mentioned in the topic) on <c>#gentoo-groupcontacts</c> |
224 |
+ and ask for a gentoo/developer cloak. One of them will have to acc the request. After this, |
225 |
+ someone from freenode staff will change the cloak. |
226 |
</p> |
227 |
|
228 |
-<pre caption="Adding the developer to ChanServ's access list"> |
229 |
-[(status)] <i>/msg ChanServ access #gentoo-dev add hyakuhei +vVOriRA</i> |
230 |
-</pre> |
231 |
+</body> |
232 |
+</section> |
233 |
+<section> |
234 |
+<title>8. Developer operator status in #gentoo-dev</title> |
235 |
+<body> |
236 |
|
237 |
<p> |
238 |
-You will see him getting <b>+o</b> by ChanServ. In order to make sure, the |
239 |
-<c>AUTOOP</c> is working, kick the new developer from <c>#gentoo-dev</c> and |
240 |
-wait till he rejoins. If everything is working as it should, he will get the |
241 |
-<b>+o</b> on join by ChanServ. |
242 |
+After freenode staff has changed the cloak for our new dev, he should get |
243 |
++o when joining <c>#gentoo-dev</c>. |
244 |
+In order to make sure, the <c>AUTOOP</c> is working, kick the new developer |
245 |
+from <c>#gentoo-dev</c> and wait till he rejoins. If everything is working |
246 |
+as it should, he will get the <b>+o</b> on join by ChanServ. |
247 |
</p> |
248 |
|
249 |
<p> |