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-07-01 21:18+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\n"
17 # type: Content of: <chapter><title>
18 #: developer-duties.dbk:7
19 msgid "Debian Developer's Duties"
22 # type: Content of: <chapter><section><title>
23 #: developer-duties.dbk:9
24 msgid "Maintaining your Debian information"
27 # type: Content of: <chapter><section><para>
28 #: developer-duties.dbk:11
30 "There's a LDAP database containing information about Debian developers at "
31 "<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information "
32 "there and update it as it changes. Most notably, make sure that the address "
33 "where your debian.org email gets forwarded to is always up to date, as well "
34 "as the address where you get your debian-private subscription if you choose "
38 # type: Content of: <chapter><section><para>
39 #: developer-duties.dbk:19
41 "For more information about the database, please see <xref linkend=\"devel-db"
45 # type: Content of: <chapter><section><title>
46 #: developer-duties.dbk:25
47 msgid "Maintaining your public key"
50 # type: Content of: <chapter><section><para>
51 #: developer-duties.dbk:27
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 linkend="
55 "\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the "
56 "documentation that comes with your software; read the <ulink url=\"&url-pgp-"
57 "faq;\">PGP FAQ</ulink>."
60 # type: Content of: <chapter><section><para>
61 #: developer-duties.dbk:34
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:40
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>&keyserver-host;</literal>."
77 # type: Content of: <chapter><section><para>
78 #: developer-duties.dbk:45
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 url=\"http://&keyserver-host;/"
85 "replacing_keys.html\"></ulink>."
88 # type: Content of: <chapter><section><para>
89 #: developer-duties.dbk:53
91 "The same key extraction routines discussed in <xref linkend=\"registering\"/"
95 # type: Content of: <chapter><section><para>
96 #: developer-duties.dbk:57
98 "You can find a more in-depth discussion of Debian key maintenance in the "
99 "documentation of the <systemitem role=\"package\">debian-keyring</"
100 "systemitem> package."
103 # type: Content of: <chapter><section><title>
104 #: developer-duties.dbk:64
108 # type: Content of: <chapter><section><para>
109 #: developer-duties.dbk:66
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 url=\"&url-constitution;\">Debian Constitution</ulink>."
116 # type: Content of: <chapter><section><para>
117 #: developer-duties.dbk:72
119 "Other than the yearly leader election, votes are not routinely held, and "
120 "they are not undertaken lightly. Each proposal is first discussed on the "
121 "&email-debian-vote; mailing list and it requires several endorsements before "
122 "the project secretary starts the voting procedure."
125 # type: Content of: <chapter><section><para>
126 #: developer-duties.dbk:78
128 "You don't have to track the pre-vote discussions, as the secretary will "
129 "issue several calls for votes on &email-debian-devel-announce; (and all "
130 "developers are expected to be subscribed to that list). Democracy doesn't "
131 "work well if people don't take part in the vote, which is why we encourage "
132 "all developers to vote. Voting is conducted via GPG-signed/encrypted email "
136 # type: Content of: <chapter><section><para>
137 #: developer-duties.dbk:86
139 "The list of all proposals (past and current) is available on the <ulink url="
140 "\"&url-vote;\">Debian Voting Information</ulink> page, along with "
141 "information on how to make, second and vote on proposals."
144 # type: Content of: <chapter><section><title>
145 #: developer-duties.dbk:93
146 msgid "Going on vacation gracefully"
149 # type: Content of: <chapter><section><para>
150 #: developer-duties.dbk:95
152 "It is common for developers to have periods of absence, whether those are "
153 "planned vacations or simply being buried in other work. The important thing "
154 "to notice is that other developers need to know that you're on vacation so "
155 "that they can do whatever is needed if a problem occurs with your packages "
156 "or other duties in the project."
159 # type: Content of: <chapter><section><para>
160 #: developer-duties.dbk:102
162 "Usually this means that other developers are allowed to NMU (see <xref "
163 "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
164 "security update, etc.) occurs while you're on vacation. Sometimes it's "
165 "nothing as critical as that, but it's still appropriate to let others know "
166 "that you're unavailable."
169 # type: Content of: <chapter><section><para><footnote>
170 #: developer-duties.dbk:109
172 "In order to inform the other developers, there are two things that you "
173 "should do. First send a mail to <email>debian-private@&lists-host;</email> "
174 "with [VAC] prepended to the subject of your message<footnote>"
177 # type: Content of: <chapter><section><para><footnote><para>
178 #: developer-duties.dbk:111
180 "This is so that the message can be easily filtered by people who don't want "
181 "to read vacation notices."
184 # type: Content of: <chapter><section><para>
185 #: developer-duties.dbk:113
187 "</footnote> and state the period of time when you will be on vacation. You "
188 "can also give some special instructions on what to do if a problem occurs."
191 # type: Content of: <chapter><section><para>
192 #: developer-duties.dbk:118
194 "The other thing to do is to mark yourself as on vacation in the <link "
195 "linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
196 "information is only accessible to Debian developers). Don't forget to "
197 "remove the on vacation flag when you come back!"
200 # type: Content of: <chapter><section><para>
201 #: developer-duties.dbk:124
203 "Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php"
204 "\">GPG coordination site</ulink> when booking a holiday and check if anyone "
205 "there is looking for signing. This is especially important when people go "
206 "to exotic places where we don't have any developers yet but where there are "
207 "people who are interested in applying."
210 # type: Content of: <chapter><section><title>
211 #: developer-duties.dbk:133
212 msgid "Coordination with upstream developers"
215 # type: Content of: <chapter><section><para>
216 #: developer-duties.dbk:135
218 "A big part of your job as Debian maintainer will be to stay in contact with "
219 "the upstream developers. Debian users will sometimes report bugs that are "
220 "not specific to Debian to our bug tracking system. You have to forward "
221 "these bug reports to the upstream developers so that they can be fixed in a "
222 "future upstream release."
225 # type: Content of: <chapter><section><para>
226 #: developer-duties.dbk:142
228 "While it's not your job to fix non-Debian specific bugs, you may freely do "
229 "so if you're able. When you make such fixes, be sure to pass them on to the "
230 "upstream maintainers as well. Debian users and developers will sometimes "
231 "submit patches to fix upstream bugs — you should evaluate and forward these "
235 # type: Content of: <chapter><section><para>
236 #: developer-duties.dbk:149
238 "If you need to modify the upstream sources in order to build a policy "
239 "compliant package, then you should propose a nice fix to the upstream "
240 "developers which can be included there, so that you won't have to modify the "
241 "sources of the next upstream version. Whatever changes you need, always try "
242 "not to fork from the upstream sources."
245 # type: Content of: <chapter><section><title>
246 #: developer-duties.dbk:158
247 msgid "Managing release-critical bugs"
250 # type: Content of: <chapter><section><para>
251 #: developer-duties.dbk:160
253 "Generally you should deal with bug reports on your packages as described in "
254 "<xref linkend=\"bug-handling\"/> . However, there's a special category of "
255 "bugs that you need to take care of — the so-called release-critical bugs (RC "
256 "bugs). All bug reports that have severity <emphasis>critical</emphasis>, "
257 "<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to "
258 "have an impact on whether the package can be released in the next stable "
259 "release of Debian. These bugs can delay the Debian release and/or can "
260 "justify the removal of a package at freeze time. That's why these bugs need "
261 "to be corrected as quickly as possible."
264 # type: Content of: <chapter><section><para>
265 #: developer-duties.dbk:171
267 "Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality "
268 "Assurance</ulink> group are following all such bugs, and trying to help "
269 "whenever possible. If, for any reason, you aren't able fix an RC bug in a "
270 "package of yours within 2 weeks, you should either ask for help by sending a "
271 "mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
272 "email>, or explain your difficulties and present a plan to fix them by "
273 "sending a mail to the bug report. Otherwise, people from the QA group may "
274 "want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after "
275 "trying to contact you (they might not wait as long as usual before they do "
276 "their NMU if they have seen no recent activity from you in the BTS)."
279 # type: Content of: <chapter><section><title>
280 #: developer-duties.dbk:186
284 # type: Content of: <chapter><section><para>
285 #: developer-duties.dbk:188
287 "If you choose to leave the Debian project, you should make sure you do the "
291 # type: Content of: <chapter><section><orderedlist><listitem><para>
292 #: developer-duties.dbk:194
294 "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
297 # type: Content of: <chapter><section><orderedlist><listitem><para>
298 #: developer-duties.dbk:199
300 "Send an gpg-signed email about why you are leaving the project to "
301 "<email>debian-private@&lists-host;</email>."
304 # type: Content of: <chapter><section><orderedlist><listitem><para>
305 #: developer-duties.dbk:205
307 "Notify the Debian key ring maintainers that you are leaving by opening a "
308 "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
309 "words 'Debian RT' somewhere in the subject line (case doesn't matter)."