Hello, I have some comments on the already applied patch: > -2. Send an gpg-signed email announcing your retirement to > - ``debian-priv...@lists.debian.org``. > +- Use the link https://nm.debian.org/process/emeritus to log in to > + nm.debian.org [2]_, request emeritus status and write a goodby typo: goodbye > + message that will be automatically posted on debian-private.
While the above it's true, sending a signed retirement email to debian-private@ is still very much supported, and a very good way to proceed for all the myriad reasons there could be for SSO to fail (or to be a pain to set up for inactive people that just want to get out of the way). Can I recommend we keep the alternative available (with a somewhat lower precedence, as retirment through nm.d.o are a tad easier to process for everybody involved). > -4. If you received mails via a @debian.org e-mail alias (e.g. > - pr...@debian.org) and would like to get removed, open a RT ticket for > - the Debian System Administrators. Just send an e-mail to > - ``ad...@rt.debian.org`` with "Debian RT" somewhere in the subject > - stating from which aliases you'd like to get removed. This is still true. Nobody is actually checking the aliases to see if any need updating in the retirement/removal process, so really if somebody is receiving mails from an alias it needs to be updated manually. > + This also automatically notifies the MIA team, so that they can > + check if some of your packages still need orphaning. Why mentioning the MIA team here? > -- Contact ``da-mana...@debian.org``. > +- Use the link https://nm.debian.org/wizard/process/return to log in to > + nm.debian.org [2]_ and request to return from emeritus status. Here I would also mention that doing so requires being able to actually authenticate. That's usually hard for retired DDs because they can't get a @d.o certificate, and they most likely long lost access to their @user.alioth.d.o account. Maybe just mention in passing that for auth (or, most likely, all kind of) issues they can write to nm@d.o? And if they are registering a new SSO account (don't ask me why, it happens…), it probably needs to be linked to their previous nm.d.o account, which requires manual intervention from the people behind nm@d.o, so please do write that address as the contact point. > +.. [2] > + Login on nm.debian.org requires an SSO browser certificate. > + (you can generate them on https://sso.debian.org) > + If you cannot access SSO, the recommended way of action is to > + mail NM frontdesk using ``n...@debian.org``. Mh, not really. For SSO issues, the point of contact is the SSO team. The NM team grew a some know-how due to providing support in the past, but I really don't want it to be advertised as the SSO support team. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
