modelcontextprotocol/transports-wg
Watch
1
0
Fork
You've already forked transports-wg
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
transports-wg/GOVERNANCE.md
Peter Alexander e59b5192ec
 Update meeting details and focus areas 
- Change meeting day to Wednesdays at 1pm PT
- Remove antitrust reminder from meeting agenda (policy still applies)
- Remove public notes mention (not currently available)
- Remove Interoperability from focus areas
2026-01-08 13:20:15 +00:00

2.9 KiB
Raw Blame History

Transports Working Group Governance

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
  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
TBD TBD TBD

Note: Initial maintainers to be added as the working group forms.

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:

Name Organization GitHub
TBD TBD TBD

Contributors

Anyone who participates in any way:

  • Joining Discord discussions
  • Attending meetings
  • Opening or commenting on issues
  • Submitting pull requests
  • Reviewing proposals

No formal approval is needed to become a contributor.

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
  5. Documentation — All decisions are recorded in meeting notes or GitHub

Becoming a Maintainer

Maintainer status is earned through sustained, high-quality contributions:

  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

Meeting Requirements

All meetings must include:

  • Published agenda (48+ hours in advance)
  • Open attendance for all participants

Amendments

Governance changes require:

  1. Proposal via GitHub issue or PR
  2. Community discussion period
  3. Maintainer consensus
  4. Documented rationale for the change

Contact

Questions about governance can be directed to:

  • The #transports-wg Discord channel
  • GitHub Issues in this repository
  • Current maintainers directly