From 51add52519cb2a2830d815be43b21c474b220d91 Mon Sep 17 00:00:00 2001 From: Petr Viktorin Date: Fri, 30 Oct 2026 12:47:29 +0100 Subject: [PATCH 1/2] Add info/process for reclaiming mannequin accounts --- core-team/join-team.rst | 4 ++++ triage/issue-tracker.rst | 7 +++++++ 2 files changed, 11 insertions(+) diff --git a/core-team/join-team.rst b/core-team/join-team.rst index a0177a460..ed8a855de 100644 --- a/core-team/join-team.rst +++ b/core-team/join-team.rst @@ -86,6 +86,10 @@ are granted through these steps: (Some of these are unofficial spaces managed as a courtesy. Adjust the list to taste.) + - If the candidate has unclaimed mannequin comments from the BPO→GitHub + migration, send an invite to reclaim them from + `🔒 Import/Export settings `__. + (See :ref:`what-on-earth-is-a-mannequin` for more info.) - Add their details to `🔒 python/voters `__. - Once the python/voters update is merged, regenerate the public team membership list at :ref:`developers`. diff --git a/triage/issue-tracker.rst b/triage/issue-tracker.rst index e55cda18c..c730a0218 100644 --- a/triage/issue-tracker.rst +++ b/triage/issue-tracker.rst @@ -201,6 +201,11 @@ that happened in the issue. In case the user did share their GitHub account name in their BPO profile, we use that. Otherwise, their classic BPO username is used instead. +For triagers and core team members, :ref:`organization owners ` +can send invitations to attribute mannequin comments to GitHub user account. +(For the administrator: use the `Import/Export settings page `_; +refer to `Github's documentation `_.) + .. _disagreement-with-a-resolution-on-the-issue-tracker: @@ -239,3 +244,5 @@ reason either as ``complete`` or ``not planned``. .. _sub-issues: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues .. _Core Development Discourse category: https://discuss.python.org/c/core-dev/23 .. _old bug tracker: https://bugs.python.org/ +.. _mannequin-reclaim-settings: https://github.com/organizations/python/settings/import-export +.. _mannequin-reclaim-docs: https://docs.github.com/en/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer#reclaiming-mannequins-in-your-browser From f6168cc7eff73c1010e531d88dda0185906b5d5f Mon Sep 17 00:00:00 2001 From: Petr Viktorin Date: Fri, 30 Oct 2026 13:30:13 +0100 Subject: [PATCH 2/2] Apply suggestion from @StanFromIreland Co-authored-by: Stan Ulbrych --- core-team/join-team.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core-team/join-team.rst b/core-team/join-team.rst index ed8a855de..775f6abb2 100644 --- a/core-team/join-team.rst +++ b/core-team/join-team.rst @@ -86,7 +86,7 @@ are granted through these steps: (Some of these are unofficial spaces managed as a courtesy. Adjust the list to taste.) - - If the candidate has unclaimed mannequin comments from the BPO→GitHub + - If the candidate has unclaimed mannequin comments from the BPO to GitHub migration, send an invite to reclaim them from `🔒 Import/Export settings `__. (See :ref:`what-on-earth-is-a-mannequin` for more info.)