docs: align repo with contributor ladder and update rosters
This commit is contained in:
parent
aceda56a5f
commit
bf117ddccd
1 changed files with 166 additions and 89 deletions
117
GOVERNANCE.md
117
GOVERNANCE.md
|
|
@ -1,76 +1,109 @@
|
|||
# Transports Working Group Governance
|
||||
|
||||
The Transports Working Group operates under a lightweight, consensus-driven governance model aligned with the broader MCP community.
|
||||
The Transports Working Group operates under a lightweight, consensus-driven
|
||||
governance model aligned with the broader MCP community.
|
||||
|
||||
## Principles
|
||||
|
||||
1. **Open Participation** — Anyone can participate regardless of affiliation
|
||||
2. **Transparency** — All decisions are documented and publicly accessible
|
||||
3. **Consensus-Driven** — Maintainers seek agreement; objections prompt discussion
|
||||
4. **Antitrust Compliance** — All activities follow the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)
|
||||
5. **Ecosystem Alignment** — Work aligns with broader MCP goals and specifications
|
||||
3. **Consensus-Driven** — Maintainers seek agreement; objections prompt
|
||||
discussion
|
||||
4. **Antitrust Compliance** — All activities follow the [MCP Antitrust
|
||||
Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)
|
||||
5. **Ecosystem Alignment** — Work aligns with broader MCP goals and
|
||||
specifications
|
||||
|
||||
## Roles
|
||||
|
||||
### Maintainers
|
||||
|
||||
Maintainers are responsible for:
|
||||
|
||||
- Reviewing and merging pull requests
|
||||
- Coordinating meetings and setting agendas
|
||||
- Managing repository and community health
|
||||
- Making governance decisions
|
||||
- Representing the working group to the broader MCP community
|
||||
|
||||
**Current Maintainers:**
|
||||
|
||||
| Name | Organization | GitHub |
|
||||
|------|--------------|--------|
|
||||
| Kurtis Van Gent | Google | [@kurtisvg](https://github.com/kurtisvg) |
|
||||
| Basil Hosmer | Anthropic | [@bhosmer-ant](https://github.com/bhosmer-ant) |
|
||||
| Peter Alexander | Anthropic | [@pja-ant](https://github.com/pja-ant) |
|
||||
|
||||
### Active Contributors
|
||||
|
||||
Active contributors regularly participate in discussions, meetings, or code contributions. They:
|
||||
|
||||
- Have demonstrated sustained engagement
|
||||
- May receive triage permissions
|
||||
- Are recognized in this document
|
||||
|
||||
**Current Active Contributors:**
|
||||
|
||||
_None yet — get involved!_
|
||||
The Transports Working Group aligns with the [MCP Contributor
|
||||
Ladder](https://modelcontextprotocol.io/community/contributor-ladder).
|
||||
|
||||
### Contributors
|
||||
|
||||
Anyone who participates in any way:
|
||||
Anyone who participates in the project:
|
||||
|
||||
- Joining Discord discussions
|
||||
- Attending meetings
|
||||
- Opening or commenting on issues
|
||||
- Submitting pull requests
|
||||
- Reviewing proposals
|
||||
|
||||
No formal approval is needed to become a contributor.
|
||||
|
||||
### Members
|
||||
|
||||
Members are established contributors with sustained engagement. They:
|
||||
|
||||
- Have multiple contributions (code, documentation, or community)
|
||||
- Have at least one merged PR
|
||||
- Have enabled two-factor authentication on GitHub
|
||||
- Can be assigned to issues and PRs
|
||||
- Can use review commands like `/lgtm`
|
||||
|
||||
**Current Members:**
|
||||
|
||||
| Name | Organization | GitHub |
|
||||
|------------------|--------------|--------------------------------------------------------|
|
||||
| Caitie McCaffrey | Microsoft | [@CatieM20](https://github.com/CatieM20) |
|
||||
| Jonathan Hefner | - | [@jonathanhefner](https://github.com/jonathanhefner) |
|
||||
| Mark Roth | Google | [@markdroth](https://github.com/markdroth) |
|
||||
| Mike Kistler | Microsoft | [@mikekistler](https://github.com/mikekistler) |
|
||||
| Shaun Smith | Hugging Face | [@evalstate](https://github.com/evalstate) |
|
||||
|
||||
### Maintainers
|
||||
|
||||
Maintainers have demonstrated sustained commitment and leadership. They are
|
||||
responsible for:
|
||||
|
||||
- Reviewing and merging pull requests
|
||||
- Coordinating meetings and setting agendas
|
||||
- Managing repository and community health
|
||||
- Making technical and governance decisions within the WG scope
|
||||
- Representing the working group to the broader MCP community
|
||||
|
||||
**Current Maintainers:**
|
||||
|
||||
| Name | Organization | GitHub |
|
||||
|-----------------|--------------|------------------------------------------------|
|
||||
| Basil Hosmer | Anthropic | [@bhosmer-ant](https://github.com/bhosmer-ant) |
|
||||
| Kurtis Van Gent | Google | [@kurtisvg](https://github.com/kurtisvg) |
|
||||
| Peter Alexander | Anthropic | [@pja-ant](https://github.com/pja-ant) |
|
||||
|
||||
|
||||
## Decision Making
|
||||
|
||||
1. **Proposal** — Ideas are raised via GitHub issues, PRs, or meetings
|
||||
2. **Discussion** — Open discussion in Discord and GitHub
|
||||
3. **Consensus** — Maintainers seek agreement; silence implies consent
|
||||
4. **Objection Resolution** — Objections trigger further discussion until resolved
|
||||
4. **Objection Resolution** — Objections trigger further discussion until
|
||||
resolved
|
||||
5. **Documentation** — All decisions are recorded in meeting notes or GitHub
|
||||
|
||||
## Becoming a Member
|
||||
|
||||
To become a Member, a contributor must:
|
||||
|
||||
1. Have made multiple contributions to the WG (code, docs, or community).
|
||||
2. Have at least one merged PR or accepted contribution.
|
||||
3. Demonstrate ongoing engagement.
|
||||
4. Have 2FA enabled on GitHub.
|
||||
5. Be sponsored by two existing Members or Maintainers from different
|
||||
organizations (or one Core/Lead Maintainer).
|
||||
6. Have no objections from existing Members within 7 days of nomination.
|
||||
|
||||
## Becoming a Maintainer
|
||||
|
||||
Maintainer status is earned through sustained, high-quality contributions:
|
||||
Maintainer status is earned through sustained, high-quality contributions and
|
||||
leadership:
|
||||
|
||||
1. Demonstrate expertise in transport-related topics
|
||||
2. Contribute regularly over an extended period
|
||||
3. Show good judgment in technical discussions
|
||||
4. Be nominated by an existing maintainer
|
||||
5. Receive consensus approval from current maintainers
|
||||
1. Be a Member for at least 6 months.
|
||||
2. Demonstrate sustained, high-quality contributions.
|
||||
3. Demonstrate leadership in WG initiatives.
|
||||
4. Show ability to represent MCP's interests above an individual employer's
|
||||
interests.
|
||||
5. Complete security and governance onboarding (as required by the project).
|
||||
6. Be sponsored by an existing Maintainer or Core Maintainer.
|
||||
7. Be approved by the project Core Maintainers.
|
||||
|
||||
## Meeting Requirements
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue