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: 2008-08-08 11:33-0300\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"
15 "Content-Type: text/plain; charset=utf-8\n"
16 "Content-Transfer-Encoding: ENCODING"
18 # type: Content of: <chapter><title>
19 #: developer-duties.dbk:7
20 msgid "Debian Developer's Duties"
23 # type: Content of: <chapter><section><title>
24 #: developer-duties.dbk:9
25 msgid "Maintaining your Debian information"
28 # type: Content of: <chapter><section><para>
29 #: developer-duties.dbk:11
31 "There's a LDAP database containing information about Debian developers at "
32 "<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information "
33 "there and update it as it changes. Most notably, make sure that the address "
34 "where your debian.org email gets forwarded to is always up to date, as well "
35 "as the address where you get your debian-private subscription if you choose "
39 # type: Content of: <chapter><section><para>
40 #: developer-duties.dbk:19
42 "For more information about the database, please see <xref "
43 "linkend=\"devel-db\"/> ."
46 # type: Content of: <chapter><section><title>
47 #: developer-duties.dbk:25
48 msgid "Maintaining your public key"
51 # type: Content of: <chapter><section><para>
52 #: developer-duties.dbk:27
54 "Be very careful with your private keys. Do not place them on any public "
55 "servers or multiuser machines, such as the Debian servers (see <xref "
56 "linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. "
57 "Read the documentation that comes with your software; read the <ulink "
58 "url=\"&url-pgp-faq;\">PGP FAQ</ulink>."
61 # type: Content of: <chapter><section><para>
62 #: developer-duties.dbk:34
64 "You need to ensure not only that your key is secure against being stolen, "
65 "but also that it is secure against being lost. Generate and make a copy "
66 "(best also in paper form) of your revocation certificate; this is needed if "
70 # type: Content of: <chapter><section><para>
71 #: developer-duties.dbk:40
73 "If you add signatures to your public key, or add user identities, you can "
74 "update the Debian key ring by sending your key to the key server at "
75 "<literal>&keyserver-host;</literal>."
78 # type: Content of: <chapter><section><para>
79 #: developer-duties.dbk:45
81 "If you need to add a completely new key or remove an old key, you need to "
82 "get the new key signed by another developer. If the old key is compromised "
83 "or invalid, you also have to add the revocation certificate. If there is no "
84 "real reason for a new key, the Keyring Maintainers might reject the new "
85 "key. Details can be found at <ulink "
86 "url=\"http://&keyserver-host;/replacing_keys.html\"></ulink>."
89 # type: Content of: <chapter><section><para>
90 #: developer-duties.dbk:53
92 "The same key extraction routines discussed in <xref "
93 "linkend=\"registering\"/> apply."
96 # type: Content of: <chapter><section><para>
97 #: developer-duties.dbk:57
99 "You can find a more in-depth discussion of Debian key maintenance in the "
100 "documentation of the <systemitem "
101 "role=\"package\">debian-keyring</systemitem> package."
104 # type: Content of: <chapter><section><title>
105 #: developer-duties.dbk:64
109 # type: Content of: <chapter><section><para>
110 #: developer-duties.dbk:66
112 "Even though Debian isn't really a democracy, we use a democratic process to "
113 "elect our leaders and to approve general resolutions. These procedures are "
114 "defined by the <ulink url=\"&url-constitution;\">Debian "
115 "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 "
142 "url=\"&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 "
206 "url=\"&url-newmaint-db;gpg.php\">GPG coordination site</ulink> when booking "
207 "a holiday and check if anyone there is looking for signing. This is "
208 "especially important when people go to exotic places where we don't have any "
209 "developers yet but where there are 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 <literal>critical</literal>, "
259 "<literal>grave</literal> or <literal>serious</literal> 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 "
274 "<email>debian-qa@&lists-host;</email>, or explain your difficulties and "
275 "present a plan to fix them by sending a mail to the bug report. Otherwise, "
276 "people from the QA group may want to do a Non-Maintainer Upload (see <xref "
277 "linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long "
278 "as usual before they do their NMU if they have seen no recent activity from "
282 # type: Content of: <chapter><section><title>
283 #: developer-duties.dbk:186
287 # type: Content of: <chapter><section><para>
288 #: developer-duties.dbk:188
290 "If you choose to leave the Debian project, you should make sure you do the "
294 # type: Content of: <chapter><section><orderedlist><listitem><para>
295 #: developer-duties.dbk:194
296 msgid "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)."