Skip to content

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/

@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

@AA-Turner
Copy link
Member Author

It's been nearly two weeks, are there any further comments?

@hugovk
Copy link
Member

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
Copy link
Member Author

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
Copy link
Member

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
Copy link

LGTM for @brianquinlan

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

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

LGTM

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.

9 participants