-
-
Notifications
You must be signed in to change notification settings - Fork 964
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
Conversation
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
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.
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.
a4f71fa to
55bd28a
Compare
AA-Turner
commented
Aug 15, 2025
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
AA-Turner
commented
Aug 26, 2025
It's been nearly two weeks, are there any further comments?
hugovk
commented
Aug 27, 2025
Other than those that were already marked "(inactive)" (and maybe "^"), shall we give the others a courtesy ping to see if they want to stay in the main index?
AA-Turner
commented
Aug 27, 2025
Hello! Per the above discussion, this PR aims to do some housekeeping on the Experts Index. If you've been pinged here, we are proposing to now list you as an "expert emeritus" for one or more topics. Please let us know if you would like any modifications to the proposed changes in this PR.
A
cc: @doerwalter @brianquinlan @avassalotti @abalkin @amauryfa @meadori @maxking @eliben @giampaolo @applio @mitsuhiko @freddrake @tarekziade @jackjansen @stevendaprano @gustaebel @rbtcollins @pjenvey @birkenfeld
avassalotti
commented
Aug 27, 2025
I would prefer to stay on the active expert list. I don't contribute PRs anymore, but I still watch and review issues around the pickle modules.
brianquinlan
commented
Aug 27, 2025
LGTM for @brianquinlan
@vstinner
vstinner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Uh oh!
There was an error while loading. Please reload this page.
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:
left = "..."entry)^entries)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/