X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=developer-duties.dbk;h=f09e3cf09ab1002607f9813a2cd312c55a79f16d;hp=b2d375fd00bd676f7a3b8093ee7794cbb6cb4145;hb=4ea36085da608e48d700c63c3fb81c8f2e91dff3;hpb=eee80cde286181bc20d6f446a6cb6100027a5e53
diff --git a/developer-duties.dbk b/developer-duties.dbk
index b2d375f..f09e3cf 100644
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -16,8 +16,7 @@ as well as the address where you get your debian-private subscription if you
choose to subscribe there.
-For more information about the database, please see
-.
+For more information about the database, please see .
@@ -26,7 +25,7 @@ For more information about the database, please see
Be very careful with your private keys. Do not place them on any public
servers or multiuser machines, such as the Debian servers (see ). Back your keys up; keep a copy offline. Read
+linkend="server-machines"/>). Back your keys up; keep a copy offline. Read
the documentation that comes with your software; read the PGP FAQ.
@@ -100,7 +99,7 @@ duties in the project.
Usually this means that other developers are allowed to NMU (see ) your package if a big problem (release critical bug, security
+linkend="nmu"/>) your package if a big problem (release critical bug, security
update, etc.) occurs while you're on vacation. Sometimes it's nothing as
critical as that, but it's still appropriate to let others know that you're
unavailable.
@@ -122,7 +121,7 @@ the on vacation flag when you come back!
Ideally, you should sign up at the GPG coordination site when booking a
+url="&url-gpg-coord;">GPG coordination pages when booking a
holiday and check if anyone there is looking for signing. This is especially
important when people go to exotic places where we don't have any developers
yet but where there are people who are interested in applying.
@@ -164,7 +163,7 @@ Debian community is not worth the benefits the software may bring.
Managing release-critical bugs
Generally you should deal with bug reports on your packages as described in
- . However, there's a special category of bugs
+. However, there's a special category of bugs
that you need to take care of â the so-called release-critical bugs (RC
bugs). All bug reports that have severity critical,
grave or serious are considered to
@@ -182,7 +181,7 @@ mail to the Quality Assurance (QA) group
debian-qa@&lists-host;, or explain your difficulties and
present a plan to fix them by sending a mail to the bug report. Otherwise,
people from the QA group may want to do a Non-Maintainer Upload (see ) after trying to contact you (they might not wait as long as
+linkend="nmu"/>) after trying to contact you (they might not wait as long as
usual before they do their NMU if they have seen no recent activity from you in
the BTS).
@@ -197,7 +196,7 @@ following steps:
-Orphan all your packages, as described in .
+Orphan all your packages, as described in .
@@ -209,7 +208,7 @@ Send an gpg-signed email about why you are leaving the project to
Notify the Debian key ring maintainers that you are leaving by opening a ticket
-in Debian RT by sending a mail to keyring@rt.debian.org with the words 'Debian
+in Debian RT by sending a mail to &email-keyring; with the words 'Debian
RT' somewhere in the subject line (case doesn't matter).