[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540249: patch for returning developers



tag 540249 +patch
thanks

Dear devref maintainers,

I've prepared a patch against current svn to elaborate on the process of
accepting back to the project old developers.

It's based on material from the DAM announcement that's mentioned in msg #5 of
this bug report. The patch is spell-checked and verified against the txt &
html targets.

Cheers,
Serafeim


Index: developer-duties.dbk
===================================================================
--- developer-duties.dbk	(revision 7961)
+++ developer-duties.dbk	(working copy)
@@ -213,7 +213,45 @@
 </para>
 </listitem>
 </orderedlist>
+<para>
+It is important that the above process is followed, because finding inactive
+developers and orphaning their packages takes significant time and effort.
+</para>
 </section>
 
+<section id="returning">
+<title>Returning after retirement</title>
+<para>
+A retired developer's account is marked as "emeritus" when the process in
+<xref linkend="s3.7"/> is followed, and "disabled" otherwise. Retired
+developers with an "emeritus" account can get their account re-activated as
+follows:
+</para>
+
+<itemizedlist>
+<listitem>
+<para>
+Contact &email-debian-account-manager;.
+</para>
+</listitem>
+<listitem>
+<para>
+Go through a shortened NM process (to ensure that the returning developer
+still knows important parts of P&amp;P and T&amp;S).
+</para>
+</listitem>
+<listitem>
+<para>
+Prove that they still control the GPG key associated with the account, or
+provide proof of identify on a new GPG key, with at least two signatures from
+other developers.
+</para>
+</listitem>
+</itemizedlist>
+<para>
+Retired developers with a "disabled" account need to go through NM again.
+</para>
+</section>
+
 </chapter>
 
Index: common.ent
===================================================================
--- common.ent	(revision 7961)
+++ common.ent	(working copy)
@@ -132,6 +132,7 @@
 <!-- Debian email addresses -->
 <!ENTITY email-listmaster "<email>listmaster@&lists-host;</email>">
 <!ENTITY email-devel-ref "<email>developers-reference@&packages-host;</email>">
+<!ENTITY email-debian-account-manager "<email>da-manager@debian.org</email>">
 <!ENTITY email-debian-changes "<email>debian-changes@lists.debian.org</email>">
 <!ENTITY email-debian-devel "<email>debian-devel@&lists-host;</email>">
 <!ENTITY email-debian-devel-announce "<email>debian-devel-announce@&lists-host;</email>">



Reply to: