GitHub¶

• The user is removed from thepython/organization on GitHub;

• The user is removed from thepsf/organization on GitHub;

• The user is removed from thepypa/organization on GitHub.

The PSF staff does not follow up with GitHub with regards to GitHub accountcancellation as this action is reserved for next-of-kin or designated bythe deceased GitHub user to act as an account successor.

The general policy regarding deceased users on GitHub is described on theirDeceased User Policypage.

Repositories in the organization¶

• The user’s GitHub handle is removed from/.github/CODEOWNERS.To see all that need action, performthis query.

• The user is marked as deceased in the privatevoters/python-core.tomlfile with theleft= field set to the day of passing, if known.

discuss.python.org¶

• The user’s “custom status” is set to 🕊inmemoriam;

• The user’s “about me” is amended with$firstnamepassedawayon$date.[Inmemoriam.]($in_memoriam_post_url);

• In the user’s security “recently used devices” the staff memberchooses “Log out all”;

• In the user’s permissions the staff member chooses “Deactivate account”;

• The user’s trust level is reset to1:basicuser (trust level 0doesn’t allow links in “About Me”);

• The user’s “associated accounts” (like GitHub) that provide analternative login method, are all disconnected;

• The user’s API keys are revoked;

• The user’s admin or moderator right is revoked;

• The user’s primary email address is reset toUSERNAME@in-memoriam.invalid and secondary email addresses areremoved (this step requires the administrator to contact Discourse.orgstaff viateam@discourse.org).

The “in memoriam” Discourse topic mentioned above is best created bya community member close to the deceased.

The general best practice for deceased community members onDiscourse-powered forums is described on theirBest practices for deceased community memberspage.

python.org email account¶

The PSF staff member emailspostmaster@python.org to ask the emailadministrator to:

• remove SMTP access fromUSERNAME@python.org;

• reset the password to POP3/IMAP forUSERNAME@python.org;

• disable email forwarding, if set up, forUSERNAME@python.org andleave a record permanently as “in memoriam” to avoid future accountname reuse;

• remove this email from all mailing lists under@python.org;

• remove any known alternate emails for the same user from all mailinglists under@python.org.

In case the email shutdown causes issues for the estate executors, thePSF will reasonably try to help if contacted directly.

python.org admin¶

• The user’s account (/admin/users/user) is deactivated (NOT deleted)and their staff and superuser status is unchecked;

• The user’s password is reset to a long random string;

• The user’s primary email address is set toUSERNAME@in-memoriam.invalid and set as unverified;

• The user’s secondary email addresses are deleted;

• The user’s API keys (both on the account andtastypie) are deleted;

• The user’s “I would like to be a PSF Voting Member” field is cleared.

devguide.python.org¶

• The user is marked as deceased incore-team.csv;

• The user is removed from theexperts index.

bugs.python.org¶

While the issue tracker was migrated to GitHub, the Roundup instanceis still up for historical purposes.

• the PSF staff member logs intobugs.nyc1.psf.io;

• the PSF staff member runsroundup-admin to set the user’s emailaddress toUSERNAME@in-memoriam.invalid;

• the user’s alternate emails are removed;

• the user’s password is reset to a long random string;

• the PSF staff member removes any active login sessions from Postgres.

Other PSF-related infrastructure¶

• The PSF staff member notifies administrators of the Python Core DevsDiscord server to remove the user from the server. The PSF staffdoes not follow up with Discord with regards to Discord accountcancellation. The general policy regarding deceased users on Discordis available on theirDeceased or Incapacitated Userspage.

• The user is removed from Salt configuration for the PSF infrastructurein/pillar/base/usersthat allows SSH access to PSF-controlled servers.

• The user might have ran a buildbot worker. The PSF staff member willlook for that in thebuildmaster-configrepository.

PyPI¶

• The PSF staff member notifies PyPI admins by emailing them atadmin@pypi.org to mark the user as inactive, remove their emailaddresses, prohibit their password resets, and revoke all API keys.