Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
AA-Turner wants to merge6 commits intopython:main
base:main
Choose a base branch
Loading
fromAA-Turner:prune-experts

Conversation

@AA-Turner
Copy link
Member

@AA-TurnerAA-Turner commentedAug 14, 2025
edited by github-actionsbot
Loading

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 aleft = "..." 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

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.

StanFromIreland and malemburg reacted with thumbs up emoji

@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.

malemburg
malemburg previously requested changesAug 15, 2025
@AA-Turner
Copy link
MemberAuthor

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

willingc reacted with thumbs up emoji

@AA-Turner
Copy link
MemberAuthor

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

@hugovk
Copy link
Member

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 reacted with thumbs up emoji

@AA-Turner
Copy link
MemberAuthor

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.

hugovk and AA-Turner reacted with thumbs up emojiStanFromIreland reacted with heart emoji

@brianquinlan
Copy link

LGTM for@brianquinlan

Copy link
Member

@vstinnervstinner 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 freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@encukouencukouencukou left review comments

@willingcwillingcwillingc left review comments

@StanFromIrelandStanFromIrelandStanFromIreland left review comments

@vstinnervstinnervstinner approved these changes

@merwokmerwokAwaiting requested review from merwok

@hugovkhugovkAwaiting requested review from hugovk

@MariattaMariattaAwaiting requested review from Mariatta

@ezio-melottiezio-melottiAwaiting requested review from ezio-melotti

@malemburgmalemburgAwaiting requested review from malemburg

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

9 participants

@AA-Turner@encukou@malemburg@hugovk@avassalotti@brianquinlan@vstinner@willingc@StanFromIreland

[8]ページ先頭

©2009-2025 Movatter.jp