msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-08-08 11:36-0300\n"
+"POT-Creation-Date: 2009-01-23 09:48+0100\n"
"PO-Revision-Date: 2007-07-01 23:09+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
"not forwarded to the bug distribution mailing list."
msgstr ""
+# type: Content of: <chapter><section><section><section><title>
+#: beyond-pkging.dbk:98
+msgid "Usertags"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:100
+msgid ""
+"You may wish to use BTS usertags when submitting bugs across a number of "
+"packages. Usertags are similar to normal tags such as 'patch' and 'wishlist' "
+"but differ in that they are user-defined and occupy a namespace that is "
+"unique to a particular user. This allows multiple sets of developers to "
+"'usertag' the same bug in different ways without conflicting."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:107
+msgid ""
+"To add usertags when filing bugs, specify the <literal>User</literal> and "
+"<literal>Usertags</literal> pseudo-headers:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><screen>
+#: beyond-pkging.dbk:110
+#, no-wrap
+msgid ""
+"\n"
+"To: submit@bugs.debian.org\n"
+"Subject: <replaceable><title-of-bug></replaceable>\n"
+"\n"
+"Package: <replaceable><pkgname></replaceable>\n"
+"<replaceable>[ ... ]</replaceable>\n"
+"User: <replaceable><email-addr></replaceable>\n"
+"Usertags: <replaceable><tag-name> [ <tag-name> ... ]</replaceable>\n"
+"\n"
+"<replaceable><description-of-bug ...></replaceable>\n"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:122
+msgid ""
+"Note that tags are seperated by spaces and cannot contain underscores. If "
+"you are filing bugs for for a particular group or team it is recommended "
+"that you set the <literal>User</literal> to an appropriate mailing list "
+"after describing your intention there."
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:128
+msgid ""
+"To view bugs tagged with a specific usertag, visit <literal>http://&bugs-"
+"host;/cgi-bin/pkgreport.cgi?users=<replaceable><email-addr></"
+"replaceable>&tag=<replaceable><tag-name></replaceable></literal>."
+msgstr ""
+
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:102
+#: beyond-pkging.dbk:137
msgid "Quality Assurance effort"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:104
+#: beyond-pkging.dbk:139
msgid "Daily work"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:106
+#: beyond-pkging.dbk:141
msgid ""
"Even though there is a dedicated group of people for Quality Assurance, QA "
"duties are not reserved solely for them. You can participate in this effort "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:120
+#: beyond-pkging.dbk:155
msgid "Bug squashing parties"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:122
+#: beyond-pkging.dbk:157
msgid ""
"From time to time the QA group organizes bug squashing parties to get rid of "
"as many problems as possible. They are announced on &email-debian-devel-"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:131
+#: beyond-pkging.dbk:166
msgid ""
"The rules for non-maintainer uploads differ during the parties because the "
"announcement of the party is considered prior notice for NMU. If you have "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:140
+#: beyond-pkging.dbk:175
msgid ""
"People participating in the party have special rules for NMU, they can NMU "
"without prior notice if they upload their NMU to DELAYED/3-day at least. "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:147
+#: beyond-pkging.dbk:182
msgid ""
"If you don't feel confident about doing an NMU, just send a patch to the "
"BTS. It's far better than a broken NMU."
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:155
+#: beyond-pkging.dbk:190
msgid "Contacting other maintainers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:157
+#: beyond-pkging.dbk:192
msgid ""
"During your lifetime within Debian, you will have to contact other "
"maintainers for various reasons. You may want to discuss a new way of "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:163
+#: beyond-pkging.dbk:198
msgid ""
"Looking up the email address of the maintainer for the package can be "
"distracting. Fortunately, there is a simple email alias, <literal><"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:171
+#: beyond-pkging.dbk:206
msgid ""
"You may also be interested in contacting the persons who are subscribed to a "
"given source package via <xref linkend=\"pkg-tracking-system\"/> . You can "
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:180
+#: beyond-pkging.dbk:215
msgid "Dealing with inactive and/or unreachable maintainers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:182
+#: beyond-pkging.dbk:217
msgid ""
"If you notice that a package is lacking maintenance, you should make sure "
"that the maintainer is active and will continue to work on their packages. "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:189
+#: beyond-pkging.dbk:224
msgid ""
"There is a simple system (the MIA database) in which information about "
"maintainers who are deemed Missing In Action is recorded. When a member of "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:200
+#: beyond-pkging.dbk:235
msgid ""
"The first step is to politely contact the maintainer, and wait a reasonable "
"time for a response. It is quite hard to define reasonable time, but it is "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:206
+#: beyond-pkging.dbk:241
msgid ""
"If the maintainer doesn't reply within four weeks (a month), one can assume "
"that a response will probably not happen. If that happens, you should "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:214
+#: beyond-pkging.dbk:249
msgid ""
"The <literal>echelon</literal> information available through the <ulink url="
"\"&url-debian-db;\">developers' LDAP database</ulink>, which indicates when "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:224
+#: beyond-pkging.dbk:259
msgid ""
"The number of packages this maintainer is responsible for, and the condition "
"of those packages. In particular, are there any RC bugs that have been open "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: beyond-pkging.dbk:233
+#: beyond-pkging.dbk:268
msgid ""
"Is there any activity of the maintainer outside of Debian? For example, they "
"might have posted something recently to non-Debian mailing lists or news "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:240
+#: beyond-pkging.dbk:275
msgid ""
"A bit of a problem are packages which were sponsored — the maintainer is not "
"an official Debian developer. The <literal>echelon</literal> information is "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:248
+#: beyond-pkging.dbk:283
msgid ""
"It is also allowed to post a query to &email-debian-devel;, asking if anyone "
"is aware of the whereabouts of the missing maintainer. Please Cc: the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:253
+#: beyond-pkging.dbk:288
msgid ""
"Once you have gathered all of this, you can contact &email-mia;. People on "
"this alias will use the information you provide in order to decide how to "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:261
+#: beyond-pkging.dbk:296
msgid ""
"One last word: please remember to be polite. We are all volunteers and "
"cannot dedicate all of our time to Debian. Also, you are not aware of the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:269
+#: beyond-pkging.dbk:304
msgid ""
"On the other hand, although we are volunteers, we do have a responsibility. "
"So you can stress the importance of the greater good — if a maintainer does "
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:275
+#: beyond-pkging.dbk:310
msgid ""
"If you are interested in working in the MIA team, please have a look at the "
"README file in <filename>/org/qa.debian.org/mia</filename> on <literal> qa."
msgstr ""
# type: Content of: <chapter><section><title>
-#: beyond-pkging.dbk:283
+#: beyond-pkging.dbk:318
msgid "Interacting with prospective Debian developers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: beyond-pkging.dbk:285
+#: beyond-pkging.dbk:320
msgid ""
"Debian's success depends on its ability to attract and retain new and "
"talented volunteers. If you are an experienced developer, we recommend that "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:291
+#: beyond-pkging.dbk:326
msgid "Sponsoring packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:293
+#: beyond-pkging.dbk:328
msgid ""
"Sponsoring a package means uploading a package for a maintainer who is not "
"able to do it on their own, a new maintainer applicant. Sponsoring a "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:304
+#: beyond-pkging.dbk:339
msgid ""
"New maintainers usually have certain difficulties creating Debian packages — "
"this is quite understandable. That is why the sponsor is there, to check "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:311
+#: beyond-pkging.dbk:346
msgid ""
"Sponsoring merely by signing the upload or just recompiling is <emphasis "
"role=\"strong\">definitely not recommended</emphasis>. You need to build "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:318
+#: beyond-pkging.dbk:353
msgid ""
"If you are an application manager for a prospective developer, you can also "
"be their sponsor. That way you can also verify how the applicant is "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:325
+#: beyond-pkging.dbk:360
msgid "Managing sponsored packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:327
+#: beyond-pkging.dbk:362
msgid ""
"By uploading a sponsored package to Debian, you are certifying that the "
"package meets minimum Debian standards. That implies that you must build "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:332
+#: beyond-pkging.dbk:367
msgid ""
"You cannot simply upload a binary <filename>.deb</filename> from the "
"sponsoree. In theory, you should only ask for the diff file and the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:341
+#: beyond-pkging.dbk:376
msgid ""
"Do not be afraid to write the sponsoree back and point out changes that need "
"to be made. It often takes several rounds of back-and-forth email before "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:346
+#: beyond-pkging.dbk:381
msgid "Once the package meets Debian standards, build and sign it with"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: beyond-pkging.dbk:348
+#: beyond-pkging.dbk:383
#, no-wrap
msgid ""
"\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:352
+#: beyond-pkging.dbk:387
msgid ""
"before uploading it to the incoming directory. Of course, you can also use "
"any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:357
+#: beyond-pkging.dbk:392
msgid ""
"The Maintainer field of the <filename>control</filename> file and the "
"<filename>changelog</filename> should list the person who did the packaging, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:363
+#: beyond-pkging.dbk:398
msgid ""
"If you prefer to leave a more evident trace of your sponsorship job, you can "
"add a line stating it in the most recent changelog entry."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:367
+#: beyond-pkging.dbk:402
msgid ""
"You are encouraged to keep tabs on the package you sponsor using <xref "
"linkend=\"pkg-tracking-system\"/> ."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:373
+#: beyond-pkging.dbk:408
msgid "Advocating new developers"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:375
+#: beyond-pkging.dbk:410
msgid ""
"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a "
"prospective developer</ulink> at the Debian web site."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:382
+#: beyond-pkging.dbk:417
msgid "Handling new maintainer applications"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:384
+#: beyond-pkging.dbk:419
msgid ""
"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
"Application Managers</ulink> at the Debian web site."
~ianmdlvl / developers-reference.git / blobdiff