Mention collab-maint in the VCS section. Closes: #496815

[developers-reference.git] / developer-duties.dbk

diff --git a/developer-duties.dbk b/developer-duties.dbk
index 6b60b6554c68cd364f0652cb1b170fc129970fda..27a7ff784303bcf921b588146cd7fac4e4d8c598 100644 (file)
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -37,7 +37,7 @@ given transition if you are not able to identify them.
 <title>Maintain packages in <literal>stable</literal></title>
 <para>
 Most of the package maintainer's work goes into providing updated
-versions of packages in <literal>unstable</literal>, but his job also entails taking care
+versions of packages in <literal>unstable</literal>, but their job also entails taking care
 of the packages in the current <literal>stable</literal> release.
 </para>
 <para>
@@ -77,7 +77,7 @@ can block the <literal>testing</literal> migration of many packages.
 </para>
 <para>
 Lack of attention to RC bugs is often interpreted by the QA team as a sign
-that the maintainer has disappeared without properly orphaning his package.
+that the maintainer has disappeared without properly orphaning their package.
 The MIA team might also get involved, which could result in your packages
 being orphaned (see <xref linkend="mia-qa" />).
 </para>
@@ -270,6 +270,15 @@ in Debian RT by sending a mail to &email-keyring; with the words 'Debian
 RT' somewhere in the subject line (case doesn't matter).
 </para>
 </listitem>
+<listitem>
+<para>
+If you received mails via a @debian.org e-mail alias (e.g.
+press@debian.org) and would like to get removed, open a RT ticket for
+the Debian System Administrators. Just send an e-mail to
+&email-rt-dsa; with "Debian RT" somewhere in the subject stating
+from which aliases you'd like to get removed.
+</para>
+</listitem>
 </orderedlist>
 <para>
 It is important that the above process is followed, because finding inactive