Skip to content

Prune entries from the Experts Index #1635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Aug 14, 2025

We suggest and recommend using the Experts Index for contributors to find a relevant committer/core developer to review a PR or comment on an issue/proposal. Listing names of inactive committers, those who have left the team, or those that never moved from BPO to GitHub can create a frustrating contributor experience.

I've split this change into 5 commits:

  • Remove all entries marked as "inactive"
  • Remove all those marked "inactive" by the voters script (i.e. no commits in the last 2 years and no explict 'stay active' response)
  • Remove all those who are marked as no longer a core developer (with a left = "..." entry)
  • Remove all former BPO usernames (^ entries)
  • Remove all those with no commits in the last 5 years, regardless of 'stay active' voter status

We can of course re-add people at any time, this is more of a housekeeping activity than anything else.

A

(I've requested review from the currently listed devguide experts: @merwok @ezio-melotti @willingc @Mariatta @hugovk)


📚 Documentation preview 📚: https://cpython-devguide--1635.org.readthedocs.build/

memory management tim-one, malemburg, Yhg1s, nascheme
locale
mathematics rhettinger, serhiy-storchaka
memory management tim-one, Yhg1s, nascheme
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tim-one -- Tim, you were caught in this because your entries for difflib, doctest, and tabnanny were marked as "inactive". Would you like to still be listed here for memory management and/or restore any of the removed entries?

@encukou
Copy link
Member

encukou commented Aug 15, 2025

IMO, starting with people who didn't make the GitHub transition would make this much more straightforward.

What about adding an “emeriti” table at the end (mapping names to interest areas), to allow restoring the entries quickly -- and determining experts (on things like original design choices) in case the person does add a comment somewhere.

@malemburg
Copy link
Member

IMO, starting with people who didn't make the GitHub transition would make this much more straightforward.

What about adding an “emeriti” table at the end (mapping names to interest areas), to allow restoring the entries quickly -- and determining experts (on things like original design choices) in case the person does add a comment somewhere.

Agreed. I think this is also needed, since people would otherwise feel kicked out from their expert status (even when they don't contribute to CPython anymore, they are most likely still experts in the resp. fields).

It's also a way to thank people who have invested a great amount of time in those areas in the past.

@AA-Turner
Copy link
Member Author

Please excuse the force-push, I've re-ordered the commits to align with @encukou & @malemburg's suggestion of removing pre-GH transition users first, and also adding a new "Experts Emeritus" section.

A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants