1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
8 "Project-Id-Version: PACKAGE VERSION\n"
9 "POT-Creation-Date: 2007-06-26 16:13+0000\n"
10 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
11 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12 "Language-Team: LANGUAGE <LL@li.org>\n"
14 "Content-Type: text/plain; charset=utf-8\n"
15 "Content-Transfer-Encoding: ENCODING"
17 # type: Content of: <chapter><title>
18 #: developer-duties.dbk:5
19 msgid "Debian Developer's Duties"
22 # type: Content of: <chapter><section><title>
23 #: developer-duties.dbk:7
24 msgid "Maintaining your Debian information"
27 # type: Content of: <chapter><section><para>
28 #: developer-duties.dbk:9
30 "There's a LDAP database containing information about Debian developers at "
31 "<ulink url=\"https://db.debian.org/\"></ulink>. You should enter your "
32 "information there and update it as it changes. Most notably, make sure that "
33 "the address where your debian.org email gets forwarded to is always up to "
34 "date, as well as the address where you get your debian-private subscription "
35 "if you choose to subscribe there."
38 # type: Content of: <chapter><section><para>
39 #: developer-duties.dbk:17
41 "For more information about the database, please see <xref "
42 "linkend=\"devel-db\"/> ."
45 # type: Content of: <chapter><section><title>
46 #: developer-duties.dbk:23
47 msgid "Maintaining your public key"
50 # type: Content of: <chapter><section><para>
51 #: developer-duties.dbk:25
53 "Be very careful with your private keys. Do not place them on any public "
54 "servers or multiuser machines, such as the Debian servers (see <xref "
55 "linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. "
56 "Read the documentation that comes with your software; read the <ulink "
57 "url=\"http://www.cam.ac.uk.pgp.net/pgpnet/pgp-faq/\">PGP FAQ</ulink>."
60 # type: Content of: <chapter><section><para>
61 #: developer-duties.dbk:32
63 "You need to ensure not only that your key is secure against being stolen, "
64 "but also that it is secure against being lost. Generate and make a copy "
65 "(best also in paper form) of your revocation certificate; this is needed if "
69 # type: Content of: <chapter><section><para>
70 #: developer-duties.dbk:38
72 "If you add signatures to your public key, or add user identities, you can "
73 "update the Debian key ring by sending your key to the key server at "
74 "<literal>keyring.debian.org</literal>."
77 # type: Content of: <chapter><section><para>
78 #: developer-duties.dbk:43
80 "If you need to add a completely new key or remove an old key, you need to "
81 "get the new key signed by another developer. If the old key is compromised "
82 "or invalid, you also have to add the revocation certificate. If there is no "
83 "real reason for a new key, the Keyring Maintainers might reject the new "
84 "key. Details can be found at <ulink "
85 "url=\"http://keyring.debian.org/replacing_keys.html\"></ulink>."
88 # type: Content of: <chapter><section><para>
89 #: developer-duties.dbk:51
91 "The same key extraction routines discussed in <xref "
92 "linkend=\"registering\"/> apply."
95 # type: Content of: <chapter><section><para>
96 #: developer-duties.dbk:55
98 "You can find a more in-depth discussion of Debian key maintenance in the "
99 "documentation of the <systemitem "
100 "role=\"package\">debian-keyring</systemitem> package."
103 # type: Content of: <chapter><section><title>
104 #: developer-duties.dbk:62
108 # type: Content of: <chapter><section><para>
109 #: developer-duties.dbk:64
111 "Even though Debian isn't really a democracy, we use a democratic process to "
112 "elect our leaders and to approve general resolutions. These procedures are "
113 "defined by the <ulink "
114 "url=\"http://www.debian.org/devel/constitution\">Debian "
115 "Constitution</ulink>."
118 # type: Content of: <chapter><section><para>
119 #: developer-duties.dbk:70
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@lists.debian.org</email> mailing list and it requires "
124 "several endorsements before the project secretary starts the voting "
128 # type: Content of: <chapter><section><para>
129 #: developer-duties.dbk:76
131 "You don't have to track the pre-vote discussions, as the secretary will "
132 "issue several calls for votes on "
133 "<email>debian-devel-announce@lists.debian.org</email> (and all developers "
134 "are expected to be subscribed to that list). Democracy doesn't work well if "
135 "people don't take part in the vote, which is why we encourage all developers "
136 "to vote. Voting is conducted via GPG-signed/encrypted email messages."
139 # type: Content of: <chapter><section><para>
140 #: developer-duties.dbk:84
142 "The list of all proposals (past and current) is available on the <ulink "
143 "url=\"http://www.debian.org/vote/\">Debian Voting Information</ulink> page, "
144 "along with information on how to make, second and vote on proposals."
147 # type: Content of: <chapter><section><title>
148 #: developer-duties.dbk:91
149 msgid "Going on vacation gracefully"
152 # type: Content of: <chapter><section><para>
153 #: developer-duties.dbk:93
155 "It is common for developers to have periods of absence, whether those are "
156 "planned vacations or simply being buried in other work. The important thing "
157 "to notice is that other developers need to know that you're on vacation so "
158 "that they can do whatever is needed if a problem occurs with your packages "
159 "or other duties in the project."
162 # type: Content of: <chapter><section><para>
163 #: developer-duties.dbk:100
165 "Usually this means that other developers are allowed to NMU (see <xref "
166 "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
167 "security update, etc.) occurs while you're on vacation. Sometimes it's "
168 "nothing as critical as that, but it's still appropriate to let others know "
169 "that you're unavailable."
172 # type: Content of: <chapter><section><para><footnote>
173 #: developer-duties.dbk:107
175 "In order to inform the other developers, there are two things that you "
176 "should do. First send a mail to "
177 "<email>debian-private@lists.debian.org</email> with [VAC] prepended to the "
178 "subject of your message<footnote>"
181 # type: Content of: <chapter><section><para><footnote><para>
182 #: developer-duties.dbk:109
184 "This is so that the message can be easily filtered by people who don't want "
185 "to read vacation notices."
188 # type: Content of: <chapter><section><para>
189 #: developer-duties.dbk:111
191 "</footnote> and state the period of time when you will be on vacation. You "
192 "can also give some special instructions on what to do if a problem occurs."
195 # type: Content of: <chapter><section><para>
196 #: developer-duties.dbk:116
198 "The other thing to do is to mark yourself as on vacation in the <link "
199 "linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
200 "information is only accessible to Debian developers). Don't forget to "
201 "remove the on vacation flag when you come back!"
204 # type: Content of: <chapter><section><para>
205 #: developer-duties.dbk:122
207 "Ideally, you should sign up at the <ulink "
208 "url=\"http://nm.debian.org/gpg.php\">GPG coordination site</ulink> when "
209 "booking a holiday and check if anyone there is looking for signing. This is "
210 "especially important when people go to exotic places where we don't have any "
211 "developers yet but where there are people who are interested in applying."
214 # type: Content of: <chapter><section><title>
215 #: developer-duties.dbk:131
216 msgid "Coordination with upstream developers"
219 # type: Content of: <chapter><section><para>
220 #: developer-duties.dbk:133
222 "A big part of your job as Debian maintainer will be to stay in contact with "
223 "the upstream developers. Debian users will sometimes report bugs that are "
224 "not specific to Debian to our bug tracking system. You have to forward "
225 "these bug reports to the upstream developers so that they can be fixed in a "
226 "future upstream release."
229 # type: Content of: <chapter><section><para>
230 #: developer-duties.dbk:140
232 "While it's not your job to fix non-Debian specific bugs, you may freely do "
233 "so if you're able. When you make such fixes, be sure to pass them on to the "
234 "upstream maintainers as well. Debian users and developers will sometimes "
235 "submit patches to fix upstream bugs — you should evaluate and forward these "
239 # type: Content of: <chapter><section><para>
240 #: developer-duties.dbk:147
242 "If you need to modify the upstream sources in order to build a policy "
243 "compliant package, then you should propose a nice fix to the upstream "
244 "developers which can be included there, so that you won't have to modify the "
245 "sources of the next upstream version. Whatever changes you need, always try "
246 "not to fork from the upstream sources."
249 # type: Content of: <chapter><section><title>
250 #: developer-duties.dbk:156
251 msgid "Managing release-critical bugs"
254 # type: Content of: <chapter><section><para>
255 #: developer-duties.dbk:158
257 "Generally you should deal with bug reports on your packages as described in "
258 "<xref linkend=\"bug-handling\"/> . However, there's a special category of "
259 "bugs that you need to take care of — the so-called release-critical bugs (RC "
260 "bugs). All bug reports that have severity <emphasis>critical</emphasis>, "
261 "<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to "
262 "have an impact on whether the package can be released in the next stable "
263 "release of Debian. These bugs can delay the Debian release and/or can "
264 "justify the removal of a package at freeze time. That's why these bugs need "
265 "to be corrected as quickly as possible."
268 # type: Content of: <chapter><section><para>
269 #: developer-duties.dbk:169
271 "Developers who are part of the <ulink url=\"http://qa.debian.org/\">Quality "
272 "Assurance</ulink> group are following all such bugs, and trying to help "
273 "whenever possible. If, for any reason, you aren't able fix an RC bug in a "
274 "package of yours within 2 weeks, you should either ask for help by sending a "
275 "mail to the Quality Assurance (QA) group "
276 "<email>debian-qa@lists.debian.org</email>, or explain your difficulties and "
277 "present a plan to fix them by sending a mail to the bug report. Otherwise, "
278 "people from the QA group may want to do a Non-Maintainer Upload (see <xref "
279 "linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long "
280 "as usual before they do their NMU if they have seen no recent activity from "
284 # type: Content of: <chapter><section><title>
285 #: developer-duties.dbk:184
289 # type: Content of: <chapter><section><para>
290 #: developer-duties.dbk:186
292 "If you choose to leave the Debian project, you should make sure you do the "
296 # type: Content of: <chapter><section><orderedlist><listitem><para>
297 #: developer-duties.dbk:192
298 msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
301 # type: Content of: <chapter><section><orderedlist><listitem><para>
302 #: developer-duties.dbk:197
304 "Send an gpg-signed email about why you are leaving the project to "
305 "<email>debian-private@lists.debian.org</email>."
308 # type: Content of: <chapter><section><orderedlist><listitem><para>
309 #: developer-duties.dbk:203
311 "Notify the Debian key ring maintainers that you are leaving by opening a "
312 "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
313 "words 'Debian RT' somewhere in the subject line (case doesn't matter)."