1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) 2007 Free Software Foundation, Inc.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "Report-Msgid-Bugs-To: \n"
11 "POT-Creation-Date: 2010-05-27 11:15-0400\n"
12 "PO-Revision-Date: 2007-07-01 23:10+0000\n"
13 "Last-Translator: <>\n"
17 "Content-Type: text/plain; charset=UTF-8\n"
18 "Content-Transfer-Encoding: \n"
20 # type: Content of: <chapter><title>
21 #. type: Content of: <chapter><title>
22 #: developer-duties.dbk:7
23 msgid "Debian Developer's Duties"
24 msgstr "Les charges du responsable Debian"
26 # type: Content of: <chapter><section><title>
27 #. type: Content of: <chapter><section><title>
28 #: developer-duties.dbk:9
29 msgid "Maintaining your Debian information"
30 msgstr "Mise à jour de vos références Debian"
32 # type: Content of: <chapter><section><para>
33 #. type: Content of: <chapter><section><para>
34 #: developer-duties.dbk:11
36 "There's a LDAP database containing information about Debian developers at "
37 "<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information "
38 "there and update it as it changes. Most notably, make sure that the address "
39 "where your debian.org email gets forwarded to is always up to date, as well "
40 "as the address where you get your debian-private subscription if you choose "
44 # type: Content of: <chapter><section><para>
45 #. type: Content of: <chapter><section><para>
46 #: developer-duties.dbk:19
48 "For more information about the database, please see <xref linkend=\"devel-db"
52 # type: Content of: <chapter><section><title>
53 #. type: Content of: <chapter><section><title>
54 #: developer-duties.dbk:25
55 msgid "Maintaining your public key"
56 msgstr "Gérer votre clé publique"
58 # type: Content of: <chapter><section><para>
59 #. type: Content of: <chapter><section><para>
60 #: developer-duties.dbk:27
62 "Be very careful with your private keys. Do not place them on any public "
63 "servers or multiuser machines, such as the Debian servers (see <xref linkend="
64 "\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the "
65 "documentation that comes with your software; read the <ulink url=\"&url-pgp-"
66 "faq;\">PGP FAQ</ulink>."
69 # type: Content of: <chapter><section><para>
70 #. type: Content of: <chapter><section><para>
71 #: developer-duties.dbk:34
73 "You need to ensure not only that your key is secure against being stolen, "
74 "but also that it is secure against being lost. Generate and make a copy "
75 "(best also in paper form) of your revocation certificate; this is needed if "
79 # type: Content of: <chapter><section><para>
80 #. type: Content of: <chapter><section><para>
81 #: developer-duties.dbk:40
83 "If you add signatures to your public key, or add user identities, you can "
84 "update the Debian key ring by sending your key to the key server at "
85 "<literal>&keyserver-host;</literal>."
88 # type: Content of: <chapter><section><para>
89 #. type: Content of: <chapter><section><para>
90 #: developer-duties.dbk:45
92 "If you need to add a completely new key or remove an old key, you need to "
93 "get the new key signed by another developer. If the old key is compromised "
94 "or invalid, you also have to add the revocation certificate. If there is no "
95 "real reason for a new key, the Keyring Maintainers might reject the new "
96 "key. Details can be found at <ulink url=\"http://&keyserver-host;/"
97 "replacing_keys.html\"></ulink>."
100 # type: Content of: <chapter><section><para>
101 #. type: Content of: <chapter><section><para>
102 #: developer-duties.dbk:53
104 "The same key extraction routines discussed in <xref linkend=\"registering\"/"
108 # type: Content of: <chapter><section><para>
109 #. type: Content of: <chapter><section><para>
110 #: developer-duties.dbk:57
112 "You can find a more in-depth discussion of Debian key maintenance in the "
113 "documentation of the <systemitem role=\"package\">debian-keyring</"
114 "systemitem> package."
117 # type: Content of: <chapter><section><title>
118 #. type: Content of: <chapter><section><title>
119 #: developer-duties.dbk:64
123 # type: Content of: <chapter><section><para>
124 #. type: Content of: <chapter><section><para>
125 #: developer-duties.dbk:66
127 "Even though Debian isn't really a democracy, we use a democratic process to "
128 "elect our leaders and to approve general resolutions. These procedures are "
129 "defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>."
132 # type: Content of: <chapter><section><para>
133 #. type: Content of: <chapter><section><para>
134 #: developer-duties.dbk:72
136 "Other than the yearly leader election, votes are not routinely held, and "
137 "they are not undertaken lightly. Each proposal is first discussed on the "
138 "&email-debian-vote; mailing list and it requires several endorsements before "
139 "the project secretary starts the voting procedure."
142 # type: Content of: <chapter><section><para>
143 #. type: Content of: <chapter><section><para>
144 #: developer-duties.dbk:78
146 "You don't have to track the pre-vote discussions, as the secretary will "
147 "issue several calls for votes on &email-debian-devel-announce; (and all "
148 "developers are expected to be subscribed to that list). Democracy doesn't "
149 "work well if people don't take part in the vote, which is why we encourage "
150 "all developers to vote. Voting is conducted via GPG-signed/encrypted email "
154 # type: Content of: <chapter><section><para>
155 #. type: Content of: <chapter><section><para>
156 #: developer-duties.dbk:86
158 "The list of all proposals (past and current) is available on the <ulink url="
159 "\"&url-vote;\">Debian Voting Information</ulink> page, along with "
160 "information on how to make, second and vote on proposals."
163 # type: Content of: <chapter><section><title>
164 #. type: Content of: <chapter><section><title>
165 #: developer-duties.dbk:93
166 msgid "Going on vacation gracefully"
169 # type: Content of: <chapter><section><para>
170 #. type: Content of: <chapter><section><para>
171 #: developer-duties.dbk:95
173 "It is common for developers to have periods of absence, whether those are "
174 "planned vacations or simply being buried in other work. The important thing "
175 "to notice is that other developers need to know that you're on vacation so "
176 "that they can do whatever is needed if a problem occurs with your packages "
177 "or other duties in the project."
180 # type: Content of: <chapter><section><para>
181 #. type: Content of: <chapter><section><para>
182 #: developer-duties.dbk:102
184 "Usually this means that other developers are allowed to NMU (see <xref "
185 "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
186 "security update, etc.) occurs while you're on vacation. Sometimes it's "
187 "nothing as critical as that, but it's still appropriate to let others know "
188 "that you're unavailable."
191 # type: Content of: <chapter><section><para><footnote><para>
192 #. type: Content of: <chapter><section><para><footnote><para>
193 #: developer-duties.dbk:111
195 "This is so that the message can be easily filtered by people who don't want "
196 "to read vacation notices."
199 #. type: Content of: <chapter><section><para>
200 #: developer-duties.dbk:109
202 "In order to inform the other developers, there are two things that you "
203 "should do. First send a mail to <email>debian-private@&lists-host;</email> "
204 "with [VAC] prepended to the subject of your message<placeholder type="
205 "\"footnote\" id=\"0\"/> and state the period of time when you will be on "
206 "vacation. You can also give some special instructions on what to do if a "
210 # type: Content of: <chapter><section><para>
211 #. type: Content of: <chapter><section><para>
212 #: developer-duties.dbk:118
214 "The other thing to do is to mark yourself as on vacation in the <link "
215 "linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
216 "information is only accessible to Debian developers). Don't forget to "
217 "remove the on vacation flag when you come back!"
220 # type: Content of: <chapter><section><para>
221 #. type: Content of: <chapter><section><para>
222 #: developer-duties.dbk:124
224 "Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php"
225 "\">GPG coordination site</ulink> when booking a holiday and check if anyone "
226 "there is looking for signing. This is especially important when people go "
227 "to exotic places where we don't have any developers yet but where there are "
228 "people who are interested in applying."
231 # type: Content of: <chapter><section><title>
232 #. type: Content of: <chapter><section><title>
233 #: developer-duties.dbk:133
234 msgid "Coordination with upstream developers"
237 # type: Content of: <chapter><section><para>
238 #. type: Content of: <chapter><section><para>
239 #: developer-duties.dbk:135
241 "A big part of your job as Debian maintainer will be to stay in contact with "
242 "the upstream developers. Debian users will sometimes report bugs that are "
243 "not specific to Debian to our bug tracking system. You have to forward "
244 "these bug reports to the upstream developers so that they can be fixed in a "
245 "future upstream release."
248 # type: Content of: <chapter><section><para>
249 #. type: Content of: <chapter><section><para>
250 #: developer-duties.dbk:142
252 "While it's not your job to fix non-Debian specific bugs, you may freely do "
253 "so if you're able. When you make such fixes, be sure to pass them on to the "
254 "upstream maintainers as well. Debian users and developers will sometimes "
255 "submit patches to fix upstream bugs — you should evaluate and forward these "
259 # type: Content of: <chapter><section><para>
260 #. type: Content of: <chapter><section><para>
261 #: developer-duties.dbk:149
263 "If you need to modify the upstream sources in order to build a policy "
264 "compliant package, then you should propose a nice fix to the upstream "
265 "developers which can be included there, so that you won't have to modify the "
266 "sources of the next upstream version. Whatever changes you need, always try "
267 "not to fork from the upstream sources."
270 #. type: Content of: <chapter><section><para>
271 #: developer-duties.dbk:156
273 "If you find that the upstream developers are or become hostile towards "
274 "Debian or the free software community, you may want to re-consider the need "
275 "to include the software in Debian. Sometimes the social cost to the Debian "
276 "community is not worth the benefits the software may bring."
279 # type: Content of: <chapter><section><title>
280 #. type: Content of: <chapter><section><title>
281 #: developer-duties.dbk:164
282 msgid "Managing release-critical bugs"
285 # type: Content of: <chapter><section><para>
286 #. type: Content of: <chapter><section><para>
287 #: developer-duties.dbk:166
289 "Generally you should deal with bug reports on your packages as described in "
290 "<xref linkend=\"bug-handling\"/> . However, there's a special category of "
291 "bugs that you need to take care of — the so-called release-critical bugs (RC "
292 "bugs). All bug reports that have severity <literal>critical</literal>, "
293 "<literal>grave</literal> or <literal>serious</literal> are considered to "
294 "have an impact on whether the package can be released in the next stable "
295 "release of Debian. These bugs can delay the Debian release and/or can "
296 "justify the removal of a package at freeze time. That's why these bugs need "
297 "to be corrected as quickly as possible."
300 # type: Content of: <chapter><section><para>
301 #. type: Content of: <chapter><section><para>
302 #: developer-duties.dbk:177
304 "Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality "
305 "Assurance</ulink> group are following all such bugs, and trying to help "
306 "whenever possible. If, for any reason, you aren't able fix an RC bug in a "
307 "package of yours within 2 weeks, you should either ask for help by sending a "
308 "mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
309 "email>, or explain your difficulties and present a plan to fix them by "
310 "sending a mail to the bug report. Otherwise, people from the QA group may "
311 "want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after "
312 "trying to contact you (they might not wait as long as usual before they do "
313 "their NMU if they have seen no recent activity from you in the BTS)."
316 # type: Content of: <chapter><section><title>
317 #. type: Content of: <chapter><section><title>
318 #: developer-duties.dbk:192
322 # type: Content of: <chapter><section><para>
323 #. type: Content of: <chapter><section><para>
324 #: developer-duties.dbk:194
326 "If you choose to leave the Debian project, you should make sure you do the "
330 # type: Content of: <chapter><section><orderedlist><listitem><para>
331 #. type: Content of: <chapter><section><orderedlist><listitem><para>
332 #: developer-duties.dbk:200
334 "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
337 # type: Content of: <chapter><section><orderedlist><listitem><para>
338 #. type: Content of: <chapter><section><orderedlist><listitem><para>
339 #: developer-duties.dbk:205
341 "Send an gpg-signed email about why you are leaving the project to "
342 "<email>debian-private@&lists-host;</email>."
345 # type: Content of: <chapter><section><orderedlist><listitem><para>
346 #. type: Content of: <chapter><section><orderedlist><listitem><para>
347 #: developer-duties.dbk:211
349 "Notify the Debian key ring maintainers that you are leaving by opening a "
350 "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
351 "words 'Debian RT' somewhere in the subject line (case doesn't matter)."