ftp-eu-upload-host is ftp."eu".upload.debian.org. fixed.

[developers-reference.git] / beyond-pkging.dbk

diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk
index 0d27668977c723d4f15da1cf50964b05fa1f119b..b43eda4413c1234c6a4c78c1bc8f20ca6ccc7a6d 100644 (file)
--- a/beyond-pkging.dbk
+++ b/beyond-pkging.dbk
@@ -84,7 +84,7 @@ is a real problem.  In addition, it will help prevent a situation in which
 several maintainers start filing the same bug report simultaneously.
 </para>
 <para>
 several maintainers start filing the same bug report simultaneously.
 </para>
 <para>

-Please use the programms <command>dd-list</command> and if appropriate
+Please use the programs <command>dd-list</command> and if appropriate

 <command>whodepends</command> (from the package devscripts) to generate a list
 of all affected packages, and include the output in your mail to
 &email-debian-devel;.
 <command>whodepends</command> (from the package devscripts) to generate a list
 of all affected packages, and include the output in your mail to
 &email-debian-devel;.


@@ -94,6 +94,41 @@ Note that when sending lots of bugs on the same subject, you should send the
 bug report to <email>maintonly@&bugs-host;</email> so that the bug report
 is not forwarded to the bug distribution mailing list.
 </para>
 bug report to <email>maintonly@&bugs-host;</email> so that the bug report
 is not forwarded to the bug distribution mailing list.
 </para>

+<section id="usertags">
+<title>Usertags</title>
+<para>
+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.
+</para>
+<para>
+To add usertags when filing bugs, specify the <literal>User</literal> and
+<literal>Usertags</literal> pseudo-headers:
+</para>
+<screen>
+To: submit@bugs.debian.org
+Subject: <replaceable>&lt;title-of-bug&gt;</replaceable>
+
+Package: <replaceable>&lt;pkgname&gt;</replaceable>
+<replaceable>[ ... ]</replaceable>
+User: <replaceable>&lt;email-addr&gt;</replaceable>
+Usertags: <replaceable>&lt;tag-name&gt; [ &lt;tag-name&gt; ... ]</replaceable>
+
+<replaceable>&lt;description-of-bug ...&gt;</replaceable>
+</screen>
+<para>
+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.
+</para>
+<para>
+To view bugs tagged with a specific usertag, visit
+<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>&lt;email-addr&gt;</replaceable>&amp;tag=<replaceable>&lt;tag-name&gt;</replaceable></literal>.
+</para>
+</section>

 </section>
 
 </section>
 </section>
 
 </section>


@@ -124,8 +159,8 @@ many problems as possible.  They are announced on
 &email-debian-devel-announce; and the announcement explains
 which area will be the focus of the party: usually they focus on release
 critical bugs but it may happen that they decide to help finish a major upgrade
 &email-debian-devel-announce; and the announcement explains
 which area will be the focus of the party: usually they focus on release
 critical bugs but it may happen that they decide to help finish a major upgrade

-(like a new perl version which requires recompilation of all the binary
-modules).
+(like a new <command>perl</command> version which requires recompilation of all
+the binary modules).

 </para>
 <para>
 The rules for non-maintainer uploads differ during the parties because the
 </para>
 <para>
 The rules for non-maintainer uploads differ during the parties because the


@@ -190,11 +225,11 @@ 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 the
 QA group contacts an inactive maintainer or finds more information about one,
 this is recorded in the MIA database.  This system is available in
 maintainers who are deemed Missing In Action is recorded.  When a member of the
 QA group contacts an inactive maintainer or finds more information about one,
 this is recorded in the MIA database.  This system is available in

-/org/qa.debian.org/mia on the host qa.debian.org, and can be queried with a
-tool known as <command>mia-query</command>.  Use <command>mia-query --help</command>
-to see how to query the database.  If you find that no information has been
-recorded about an inactive maintainer yet, or that you can add more
-information, you should generally proceed as follows.
+<filename>/org/qa.debian.org/mia</filename> on the host <literal>qa.debian.org
+</literal>, and can be queried with the <command>mia-query</command> tool.
+Use <command>mia-query --help</command> to see how to query the database.
+If you find that no information has been recorded about an inactive maintainer yet,
+or that you can add more information, you should generally proceed as follows.

 </para>
 <para>
 The first step is to politely contact the maintainer, and wait a reasonable
 </para>
 <para>
 The first step is to politely contact the maintainer, and wait a reasonable


@@ -211,11 +246,12 @@ maintainer in question as possible.  This includes:
 <itemizedlist>
 <listitem>
 <para>
 <itemizedlist>
 <listitem>
 <para>

-The echelon information available through the <ulink
+The <literal>echelon</literal> information available through the <ulink

 url="&url-debian-db;">developers' LDAP database</ulink>, which indicates
 when the developer last posted to a Debian mailing list.  (This includes
 url="&url-debian-db;">developers' LDAP database</ulink>, which indicates
 when the developer last posted to a Debian mailing list.  (This includes

-uploads via debian-*-changes lists.) Also, remember to check whether the
-maintainer is marked as on vacation in the database.
+mails about uploads distributed via the &email-debian-devel-changes; list.)
+Also, remember to check whether the maintainer is marked as on vacation in
+the database.

 </para>
 </listitem>
 <listitem>
 </para>
 </listitem>
 <listitem>


@@ -237,11 +273,11 @@ groups.
 </itemizedlist>
 <para>
 A bit of a problem are packages which were sponsored — the maintainer is not
 </itemizedlist>
 <para>
 A bit of a problem are packages which were sponsored — the maintainer is not

-an official Debian developer.  The echelon information is not available for
-sponsored people, for example, so you need to find and contact the Debian
-developer who has actually uploaded the package.  Given that they signed the
-package, they're responsible for the upload anyhow, and are likely to know what
-happened to the person they sponsored.
+an official Debian developer.  The <literal>echelon</literal> information is not
+available for sponsored people, for example, so you need to find and contact the
+Debian developer who has actually uploaded the package.  Given that they signed
+the package, they're responsible for the upload anyhow, and are likely to know
+what happened to the person they sponsored.

 </para>
 <para>
 It is also allowed to post a query to &email-debian-devel;,
 </para>
 <para>
 It is also allowed to post a query to &email-debian-devel;,


@@ -272,9 +308,9 @@ someone with more time.
 </para>
 <para>
 If you are interested in working in the MIA team, please have a look at the
 </para>
 <para>
 If you are interested in working in the MIA team, please have a look at the

-README file in /org/qa.debian.org/mia on qa.debian.org where the technical
-details and the MIA procedures are documented and contact
-&email-mia;.
+README file in <filename>/org/qa.debian.org/mia</filename> on <literal>
+qa.debian.org</literal> where the technical details and the MIA procedures are
+documented and contact &email-mia;.

 </para>
 </section>
 
 </para>
 </section>