1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) 2007 Free Software Foundation, Inc.
8 "Project-Id-Version: PACKAGE VERSION\n"
9 "Report-Msgid-Bugs-To: \n"
10 "POT-Creation-Date: 2008-08-08 11:36-0300\n"
11 "PO-Revision-Date: 2010-03-29 23:04+0200\n"
12 "Last-Translator: <>\n"
15 "Content-Type: text/plain; charset=UTF-8\n"
16 "Content-Transfer-Encoding: 8bit\n"
18 # type: Content of: <chapter><title>
19 #: new-maintainer.dbk:7
20 msgid "Applying to Become a Maintainer"
21 msgstr "Devenir responsable Debian"
23 # type: Content of: <chapter><section><title>
24 #: new-maintainer.dbk:9
25 msgid "Getting started"
26 msgstr "Pour commencer"
28 # type: Content of: <chapter><section><para>
29 #: new-maintainer.dbk:11
31 "So, you've read all the documentation, you've gone through the <ulink url="
32 "\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, understand "
33 "what everything in the <systemitem role=\"package\">hello</systemitem> "
34 "example package is for, and you're about to Debianize your favorite piece of "
35 "software. How do you actually become a Debian developer so that your work "
36 "can be incorporated into the Project?"
38 "Vous avez lu toute la documentation, vous avez examiné le <ulink url=\"&url-"
39 "newmaint-guide;\">guide du nouveau responsable</ulink>, vous comprenez "
40 "l'intérêt de tout ce qui se trouve dans le paquet d'exemple<systemitem role="
41 "\"package\">hello</systemitem> et vous vous apprêtez à mettre en paquet "
42 "votre logiciel préféré. Comment devenir responsable Debian et intégrer "
43 "votre travail au projet?"
45 # type: Content of: <chapter><section><para>
46 #: new-maintainer.dbk:19
49 "Firstly, subscribe to &email-debian-devel; if you haven't already. Send the "
50 "word <literal>subscribe</literal> in the <literal>Subject</literal> of an "
51 "email to &email-debian-devel-req;. In case of problems, contact the list "
52 "administrator at &email-listmaster;. More information on available mailing "
53 "lists can be found in <xref linkend=\"mailing-lists\"/> . &email-debian-"
54 "devel-announce; is another list which is mandatory for anyone who wishes to "
55 "follow Debian's development."
57 "Si vous ne l'avez pas encore fait, commencez par vous inscrire à la liste "
58 "&email-debian-devel;. Pour cela, envoyez un courrier à l'adresse&email-"
59 "debian-devel-req; avec le mot <literal>subscribe</literal> dans la "
60 "ligne<emphasis>Objet</emphasis><footnote><para><emphasis>Subject</emphasis> "
61 "en anglais</para></footnote>de votre message. En cas de problème, contactez "
62 "l'administrateur de la liste &email-listmaster;. Vous trouverez plus "
63 "d'informations dans la section <xref linkend=\"mailing-lists\"/>. &email-"
64 "debian-devel-announce; est une autre liste incontournable pour qui veut "
65 "suivre les développements de Debian."
67 # type: Content of: <chapter><section><para>
68 #: new-maintainer.dbk:29
70 "You should subscribe and lurk (that is, read without posting) for a bit "
71 "before doing any coding, and you should post about your intentions to work "
72 "on something to avoid duplicated effort."
74 "Vous suivrez les discussions de cette liste (sans poster) pendant quelque "
75 "temps avant de coder quoi que ce soit et vous informerez la liste de votre "
76 "intention de travailler sur quelque chose pour éviter de dupliquer le travail "
79 # type: Content of: <chapter><section><para>
80 #: new-maintainer.dbk:34
82 "Another good list to subscribe to is &email-debian-mentors;. See <xref "
83 "linkend=\"mentors\"/> for details. The IRC channel <literal>#debian</"
84 "literal> can also be helpful; see <xref linkend=\"irc-channels\"/> ."
86 "Une autre liste intéressante est &email-debian-mentors;. Voir la section "
87 "<xref linkend=\"mentors\"/> pour les détails. Le canal IRC<literal>#debian</"
88 "literal> pourra aussi être utile ; voir <xref linkend=\"irc-channels\"/"
91 # type: Content of: <chapter><section><para>
92 #: new-maintainer.dbk:40
94 "When you know how you want to contribute to &debian-formal;, you should get "
95 "in contact with existing Debian maintainers who are working on similar "
96 "tasks. That way, you can learn from experienced developers. For example, "
97 "if you are interested in packaging existing software for Debian, you should "
98 "try to get a sponsor. A sponsor will work together with you on your package "
99 "and upload it to the Debian archive once they are happy with the packaging "
100 "work you have done. You can find a sponsor by mailing the &email-debian-"
101 "mentors; mailing list, describing your package and yourself and asking for a "
102 "sponsor (see <xref linkend=\"sponsoring\"/> and <ulink url=\"&url-mentors;"
103 "\"></ulink> for more information on sponsoring). On the other hand, if you "
104 "are interested in porting Debian to alternative architectures or kernels you "
105 "can subscribe to port specific mailing lists and ask there how to get "
106 "started. Finally, if you are interested in documentation or Quality "
107 "Assurance (QA) work you can join maintainers already working on these tasks "
108 "and submit patches and improvements."
111 # type: Content of: <chapter><section><para>
112 #: new-maintainer.dbk:57
114 "One pitfall could be a too-generic local part in your mailadress: Terms like "
115 "mail, admin, root, master should be avoided, please see <ulink url=\"&url-"
116 "debian-lists;\"></ulink> for details."
119 # type: Content of: <chapter><section><title>
120 #: new-maintainer.dbk:64
121 msgid "Debian mentors and sponsors"
122 msgstr "Mentors et parrains Debian"
124 # type: Content of: <chapter><section><para>
125 #: new-maintainer.dbk:66
127 "The mailing list &email-debian-mentors; has been set up for novice "
128 "maintainers who seek help with initial packaging and other developer-related "
129 "issues. Every new developer is invited to subscribe to that list (see <xref "
130 "linkend=\"mailing-lists\"/> for details)."
133 # type: Content of: <chapter><section><para>
134 #: new-maintainer.dbk:72
136 "Those who prefer one-on-one help (e.g., via private email) should also post "
137 "to that list and an experienced developer will volunteer to help."
144 # type: Content of: <chapter><section><para>
145 #. FIXME - out of order
146 #. Those who are seeking a
147 #. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/"></ulink>.
148 #: new-maintainer.dbk:76
150 "In addition, if you have some packages ready for inclusion in Debian, but "
151 "are waiting for your new maintainer application to go through, you might be "
152 "able find a sponsor to upload your package for you. Sponsors are people who "
153 "are official Debian Developers, and who are willing to criticize and upload "
154 "your packages for you. Please read the unofficial debian-mentors FAQ at "
155 "<ulink url=\"&url-mentors;\"></ulink> first."
158 # type: Content of: <chapter><section><para>
159 #: new-maintainer.dbk:89
161 "If you wish to be a mentor and/or sponsor, more information is available in "
162 "<xref linkend=\"newmaint\"/> ."
165 # type: Content of: <chapter><section><title>
166 #: new-maintainer.dbk:95
167 msgid "Registering as a Debian developer"
170 # type: Content of: <chapter><section><para>
171 #: new-maintainer.dbk:97
173 "Before you decide to register with &debian-formal;, you will need to read "
174 "all the information available at the <ulink url=\"&url-newmaint;\">New "
175 "Maintainer's Corner</ulink>. It describes in detail the preparations you "
176 "have to do before you can register to become a Debian developer. For "
177 "example, before you apply, you have to read the <ulink url=\"&url-social-"
178 "contract;\">Debian Social Contract</ulink>. Registering as a developer "
179 "means that you agree with and pledge to uphold the Debian Social Contract; "
180 "it is very important that maintainers are in accord with the essential ideas "
181 "behind &debian-formal;. Reading the <ulink url=\"&url-gnu-manifesto;\">GNU "
182 "Manifesto</ulink> would also be a good idea."
185 # type: Content of: <chapter><section><para>
186 #: new-maintainer.dbk:111
188 "The process of registering as a developer is a process of verifying your "
189 "identity and intentions, and checking your technical skills. As the number "
190 "of people working on &debian-formal; has grown to over &number-of-"
191 "maintainers; and our systems are used in several very important places, we "
192 "have to be careful about being compromised. Therefore, we need to verify "
193 "new maintainers before we can give them accounts on our servers and let them "
197 # type: Content of: <chapter><section><para>
198 #: new-maintainer.dbk:120
200 "Before you actually register you should have shown that you can do competent "
201 "work and will be a good contributor. You show this by submitting patches "
202 "through the Bug Tracking System and having a package sponsored by an "
203 "existing Debian Developer for a while. Also, we expect that contributors "
204 "are interested in the whole project and not just in maintaining their own "
205 "packages. If you can help other maintainers by providing further "
206 "information on a bug or even a patch, then do so!"
209 # type: Content of: <chapter><section><para>
210 #: new-maintainer.dbk:129
212 "Registration requires that you are familiar with Debian's philosophy and "
213 "technical documentation. Furthermore, you need a GnuPG key which has been "
214 "signed by an existing Debian maintainer. If your GnuPG key is not signed "
215 "yet, you should try to meet a Debian Developer in person to get your key "
216 "signed. There's a <ulink url=\"&url-gpg-coord;\">GnuPG Key Signing "
217 "Coordination page</ulink> which should help you find a Debian Developer "
218 "close to you. (If there is no Debian Developer close to you, alternative "
219 "ways to pass the ID check may be permitted as an absolute exception on a "
220 "case-by-case-basis. See the <ulink url=\"&url-newmaint-id;\">identification "
221 "page</ulink> for more information.)"
224 # type: Content of: <chapter><section><para>
225 #: new-maintainer.dbk:142
227 "If you do not have an OpenPGP key yet, generate one. Every developer needs "
228 "an OpenPGP key in order to sign and verify package uploads. You should read "
229 "the manual for the software you are using, since it has much important "
230 "information which is critical to its security. Many more security failures "
231 "are due to human error than to software failure or high-powered spy "
232 "techniques. See <xref linkend=\"key-maint\"/> for more information on "
233 "maintaining your public key."
236 # type: Content of: <chapter><section><para>
237 #: new-maintainer.dbk:150
239 "Debian uses the <command>GNU Privacy Guard</command> (package <systemitem "
240 "role=\"package\">gnupg</systemitem> version 1 or better) as its baseline "
241 "standard. You can use some other implementation of OpenPGP as well. Note "
242 "that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC "
246 # type: Content of: <chapter><section><para><footnote>
247 #: new-maintainer.dbk:157
249 "You need a version 4 key for use in Debian Development. Your key length "
250 "must be at least 1024 bits; there is no reason to use a smaller key, and "
251 "doing so would be much less secure. <footnote>"
254 # type: Content of: <chapter><section><para><footnote><para>
255 #: new-maintainer.dbk:159
257 "Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC "
258 "2440. Version 4 is the key type that has always been created when using "
259 "GnuPG. PGP versions since 5.x also could create v4 keys, the other choice "
260 "having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
263 # type: Content of: <chapter><section><para><footnote><para>
264 #: new-maintainer.dbk:163
266 "Version 4 (primary) keys can either use the RSA or the DSA algorithms, so "
267 "this has nothing to do with GnuPG's question about which kind of key do you "
268 "want: (1) DSA and Elgamal, (2) DSA (sign only), (5) RSA (sign only). If "
269 "you don't have any special requirements just pick the default."
272 # type: Content of: <chapter><section><para><footnote><para>
273 #: new-maintainer.dbk:167
275 "The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) "
276 "key is to look at the fingerprint: Fingerprints of version 4 keys are the "
277 "SHA-1 hash of some key material, so they are 40 hex digits, usually grouped "
278 "in blocks of 4. Fingerprints of older key format versions used MD5 and are "
279 "generally shown in blocks of 2 hex digits. For example if your fingerprint "
280 "looks like <literal>5B00 C96D 5D54 AEE1 206B AF84 DE7A AF6E 94C0 9C7F</"
281 "literal> then it's a v4 key."
284 # type: Content of: <chapter><section><para><footnote><para>
285 #: new-maintainer.dbk:174
287 "Another possibility is to pipe the key into <command>pgpdump</command>, "
288 "which will say something like Public Key Packet - Ver 4."
291 # type: Content of: <chapter><section><para><footnote><para>
292 #: new-maintainer.dbk:176
294 "Also note that your key must be self-signed (i.e. it has to sign all its "
295 "own user IDs; this prevents user ID tampering). All modern OpenPGP software "
296 "does that automatically, but if you have an older key you may have to "
297 "manually add those signatures."
300 # type: Content of: <chapter><section><para>
301 #: new-maintainer.dbk:179
305 # type: Content of: <chapter><section><para>
306 #: new-maintainer.dbk:182
308 "If your public key isn't on a public key server such as &pgp-keyserv;, "
309 "please read the documentation available at <ulink url=\"&url-newmaint-id;"
310 "\">NM Step 2: Identification</ulink>. That document contains instructions "
311 "on how to put your key on the public key servers. The New Maintainer Group "
312 "will put your public key on the servers if it isn't already there."
315 # type: Content of: <chapter><section><para>
316 #: new-maintainer.dbk:190
318 "Some countries restrict the use of cryptographic software by their "
319 "citizens. This need not impede one's activities as a Debian package "
320 "maintainer however, as it may be perfectly legal to use cryptographic "
321 "products for authentication, rather than encryption purposes. If you live "
322 "in a country where use of cryptography even for authentication is forbidden "
323 "then please contact us so we can make special arrangements."
326 # type: Content of: <chapter><section><para>
327 #: new-maintainer.dbk:198
329 "To apply as a new maintainer, you need an existing Debian Developer to "
330 "support your application (an <literal>advocate</literal>). After you have "
331 "contributed to Debian for a while, and you want to apply to become a "
332 "registered developer, an existing developer with whom you have worked over "
333 "the past months has to express their belief that you can contribute to "
334 "Debian successfully."
337 # type: Content of: <chapter><section><para>
338 #: new-maintainer.dbk:205
340 "When you have found an advocate, have your GnuPG key signed and have already "
341 "contributed to Debian for a while, you're ready to apply. You can simply "
342 "register on our <ulink url=\"&url-newmaint-apply;\">application page</"
343 "ulink>. After you have signed up, your advocate has to confirm your "
344 "application. When your advocate has completed this step you will be "
345 "assigned an Application Manager who will go with you through the necessary "
346 "steps of the New Maintainer process. You can always check your status on "
347 "the <ulink url=\"&url-newmaint-db;\">applications status board</ulink>."
350 # type: Content of: <chapter><section><para>
351 #: new-maintainer.dbk:215
353 "For more details, please consult <ulink url=\"&url-newmaint;\">New "
354 "Maintainer's Corner</ulink> at the Debian web site. Make sure that you are "
355 "familiar with the necessary steps of the New Maintainer process before "
356 "actually applying. If you are well prepared, you can save a lot of time "