Update the peers list #3482
Open
Update the peers list #3482
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ddbeck
requested review from
Elchi3,
Fyrd,
LeoMcA,
atopal,
captainbrosset,
dfabulich,
foolip and
jgraham
github-actions
bot
added
the
documentation
dfabulich
approved these changes
Oct 22, 2025
LeoMcA
approved these changes
Oct 23, 2025
Elchi3
approved these changes
Oct 23, 2025
captainbrosset
approved these changes
Oct 29, 2025
|
@ddbeck this looks ready for you to merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This edits the governance doc, mostly to refresh the peers list to reflect currently active contributors. Specifically:
Add Rick Viscomi (@rviscomi) to the peers list. Rick was granted commit access to the repo, but never formally named as a peer. We ought to resolve this discrepancy.
Move several names to the emeriti list. These contributors have not recently been active on the project, so probably shouldn't be @-mentioned on issues and PRs. If they'd like to return, they're welcome to ask to be reinstated. In the mean time, we ought to deactivate their elevated repo privileges, as a security precaution.
The governance process requires owners' approval for these changes. I won't merge this without a couple owner approvers (and no objections).