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: 2007-07-01 21:16+0000\n"
12 "PO-Revision-Date: 2007-07-01 23:10+0000\n"
13 "Last-Translator: <>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: "
19 # type: Content of: <chapter><title>
20 #: developer-duties.dbk:7
21 msgid "Debian Developer's Duties"
22 msgstr "Les charges du responsable Debian"
24 # type: Content of: <chapter><section><title>
25 #: developer-duties.dbk:9
26 msgid "Maintaining your Debian information"
27 msgstr "Mise à jour de vos références Debian"
29 # type: Content of: <chapter><section><para>
30 #: developer-duties.dbk:11
32 "There's a LDAP database containing information about Debian developers at "
33 "<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information "
34 "there and update it as it changes. Most notably, make sure that the address "
35 "where your debian.org email gets forwarded to is always up to date, as well "
36 "as the address where you get your debian-private subscription if you choose "
40 # type: Content of: <chapter><section><para>
41 #: developer-duties.dbk:19
43 "For more information about the database, please see <xref linkend=\"devel-db"
47 # type: Content of: <chapter><section><title>
48 #: developer-duties.dbk:25
49 msgid "Maintaining your public key"
50 msgstr "Gérer votre clé publique"
52 # type: Content of: <chapter><section><para>
53 #: developer-duties.dbk:27
55 "Be very careful with your private keys. Do not place them on any public "
56 "servers or multiuser machines, such as the Debian servers (see <xref linkend="
57 "\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the "
58 "documentation that comes with your software; read the <ulink url=\"&url-pgp-"
59 "faq;\">PGP FAQ</ulink>."
62 # type: Content of: <chapter><section><para>
63 #: developer-duties.dbk:34
65 "You need to ensure not only that your key is secure against being stolen, "
66 "but also that it is secure against being lost. Generate and make a copy "
67 "(best also in paper form) of your revocation certificate; this is needed if "
71 # type: Content of: <chapter><section><para>
72 #: developer-duties.dbk:40
74 "If you add signatures to your public key, or add user identities, you can "
75 "update the Debian key ring by sending your key to the key server at "
76 "<literal>&keyserver-host;</literal>."
79 # type: Content of: <chapter><section><para>
80 #: developer-duties.dbk:45
82 "If you need to add a completely new key or remove an old key, you need to "
83 "get the new key signed by another developer. If the old key is compromised "
84 "or invalid, you also have to add the revocation certificate. If there is no "
85 "real reason for a new key, the Keyring Maintainers might reject the new "
86 "key. Details can be found at <ulink url=\"http://&keyserver-host;/"
87 "replacing_keys.html\"></ulink>."
90 # type: Content of: <chapter><section><para>
91 #: developer-duties.dbk:53
93 "The same key extraction routines discussed in <xref linkend=\"registering\"/"
97 # type: Content of: <chapter><section><para>
98 #: developer-duties.dbk:57
100 "You can find a more in-depth discussion of Debian key maintenance in the "
101 "documentation of the <systemitem role=\"package\">debian-keyring</"
102 "systemitem> package."
105 # type: Content of: <chapter><section><title>
106 #: developer-duties.dbk:64
110 # type: Content of: <chapter><section><para>
111 #: developer-duties.dbk:66
113 "Even though Debian isn't really a democracy, we use a democratic process to "
114 "elect our leaders and to approve general resolutions. These procedures are "
115 "defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>."
118 # type: Content of: <chapter><section><para>
119 #: developer-duties.dbk:72
121 "Other than the yearly leader election, votes are not routinely held, and "
122 "they are not undertaken lightly. Each proposal is first discussed on the "
123 "&email-debian-vote; mailing list and it requires several endorsements before "
124 "the project secretary starts the voting procedure."
127 # type: Content of: <chapter><section><para>
128 #: developer-duties.dbk:78
130 "You don't have to track the pre-vote discussions, as the secretary will "
131 "issue several calls for votes on &email-debian-devel-announce; (and all "
132 "developers are expected to be subscribed to that list). Democracy doesn't "
133 "work well if people don't take part in the vote, which is why we encourage "
134 "all developers to vote. Voting is conducted via GPG-signed/encrypted email "
138 # type: Content of: <chapter><section><para>
139 #: developer-duties.dbk:86
141 "The list of all proposals (past and current) is available on the <ulink url="
142 "\"&url-vote;\">Debian Voting Information</ulink> page, along with "
143 "information on how to make, second and vote on proposals."
146 # type: Content of: <chapter><section><title>
147 #: developer-duties.dbk:93
148 msgid "Going on vacation gracefully"
151 # type: Content of: <chapter><section><para>
152 #: developer-duties.dbk:95
154 "It is common for developers to have periods of absence, whether those are "
155 "planned vacations or simply being buried in other work. The important thing "
156 "to notice is that other developers need to know that you're on vacation so "
157 "that they can do whatever is needed if a problem occurs with your packages "
158 "or other duties in the project."
161 # type: Content of: <chapter><section><para>
162 #: developer-duties.dbk:102
164 "Usually this means that other developers are allowed to NMU (see <xref "
165 "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
166 "security update, etc.) occurs while you're on vacation. Sometimes it's "
167 "nothing as critical as that, but it's still appropriate to let others know "
168 "that you're unavailable."
171 # type: Content of: <chapter><section><para><footnote>
172 #: developer-duties.dbk:109
174 "In order to inform the other developers, there are two things that you "
175 "should do. First send a mail to <email>debian-private@&lists-host;</email> "
176 "with [VAC] prepended to the subject of your message<footnote>"
179 # type: Content of: <chapter><section><para><footnote><para>
180 #: developer-duties.dbk:111
182 "This is so that the message can be easily filtered by people who don't want "
183 "to read vacation notices."
186 # type: Content of: <chapter><section><para>
187 #: developer-duties.dbk:113
189 "</footnote> and state the period of time when you will be on vacation. You "
190 "can also give some special instructions on what to do if a problem occurs."
193 # type: Content of: <chapter><section><para>
194 #: developer-duties.dbk:118
196 "The other thing to do is to mark yourself as on vacation in the <link "
197 "linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
198 "information is only accessible to Debian developers). Don't forget to "
199 "remove the on vacation flag when you come back!"
202 # type: Content of: <chapter><section><para>
203 #: developer-duties.dbk:124
205 "Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php"
206 "\">GPG coordination site</ulink> when booking a holiday and check if anyone "
207 "there is looking for signing. This is especially important when people go "
208 "to exotic places where we don't have any developers yet but where there are "
209 "people who are interested in applying."
212 # type: Content of: <chapter><section><title>
213 #: developer-duties.dbk:133
214 msgid "Coordination with upstream developers"
217 # type: Content of: <chapter><section><para>
218 #: developer-duties.dbk:135
220 "A big part of your job as Debian maintainer will be to stay in contact with "
221 "the upstream developers. Debian users will sometimes report bugs that are "
222 "not specific to Debian to our bug tracking system. You have to forward "
223 "these bug reports to the upstream developers so that they can be fixed in a "
224 "future upstream release."
227 # type: Content of: <chapter><section><para>
228 #: developer-duties.dbk:142
230 "While it's not your job to fix non-Debian specific bugs, you may freely do "
231 "so if you're able. When you make such fixes, be sure to pass them on to the "
232 "upstream maintainers as well. Debian users and developers will sometimes "
233 "submit patches to fix upstream bugs — you should evaluate and forward these "
237 # type: Content of: <chapter><section><para>
238 #: developer-duties.dbk:149
240 "If you need to modify the upstream sources in order to build a policy "
241 "compliant package, then you should propose a nice fix to the upstream "
242 "developers which can be included there, so that you won't have to modify the "
243 "sources of the next upstream version. Whatever changes you need, always try "
244 "not to fork from the upstream sources."
247 # type: Content of: <chapter><section><title>
248 #: developer-duties.dbk:158
249 msgid "Managing release-critical bugs"
252 # type: Content of: <chapter><section><para>
253 #: developer-duties.dbk:160
255 "Generally you should deal with bug reports on your packages as described in "
256 "<xref linkend=\"bug-handling\"/> . However, there's a special category of "
257 "bugs that you need to take care of — the so-called release-critical bugs (RC "
258 "bugs). All bug reports that have severity <emphasis>critical</emphasis>, "
259 "<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to "
260 "have an impact on whether the package can be released in the next stable "
261 "release of Debian. These bugs can delay the Debian release and/or can "
262 "justify the removal of a package at freeze time. That's why these bugs need "
263 "to be corrected as quickly as possible."
266 # type: Content of: <chapter><section><para>
267 #: developer-duties.dbk:171
269 "Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality "
270 "Assurance</ulink> group are following all such bugs, and trying to help "
271 "whenever possible. If, for any reason, you aren't able fix an RC bug in a "
272 "package of yours within 2 weeks, you should either ask for help by sending a "
273 "mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
274 "email>, or explain your difficulties and present a plan to fix them by "
275 "sending a mail to the bug report. Otherwise, people from the QA group may "
276 "want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after "
277 "trying to contact you (they might not wait as long as usual before they do "
278 "their NMU if they have seen no recent activity from you in the BTS)."
281 # type: Content of: <chapter><section><title>
282 #: developer-duties.dbk:186
286 # type: Content of: <chapter><section><para>
287 #: developer-duties.dbk:188
289 "If you choose to leave the Debian project, you should make sure you do the "
293 # type: Content of: <chapter><section><orderedlist><listitem><para>
294 #: developer-duties.dbk:194
296 "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
299 # type: Content of: <chapter><section><orderedlist><listitem><para>
300 #: developer-duties.dbk:199
302 "Send an gpg-signed email about why you are leaving the project to "
303 "<email>debian-private@&lists-host;</email>."
306 # type: Content of: <chapter><section><orderedlist><listitem><para>
307 #: developer-duties.dbk:205
309 "Notify the Debian key ring maintainers that you are leaving by opening a "
310 "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
311 "words 'Debian RT' somewhere in the subject line (case doesn't matter)."