X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developer-duties.dbk;h=6b60b6554c68cd364f0652cb1b170fc129970fda;hb=91a4aecaa35972f377bcaf4be8d5e70e659b9867;hp=120b89cbdc4afbb27b53a87b0d17db2c0164b294;hpb=bae8532415c6dd425040394761eb85e03726fbe7;p=developers-reference.git
diff --git a/developer-duties.dbk b/developer-duties.dbk
index 120b89c..6b60b65 100644
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -271,6 +271,44 @@ RT' somewhere in the subject line (case doesn't matter).
+
+It is important that the above process is followed, because finding inactive
+developers and orphaning their packages takes significant time and effort.
+
+
+
+
+Returning after retirement
+
+A retired developer's account is marked as "emeritus" when the process in
+ is followed, and "disabled" otherwise. Retired
+developers with an "emeritus" account can get their account re-activated as
+follows:
+
+
+
+
+
+Contact &email-debian-account-manager;.
+
+
+
+
+Go through a shortened NM process (to ensure that the returning developer
+still knows important parts of P&P and T&S).
+
+
+
+
+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.
+
+
+
+
+Retired developers with a "disabled" account need to go through NM again.
+