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: 2010-01-04 00:20+0100\n"
12 "PO-Revision-Date: 2007-07-01 23:09+0000\n"
13 "Last-Translator: <>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: \n"
19 # type: Content of: <chapter><title>
20 #. type: Content of: <chapter><title>
21 #: beyond-pkging.dbk:7
22 msgid "Beyond Packaging"
23 msgstr "Au-delà de l'empaquetage"
25 # type: Content of: <chapter><para>
26 #. type: Content of: <chapter><para>
27 #: beyond-pkging.dbk:9
29 "Debian is about a lot more than just packaging software and maintaining "
30 "those packages. This chapter contains information about ways, often really "
31 "critical ways, to contribute to Debian beyond simply creating and "
32 "maintaining packages."
35 # type: Content of: <chapter><para>
36 #. type: Content of: <chapter><para>
37 #: beyond-pkging.dbk:14
39 "As a volunteer organization, Debian relies on the discretion of its members "
40 "in choosing what they want to work on and in choosing the most critical "
41 "thing to spend their time on."
44 # type: Content of: <chapter><section><title>
45 #. type: Content of: <chapter><section><title>
46 #: beyond-pkging.dbk:19
48 msgstr "Rapporter des bogues"
50 # type: Content of: <chapter><section><para>
51 #. type: Content of: <chapter><section><para>
52 #: beyond-pkging.dbk:21
54 "We encourage you to file bugs as you find them in Debian packages. In fact, "
55 "Debian developers are often the first line testers. Finding and reporting "
56 "bugs in other developers' packages improves the quality of Debian."
59 # type: Content of: <chapter><section><para>
60 #. type: Content of: <chapter><section><para>
61 #: beyond-pkging.dbk:26
63 "Read the <ulink url=\"&url-bts-report;\">instructions for reporting bugs</"
64 "ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking system</ulink>."
67 # type: Content of: <chapter><section><para>
68 #. type: Content of: <chapter><section><para>
69 #: beyond-pkging.dbk:31
71 "Try to submit the bug from a normal user account at which you are likely to "
72 "receive mail, so that people can reach you if they need further information "
73 "about the bug. Do not submit bugs as root."
76 # type: Content of: <chapter><section><para>
77 #. type: Content of: <chapter><section><para>
78 #: beyond-pkging.dbk:36
80 "You can use a tool like <citerefentry> <refentrytitle>reportbug</"
81 "refentrytitle> <manvolnum>1</manvolnum> </citerefentry> to submit bugs. It "
82 "can automate and generally ease the process."
85 # type: Content of: <chapter><section><para>
86 #. type: Content of: <chapter><section><para>
87 #: beyond-pkging.dbk:41
89 "Make sure the bug is not already filed against a package. Each package has "
90 "a bug list easily reachable at <literal>http://&bugs-host;/"
91 "<replaceable>packagename</replaceable></literal> Utilities like "
92 "<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</"
93 "manvolnum> </citerefentry> can also provide you with this information (and "
94 "<command>reportbug</command> will usually invoke <command>querybts</command> "
95 "before sending, too)."
98 # type: Content of: <chapter><section><para>
99 #. type: Content of: <chapter><section><para>
100 #: beyond-pkging.dbk:50
102 "Try to direct your bugs to the proper location. When for example your bug "
103 "is about a package which overwrites files from another package, check the "
104 "bug lists for <emphasis>both</emphasis> of those packages in order to avoid "
105 "filing duplicate bug reports."
108 # type: Content of: <chapter><section><para>
109 #. type: Content of: <chapter><section><para>
110 #: beyond-pkging.dbk:56
112 "For extra credit, you can go through other packages, merging bugs which are "
113 "reported more than once, or tagging bugs `fixed' when they have already been "
114 "fixed. Note that when you are neither the bug submitter nor the package "
115 "maintainer, you should not actually close the bug (unless you secure "
116 "permission from the maintainer)."
119 # type: Content of: <chapter><section><para>
120 #. type: Content of: <chapter><section><para>
121 #: beyond-pkging.dbk:63
123 "From time to time you may want to check what has been going on with the bug "
124 "reports that you submitted. Take this opportunity to close those that you "
125 "can't reproduce anymore. To find out all the bugs you submitted, you just "
126 "have to visit <literal>http://&bugs-host;/from:<replaceable><your-email-"
127 "addr></replaceable></literal>."
130 # type: Content of: <chapter><section><section><title>
131 #. type: Content of: <chapter><section><section><title>
132 #: beyond-pkging.dbk:70
133 msgid "Reporting lots of bugs at once (mass bug filing)"
136 # type: Content of: <chapter><section><section><para>
137 #. type: Content of: <chapter><section><section><para>
138 #: beyond-pkging.dbk:72
140 "Reporting a great number of bugs for the same problem on a great number of "
141 "different packages — i.e., more than 10 — is a deprecated practice. Take "
142 "all possible steps to avoid submitting bulk bugs at all. For instance, if "
143 "checking for the problem can be automated, add a new check to <systemitem "
144 "role=\"package\">lintian</systemitem> so that an error or warning is emitted."
147 # type: Content of: <chapter><section><section><para>
148 #. type: Content of: <chapter><section><section><para>
149 #: beyond-pkging.dbk:79
151 "If you report more than 10 bugs on the same topic at once, it is recommended "
152 "that you send a message to &email-debian-devel; describing your intention "
153 "before submitting the report, and mentioning the fact in the subject of your "
154 "mail. This will allow other developers to verify that the bug is a real "
155 "problem. In addition, it will help prevent a situation in which several "
156 "maintainers start filing the same bug report simultaneously."
159 #. type: Content of: <chapter><section><section><para>
160 #: beyond-pkging.dbk:87
162 "Please use the programs <command>dd-list</command> and if appropriate "
163 "<command>whodepends</command> (from the package devscripts) to generate a "
164 "list of all affected packages, and include the output in your mail to &email-"
168 # type: Content of: <chapter><section><section><para>
169 #. type: Content of: <chapter><section><section><para>
170 #: beyond-pkging.dbk:93
172 "Note that when sending lots of bugs on the same subject, you should send the "
173 "bug report to <email>maintonly@&bugs-host;</email> so that the bug report is "
174 "not forwarded to the bug distribution mailing list."
177 # type: Content of: <chapter><section><section><section><title>
178 #. type: Content of: <chapter><section><section><section><title>
179 #: beyond-pkging.dbk:98
183 # type: Content of: <chapter><section><section><section><para>
184 #. type: Content of: <chapter><section><section><section><para>
185 #: beyond-pkging.dbk:100
187 "You may wish to use BTS usertags when submitting bugs across a number of "
188 "packages. Usertags are similar to normal tags such as 'patch' and 'wishlist' "
189 "but differ in that they are user-defined and occupy a namespace that is "
190 "unique to a particular user. This allows multiple sets of developers to "
191 "'usertag' the same bug in different ways without conflicting."
194 # type: Content of: <chapter><section><section><section><para>
195 #. type: Content of: <chapter><section><section><section><para>
196 #: beyond-pkging.dbk:107
198 "To add usertags when filing bugs, specify the <literal>User</literal> and "
199 "<literal>Usertags</literal> pseudo-headers:"
202 #. type: Content of: <chapter><section><section><section><screen>
203 #: beyond-pkging.dbk:111
206 "To: submit@bugs.debian.org\n"
207 "Subject: <replaceable><title-of-bug></replaceable>\n"
209 "Package: <replaceable><pkgname></replaceable>\n"
210 "<replaceable>[ ... ]</replaceable>\n"
211 "User: <replaceable><email-addr></replaceable>\n"
212 "Usertags: <replaceable><tag-name> [ <tag-name> ... ]</replaceable>\n"
214 "<replaceable><description-of-bug ...></replaceable>\n"
217 # type: Content of: <chapter><section><section><section><para>
218 #. type: Content of: <chapter><section><section><section><para>
219 #: beyond-pkging.dbk:122
221 "Note that tags are seperated by spaces and cannot contain underscores. If "
222 "you are filing bugs for for a particular group or team it is recommended "
223 "that you set the <literal>User</literal> to an appropriate mailing list "
224 "after describing your intention there."
227 # type: Content of: <chapter><section><section><section><para>
228 #. type: Content of: <chapter><section><section><section><para>
229 #: beyond-pkging.dbk:128
231 "To view bugs tagged with a specific usertag, visit <literal>http://&bugs-"
232 "host;/cgi-bin/pkgreport.cgi?users=<replaceable><email-addr></"
233 "replaceable>&tag=<replaceable><tag-name></replaceable></literal>."
236 # type: Content of: <chapter><section><title>
237 #. type: Content of: <chapter><section><title>
238 #: beyond-pkging.dbk:137
239 msgid "Quality Assurance effort"
242 # type: Content of: <chapter><section><section><title>
243 #. type: Content of: <chapter><section><section><title>
244 #: beyond-pkging.dbk:139
248 # type: Content of: <chapter><section><section><para>
249 #. type: Content of: <chapter><section><section><para>
250 #: beyond-pkging.dbk:141
252 "Even though there is a dedicated group of people for Quality Assurance, QA "
253 "duties are not reserved solely for them. You can participate in this effort "
254 "by keeping your packages as bug-free as possible, and as lintian-clean (see "
255 "<xref linkend=\"lintian\"/> ) as possible. If you do not find that "
256 "possible, then you should consider orphaning some of your packages (see "
257 "<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of "
258 "other people in order to catch up with the backlog of bugs that you have "
259 "(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the "
260 "same time, you can look for co-maintainers (see <xref linkend="
261 "\"collaborative-maint\"/> )."
264 # type: Content of: <chapter><section><section><title>
265 #. type: Content of: <chapter><section><section><title>
266 #: beyond-pkging.dbk:155
267 msgid "Bug squashing parties"
270 # type: Content of: <chapter><section><section><para>
271 #. type: Content of: <chapter><section><section><para>
272 #: beyond-pkging.dbk:157
274 "From time to time the QA group organizes bug squashing parties to get rid of "
275 "as many problems as possible. They are announced on &email-debian-devel-"
276 "announce; and the announcement explains which area will be the focus of the "
277 "party: usually they focus on release critical bugs but it may happen that "
278 "they decide to help finish a major upgrade (like a new <command>perl</"
279 "command> version which requires recompilation of all the binary modules)."
282 # type: Content of: <chapter><section><section><para>
283 #. type: Content of: <chapter><section><section><para>
284 #: beyond-pkging.dbk:166
286 "The rules for non-maintainer uploads differ during the parties because the "
287 "announcement of the party is considered prior notice for NMU. If you have "
288 "packages that may be affected by the party (because they have release "
289 "critical bugs for example), you should send an update to each of the "
290 "corresponding bug to explain their current status and what you expect from "
291 "the party. If you don't want an NMU, or if you're only interested in a "
292 "patch, or if you will deal yourself with the bug, please explain that in the "
296 # type: Content of: <chapter><section><section><para>
297 #. type: Content of: <chapter><section><section><para>
298 #: beyond-pkging.dbk:175
300 "People participating in the party have special rules for NMU, they can NMU "
301 "without prior notice if they upload their NMU to DELAYED/3-day at least. "
302 "All other NMU rules apply as usually; they should send the patch of the NMU "
303 "to the BTS (to one of the open bugs fixed by the NMU, or to a new bug, "
304 "tagged fixed). They should also respect any particular wishes of the "
308 # type: Content of: <chapter><section><section><para>
309 #. type: Content of: <chapter><section><section><para>
310 #: beyond-pkging.dbk:182
312 "If you don't feel confident about doing an NMU, just send a patch to the "
313 "BTS. It's far better than a broken NMU."
316 # type: Content of: <chapter><section><title>
317 #. type: Content of: <chapter><section><title>
318 #: beyond-pkging.dbk:190
319 msgid "Contacting other maintainers"
322 # type: Content of: <chapter><section><para>
323 #. type: Content of: <chapter><section><para>
324 #: beyond-pkging.dbk:192
326 "During your lifetime within Debian, you will have to contact other "
327 "maintainers for various reasons. You may want to discuss a new way of "
328 "cooperating between a set of related packages, or you may simply remind "
329 "someone that a new upstream version is available and that you need it."
332 # type: Content of: <chapter><section><para>
333 #. type: Content of: <chapter><section><para>
334 #: beyond-pkging.dbk:198
336 "Looking up the email address of the maintainer for the package can be "
337 "distracting. Fortunately, there is a simple email alias, <literal><"
338 "package>@&packages-host;</literal>, which provides a way to email the "
339 "maintainer, whatever their individual email address (or addresses) may be. "
340 "Replace <literal><package></literal> with the name of a source or a "
344 # type: Content of: <chapter><section><para>
345 #. type: Content of: <chapter><section><para>
346 #: beyond-pkging.dbk:206
348 "You may also be interested in contacting the persons who are subscribed to a "
349 "given source package via <xref linkend=\"pkg-tracking-system\"/> . You can "
350 "do so by using the <literal><package>@&pts-host;</literal> email "
354 # type: Content of: <chapter><section><title>
355 #. type: Content of: <chapter><section><title>
356 #: beyond-pkging.dbk:215
357 msgid "Dealing with inactive and/or unreachable maintainers"
360 # type: Content of: <chapter><section><para>
361 #. type: Content of: <chapter><section><para>
362 #: beyond-pkging.dbk:217
364 "If you notice that a package is lacking maintenance, you should make sure "
365 "that the maintainer is active and will continue to work on their packages. "
366 "It is possible that they are not active any more, but haven't registered out "
367 "of the system, so to speak. On the other hand, it is also possible that "
368 "they just need a reminder."
371 # type: Content of: <chapter><section><para>
372 #. type: Content of: <chapter><section><para>
373 #: beyond-pkging.dbk:224
375 "There is a simple system (the MIA database) in which information about "
376 "maintainers who are deemed Missing In Action is recorded. When a member of "
377 "the QA group contacts an inactive maintainer or finds more information about "
378 "one, this is recorded in the MIA database. This system is available in "
379 "<filename>/org/qa.debian.org/mia</filename> on the host <literal>qa.debian."
380 "org </literal>, and can be queried with the <command>mia-query</command> "
381 "tool. Use <command>mia-query --help</command> to see how to query the "
382 "database. If you find that no information has been recorded about an "
383 "inactive maintainer yet, or that you can add more information, you should "
384 "generally proceed as follows."
387 # type: Content of: <chapter><section><para>
388 #. type: Content of: <chapter><section><para>
389 #: beyond-pkging.dbk:235
391 "The first step is to politely contact the maintainer, and wait a reasonable "
392 "time for a response. It is quite hard to define reasonable time, but it is "
393 "important to take into account that real life is sometimes very hectic. One "
394 "way to handle this would be to send a reminder after two weeks."
397 # type: Content of: <chapter><section><para>
398 #. type: Content of: <chapter><section><para>
399 #: beyond-pkging.dbk:241
401 "If the maintainer doesn't reply within four weeks (a month), one can assume "
402 "that a response will probably not happen. If that happens, you should "
403 "investigate further, and try to gather as much useful information about the "
404 "maintainer in question as possible. This includes:"
407 # type: Content of: <chapter><section><itemizedlist><listitem><para>
408 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
409 #: beyond-pkging.dbk:249
411 "The <literal>echelon</literal> information available through the <ulink url="
412 "\"&url-debian-db;\">developers' LDAP database</ulink>, which indicates when "
413 "the developer last posted to a Debian mailing list. (This includes mails "
414 "about uploads distributed via the &email-debian-devel-changes; list.) Also, "
415 "remember to check whether the maintainer is marked as on vacation in the "
419 # type: Content of: <chapter><section><itemizedlist><listitem><para>
420 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
421 #: beyond-pkging.dbk:259
423 "The number of packages this maintainer is responsible for, and the condition "
424 "of those packages. In particular, are there any RC bugs that have been open "
425 "for ages? Furthermore, how many bugs are there in general? Another important "
426 "piece of information is whether the packages have been NMUed, and if so, by "
430 # type: Content of: <chapter><section><itemizedlist><listitem><para>
431 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
432 #: beyond-pkging.dbk:268
434 "Is there any activity of the maintainer outside of Debian? For example, they "
435 "might have posted something recently to non-Debian mailing lists or news "
439 # type: Content of: <chapter><section><para>
440 #. type: Content of: <chapter><section><para>
441 #: beyond-pkging.dbk:275
443 "A bit of a problem are packages which were sponsored — the maintainer is not "
444 "an official Debian developer. The <literal>echelon</literal> information is "
445 "not available for sponsored people, for example, so you need to find and "
446 "contact the Debian developer who has actually uploaded the package. Given "
447 "that they signed the package, they're responsible for the upload anyhow, and "
448 "are likely to know what happened to the person they sponsored."
451 # type: Content of: <chapter><section><para>
452 #. type: Content of: <chapter><section><para>
453 #: beyond-pkging.dbk:283
455 "It is also allowed to post a query to &email-debian-devel;, asking if anyone "
456 "is aware of the whereabouts of the missing maintainer. Please Cc: the "
457 "person in question."
460 # type: Content of: <chapter><section><para>
461 #. type: Content of: <chapter><section><para>
462 #: beyond-pkging.dbk:288
464 "Once you have gathered all of this, you can contact &email-mia;. People on "
465 "this alias will use the information you provide in order to decide how to "
466 "proceed. For example, they might orphan one or all of the packages of the "
467 "maintainer. If a package has been NMUed, they might prefer to contact the "
468 "NMUer before orphaning the package — perhaps the person who has done the NMU "
469 "is interested in the package."
472 # type: Content of: <chapter><section><para>
473 #. type: Content of: <chapter><section><para>
474 #: beyond-pkging.dbk:296
476 "One last word: please remember to be polite. We are all volunteers and "
477 "cannot dedicate all of our time to Debian. Also, you are not aware of the "
478 "circumstances of the person who is involved. Perhaps they might be "
479 "seriously ill or might even have died — you do not know who may be on the "
480 "receiving side. Imagine how a relative will feel if they read the e-mail of "
481 "the deceased and find a very impolite, angry and accusing message!"
484 # type: Content of: <chapter><section><para>
485 #. type: Content of: <chapter><section><para>
486 #: beyond-pkging.dbk:304
488 "On the other hand, although we are volunteers, we do have a responsibility. "
489 "So you can stress the importance of the greater good — if a maintainer does "
490 "not have the time or interest anymore, they should let go and give the "
491 "package to someone with more time."
494 # type: Content of: <chapter><section><para>
495 #. type: Content of: <chapter><section><para>
496 #: beyond-pkging.dbk:310
498 "If you are interested in working in the MIA team, please have a look at the "
499 "README file in <filename>/org/qa.debian.org/mia</filename> on <literal> qa."
500 "debian.org</literal> where the technical details and the MIA procedures are "
501 "documented and contact &email-mia;."
504 # type: Content of: <chapter><section><title>
505 #. type: Content of: <chapter><section><title>
506 #: beyond-pkging.dbk:318
507 msgid "Interacting with prospective Debian developers"
510 # type: Content of: <chapter><section><para>
511 #. type: Content of: <chapter><section><para>
512 #: beyond-pkging.dbk:320
514 "Debian's success depends on its ability to attract and retain new and "
515 "talented volunteers. If you are an experienced developer, we recommend that "
516 "you get involved with the process of bringing in new developers. This "
517 "section describes how to help new prospective developers."
520 # type: Content of: <chapter><section><section><title>
521 #. type: Content of: <chapter><section><section><title>
522 #: beyond-pkging.dbk:326
523 msgid "Sponsoring packages"
526 # type: Content of: <chapter><section><section><para>
527 #. type: Content of: <chapter><section><section><para>
528 #: beyond-pkging.dbk:328
530 "Sponsoring a package means uploading a package for a maintainer who is not "
531 "able to do it on their own, a new maintainer applicant. Sponsoring a "
532 "package also means accepting responsibility for it."
535 # type: Content of: <chapter><section><section><para>
536 #. type: Content of: <chapter><section><section><para>
537 #: beyond-pkging.dbk:339
539 "New maintainers usually have certain difficulties creating Debian packages — "
540 "this is quite understandable. That is why the sponsor is there, to check "
541 "the package and verify that it is good enough for inclusion in Debian. "
542 "(Note that if the sponsored package is new, the ftpmasters will also have to "
543 "inspect it before letting it in.)"
546 # type: Content of: <chapter><section><section><para>
547 #. type: Content of: <chapter><section><section><para>
548 #: beyond-pkging.dbk:346
550 "Sponsoring merely by signing the upload or just recompiling is <emphasis "
551 "role=\"strong\">definitely not recommended</emphasis>. You need to build "
552 "the source package just like you would build a package of your own. "
553 "Remember that it doesn't matter that you left the prospective developer's "
554 "name both in the changelog and the control file, the upload can still be "
558 # type: Content of: <chapter><section><section><para>
559 #. type: Content of: <chapter><section><section><para>
560 #: beyond-pkging.dbk:353
562 "If you are an application manager for a prospective developer, you can also "
563 "be their sponsor. That way you can also verify how the applicant is "
564 "handling the 'Tasks and Skills' part of their application."
567 # type: Content of: <chapter><section><section><title>
568 #. type: Content of: <chapter><section><section><title>
569 #: beyond-pkging.dbk:360
570 msgid "Managing sponsored packages"
573 # type: Content of: <chapter><section><section><para>
574 #. type: Content of: <chapter><section><section><para>
575 #: beyond-pkging.dbk:362
577 "By uploading a sponsored package to Debian, you are certifying that the "
578 "package meets minimum Debian standards. That implies that you must build "
579 "and test the package on your own system before uploading."
582 # type: Content of: <chapter><section><section><para>
583 #. type: Content of: <chapter><section><section><para>
584 #: beyond-pkging.dbk:367
586 "You cannot simply upload a binary <filename>.deb</filename> from the "
587 "sponsoree. In theory, you should only ask for the diff file and the "
588 "location of the original source tarball, and then you should download the "
589 "source and apply the diff yourself. In practice, you may want to use the "
590 "source package built by your sponsoree. In that case, you have to check "
591 "that they haven't altered the upstream files in the <filename>.orig.tar.gz</"
592 "filename> file that they're providing."
595 # type: Content of: <chapter><section><section><para>
596 #. type: Content of: <chapter><section><section><para>
597 #: beyond-pkging.dbk:376
599 "Do not be afraid to write the sponsoree back and point out changes that need "
600 "to be made. It often takes several rounds of back-and-forth email before "
601 "the package is in acceptable shape. Being a sponsor means being a mentor."
604 # type: Content of: <chapter><section><section><para>
605 #. type: Content of: <chapter><section><section><para>
606 #: beyond-pkging.dbk:381
607 msgid "Once the package meets Debian standards, build and sign it with"
610 #. type: Content of: <chapter><section><section><screen>
611 #: beyond-pkging.dbk:384
613 msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
616 # type: Content of: <chapter><section><section><para>
617 #. type: Content of: <chapter><section><section><para>
618 #: beyond-pkging.dbk:387
620 "before uploading it to the incoming directory. Of course, you can also use "
621 "any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique "
622 "in your secret keyring."
625 # type: Content of: <chapter><section><section><para>
626 #. type: Content of: <chapter><section><section><para>
627 #: beyond-pkging.dbk:392
629 "The Maintainer field of the <filename>control</filename> file and the "
630 "<filename>changelog</filename> should list the person who did the packaging, "
631 "i.e., the sponsoree. The sponsoree will therefore get all the BTS mail "
635 # type: Content of: <chapter><section><section><para>
636 #. type: Content of: <chapter><section><section><para>
637 #: beyond-pkging.dbk:398
639 "If you prefer to leave a more evident trace of your sponsorship job, you can "
640 "add a line stating it in the most recent changelog entry."
643 # type: Content of: <chapter><section><section><para>
644 #. type: Content of: <chapter><section><section><para>
645 #: beyond-pkging.dbk:402
647 "You are encouraged to keep tabs on the package you sponsor using <xref "
648 "linkend=\"pkg-tracking-system\"/> ."
651 # type: Content of: <chapter><section><section><title>
652 #. type: Content of: <chapter><section><section><title>
653 #: beyond-pkging.dbk:408
654 msgid "Advocating new developers"
657 # type: Content of: <chapter><section><section><para>
658 #. type: Content of: <chapter><section><section><para>
659 #: beyond-pkging.dbk:410
661 "See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a "
662 "prospective developer</ulink> at the Debian web site."
665 # type: Content of: <chapter><section><section><title>
666 #. type: Content of: <chapter><section><section><title>
667 #: beyond-pkging.dbk:417
668 msgid "Handling new maintainer applications"
671 # type: Content of: <chapter><section><section><para>
672 #. type: Content of: <chapter><section><section><para>
673 #: beyond-pkging.dbk:419
675 "Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
676 "Application Managers</ulink> at the Debian web site."