1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "POT-Creation-Date: 2011-03-03 11:18-0400\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
19 #. type: Content of: <chapter><title>
20 #: developer-duties.dbk:7
21 msgid "Debian Developer's Duties"
24 #. type: Content of: <chapter><section><title>
25 #: developer-duties.dbk:9
26 msgid "Maintaining your Debian information"
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:24
49 msgid "Maintaining your public key"
52 #. type: Content of: <chapter><section><para>
53 #: developer-duties.dbk:26
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:33
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:39
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:44
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:52
93 "The same key extraction routines discussed in <xref linkend=\"registering\"/"
97 #. type: Content of: <chapter><section><para>
98 #: developer-duties.dbk:56
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:63
110 #. type: Content of: <chapter><section><para>
111 #: developer-duties.dbk:65
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:71
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:77
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:85
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:92
148 msgid "Going on vacation gracefully"
151 #. type: Content of: <chapter><section><para>
152 #: developer-duties.dbk:94
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:101
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><para>
172 #: developer-duties.dbk:110
174 "This is so that the message can be easily filtered by people who don't want "
175 "to read vacation notices."
178 #. type: Content of: <chapter><section><para>
179 #: developer-duties.dbk:108
181 "In order to inform the other developers, there are two things that you "
182 "should do. First send a mail to <email>debian-private@&lists-host;</email> "
183 "with [VAC] prepended to the subject of your message<placeholder type="
184 "\"footnote\" id=\"0\"/> and state the period of time when you will be on "
185 "vacation. You can also give some special instructions on what to do if a "
189 #. type: Content of: <chapter><section><para>
190 #: developer-duties.dbk:117
192 "The other thing to do is to mark yourself as on vacation in the <link "
193 "linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
194 "information is only accessible to Debian developers). Don't forget to "
195 "remove the on vacation flag when you come back!"
198 #. type: Content of: <chapter><section><para>
199 #: developer-duties.dbk:123
201 "Ideally, you should sign up at the <ulink url=\"&url-gpg-coord;\">GPG "
202 "coordination pages</ulink> when booking a holiday and check if anyone there "
203 "is looking for signing. This is especially important when people go to "
204 "exotic places where we don't have any developers yet but where there are "
205 "people who are interested in applying."
208 #. type: Content of: <chapter><section><title>
209 #: developer-duties.dbk:132
210 msgid "Coordination with upstream developers"
213 #. type: Content of: <chapter><section><para>
214 #: developer-duties.dbk:134
216 "A big part of your job as Debian maintainer will be to stay in contact with "
217 "the upstream developers. Debian users will sometimes report bugs that are "
218 "not specific to Debian to our bug tracking system. You have to forward "
219 "these bug reports to the upstream developers so that they can be fixed in a "
220 "future upstream release."
223 #. type: Content of: <chapter><section><para>
224 #: developer-duties.dbk:141
226 "While it's not your job to fix non-Debian specific bugs, you may freely do "
227 "so if you're able. When you make such fixes, be sure to pass them on to the "
228 "upstream maintainers as well. Debian users and developers will sometimes "
229 "submit patches to fix upstream bugs — you should evaluate and forward these "
233 #. type: Content of: <chapter><section><para>
234 #: developer-duties.dbk:148
236 "If you need to modify the upstream sources in order to build a policy "
237 "compliant package, then you should propose a nice fix to the upstream "
238 "developers which can be included there, so that you won't have to modify the "
239 "sources of the next upstream version. Whatever changes you need, always try "
240 "not to fork from the upstream sources."
243 #. type: Content of: <chapter><section><para>
244 #: developer-duties.dbk:155
246 "If you find that the upstream developers are or become hostile towards "
247 "Debian or the free software community, you may want to re-consider the need "
248 "to include the software in Debian. Sometimes the social cost to the Debian "
249 "community is not worth the benefits the software may bring."
252 #. type: Content of: <chapter><section><title>
253 #: developer-duties.dbk:163
254 msgid "Managing release-critical bugs"
257 #. type: Content of: <chapter><section><para>
258 #: developer-duties.dbk:165
260 "Generally you should deal with bug reports on your packages as described in "
261 "<xref linkend=\"bug-handling\"/>. However, there's a special category of "
262 "bugs that you need to take care of — the so-called release-critical bugs (RC "
263 "bugs). All bug reports that have severity <literal>critical</literal>, "
264 "<literal>grave</literal> or <literal>serious</literal> are considered to "
265 "have an impact on whether the package can be released in the next stable "
266 "release of Debian. These bugs can delay the Debian release and/or can "
267 "justify the removal of a package at freeze time. That's why these bugs need "
268 "to be corrected as quickly as possible."
271 #. type: Content of: <chapter><section><para>
272 #: developer-duties.dbk:176
274 "Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality "
275 "Assurance</ulink> group are following all such bugs, and trying to help "
276 "whenever possible. If, for any reason, you aren't able fix an RC bug in a "
277 "package of yours within 2 weeks, you should either ask for help by sending a "
278 "mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
279 "email>, or explain your difficulties and present a plan to fix them by "
280 "sending a mail to the bug report. Otherwise, people from the QA group may "
281 "want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/>) after "
282 "trying to contact you (they might not wait as long as usual before they do "
283 "their NMU if they have seen no recent activity from you in the BTS)."
286 #. type: Content of: <chapter><section><title>
287 #: developer-duties.dbk:191
291 #. type: Content of: <chapter><section><para>
292 #: developer-duties.dbk:193
294 "If you choose to leave the Debian project, you should make sure you do the "
298 #. type: Content of: <chapter><section><orderedlist><listitem><para>
299 #: developer-duties.dbk:199
301 "Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
304 #. type: Content of: <chapter><section><orderedlist><listitem><para>
305 #: developer-duties.dbk:204
307 "Send an gpg-signed email about why you are leaving the project to "
308 "<email>debian-private@&lists-host;</email>."
311 #. type: Content of: <chapter><section><orderedlist><listitem><para>
312 #: developer-duties.dbk:210
314 "Notify the Debian key ring maintainers that you are leaving by opening a "
315 "ticket in Debian RT by sending a mail to &email-keyring; with the words "
316 "'Debian RT' somewhere in the subject line (case doesn't matter)."