Repository navigation
Set steering-committee and its child teams to triage on servers, inspector and quickstart-resources - #244
Open
PederHP wants to merge 2 commits into
Open
Set steering-committee and its child teams to triage on servers, inspector and quickstart-resources#244PederHP wants to merge 2 commits into
PederHP wants to merge 2 commits into
Conversation
Write access on servers now comes from the teams that own or operate the repository: reference-servers-maintainers, core-maintainers, moderators and security-ig. steering-committee and the SDK, working-group and docs teams nested under it move from push to triage, matching how they are configured on modelcontextprotocol and .github. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MqPQYQV9o5rePatonDBsmh
steering-committee and its child teams move from push to triage on inspector and quickstart-resources as well. inspector-maintainers keeps admin on inspector, and docs-maintainers keeps push on quickstart-resources, where its members do most of the merging. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MqPQYQV9o5rePatonDBsmh
PederHP
changed the title
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Permissions clean-up for
servers,inspectorandquickstart-resources, in line with the contributor ladder's "merge privileges for owned areas".Before:
steering-committeehaspushon all three repositories, and so do its child teams listed in each entry (SDK teams,sdk-maintainers,auth-maintainers,registry-wg,transport-wgand others). Because child teams inherit from their parent, about 126 people in this config have write access or higher on each repository. Most of them have no role in it.After: Those grants are
triage, the same level these teams have onmodelcontextprotocoland.github. They can still label, assign, and close issues and pull requests, and anyone can still contribute through a fork. Write access comes from the team that owns each repository, plus the grants this PR leaves alone:serversreference-servers-maintainers(admin)inspectorinspector-maintainers(admin)quickstart-resourcesdocs-maintainers(push)Unchanged on all three:
core-maintainersandlead-maintainers(all_repo_adminorg role),moderators(maintain), andsecurity-ig(admin; reviewing that grant is already tracked separately, see the README).docsis archived and left as it is.Impact on current work, from recent pull requests on each repository:
servers(last 600, since 2026-06-30): every branch pushed to the repository came from a reference servers maintainer or a bot. All but one merge was made by someone who keeps write access; the exception was a single merge by adocs-maintainersmember.inspector(last 400, since 2026-08-20): every in-repo branch and every merge came from someone who keeps write access, or a bot.quickstart-resources(all 223): most merges are by adocs-maintainersmember, which is why that team keepspush. Two people lose write access they have used: one in-repo branch from anmcpb-maintainersmember and two merges by aruby-sdkmember. Both can keep contributing through forks.How: In the three entries of
src/config/repoAccess.ts, changespushtotriageforsteering-committeeand each listed child team, exceptdocs-maintainersonquickstart-resources. The set of teams listed is unchanged, so thepulumi previewshould show only permission updates onrepo-servers,repo-inspectorandrepo-quickstart-resources. Updates the inheritance note in the README to match.npm run checkpasses (format, validate, 79 tests).🤖 Generated with Claude Code
https://claude.ai/code/session_01MqPQYQV9o5rePatonDBsmh