Skip to content

Commit b34e47d

Browse files
dsp-antdsp-ant
committed
Update SEP-994 with full content from merged PR modelcontextprotocol#1002
The SEP was previously just a placeholder. Added complete content based on the communication guidelines implementation in docs/community/communication.mdx.
1 parent 528d6a1 commit b34e47d

3 files changed

Lines changed: 205 additions & 28 deletions

File tree

‎docs/community/seps/994-shared-communication-practicesguidelines.mdx‎

Lines changed: 105 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -8,33 +8,117 @@ import { Badge } from "/snippets/badge.mdx";
88

99
<div className="flex items-center gap-2 mb-4">
1010
<Badge color="green">Final</Badge>
11-
<Badge color="gray">Standards Track</Badge>
11+
<Badge color="gray">Process</Badge>
1212
</div>
1313

14-
| Field | Value |
15-
| ------------- | ---------------------------------------------------------------------- |
16-
| **SEP** | 994 |
17-
| **Title** | Shared Communication Practices/Guidelines |
18-
| **Status** | Final |
19-
| **Type** | Standards Track |
20-
| **Created** | 2025-07-17 |
21-
| **Author(s)** | localden |
22-
| **Sponsor** | None |
23-
| **PR** | [#994](https://github.com/modelcontextprotocol/specification/pull/994) |
14+
| Field | Value |
15+
| ------------- | ----------------------------------------- |
16+
| **SEP** | 994 |
17+
| **Title** | Shared Communication Practices/Guidelines |
18+
| **Status** | Final |
19+
| **Type** | Process |
20+
| **Created** | 2025-07-17 |
21+
| **Author(s)** | [@localden](https://github.com/localden) |
22+
| **Sponsor** | None |
23+
| **PR** | [#994](#1002) |
2424

2525
---
2626

27-
# SEP-994: Shared Communication Practices/Guidelines
27+
## Abstract
2828

29-
- **Status**: Final
30-
- **Type**: Standards Track
31-
- **Created**: 2025-07-17
32-
- **Author(s)**: localden
33-
- **Issue**: #994
29+
This SEP establishes the communication strategy and framework for the Model Context Protocol community. It defines the official channels for contributor communication, guidelines for their use, and processes for decision documentation.
3430

35-
> [!NOTE]
36-
> This is **draft placeholder** for the detailed SEP.
31+
## Motivation
3732

38-
Outline the shared practices and locations for MCP-related communication/community.
33+
As the MCP community grows, clear communication guidelines are essential for:
3934

40-
Related change: https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1002
35+
- **Consistency**: Ensuring all contributors know where and how to communicate
36+
- **Transparency**: Making project decisions visible and accessible
37+
- **Efficiency**: Directing discussions to the most appropriate channels
38+
- **Security**: Establishing proper processes for handling sensitive issues
39+
40+
## Specification
41+
42+
### Communication Channels
43+
44+
The MCP project uses three primary communication channels:
45+
46+
1. **Discord**: For real-time or ad-hoc discussions among contributors
47+
2. **GitHub Discussions**: For structured, longer-form discussions
48+
3. **GitHub Issues**: For actionable tasks, bug reports, and feature requests
49+
50+
Security-sensitive issues follow a separate process defined in SECURITY.md.
51+
52+
### Discord Guidelines
53+
54+
The Discord server is designed for **MCP contributors** and is not intended for general MCP support.
55+
56+
#### Public Channels (Default)
57+
58+
- Open community engagement and collaborative development
59+
- SDK and tooling development discussions
60+
- Working and Interest Group discussions
61+
- Community onboarding and contribution guidance
62+
- Office hours and maintainer availability
63+
64+
#### Private Channels (Exceptions)
65+
66+
Private channels are reserved for:
67+
68+
- Security incidents (CVEs, protocol vulnerabilities)
69+
- People matters (maintainer discussions, code of conduct)
70+
- Coordination requiring immediate focused response
71+
72+
All technical and governance decisions must be documented publicly in GitHub.
73+
74+
### GitHub Discussions
75+
76+
Used for structured, long-form discussion:
77+
78+
- Project roadmap planning
79+
- Announcements and release communications
80+
- Community polls and consensus-building
81+
- Feature requests with context and rationale
82+
83+
### GitHub Issues
84+
85+
Used for actionable items:
86+
87+
- Bug reports with reproducible steps
88+
- Documentation improvements
89+
- CI/CD and infrastructure issues
90+
- Release tasks and milestone tracking
91+
92+
### Decision Records
93+
94+
All MCP decisions are documented publicly:
95+
96+
- **Technical decisions**: GitHub Issues and SEPs
97+
- **Specification changes**: Changelog on the MCP website
98+
- **Process changes**: Community documentation
99+
- **Governance decisions**: GitHub Issues and SEPs
100+
101+
Decision documentation includes:
102+
103+
- Decision makers
104+
- Background context and motivation
105+
- Options considered
106+
- Rationale for chosen approach
107+
- Implementation steps
108+
109+
## Rationale
110+
111+
This framework balances openness with practicality:
112+
113+
- **Public by default**: Maximizes transparency and community participation
114+
- **Private when necessary**: Protects security and personal matters
115+
- **Channel separation**: Keeps discussions organized and searchable
116+
- **Documentation requirements**: Ensures decisions are preserved and discoverable
117+
118+
## Backward Compatibility
119+
120+
This SEP establishes new processes and does not affect existing protocol functionality.
121+
122+
## Reference Implementation
123+
124+
The communication guidelines are published at: https://modelcontextprotocol.io/community/communication

‎docs/community/seps/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Specification Enhancement Proposals (SEPs) are the primary mechanism for proposi
2525
| [SEP-1319](/community/seps/1319-decouple-request-payload-from-rpc-methods-definiti) | Decouple Request Payload from RPC Methods Definition | <Badge color="green">Final</Badge> | Standards Track | 2025-08-08 |
2626
| [SEP-1302](/community/seps/1302-formalize-working-groups-and-interest-groups-in-mc) | Formalize Working Groups and Interest Groups in MCP Governance | <Badge color="green">Final</Badge> | Standards Track | 2025-08-05 |
2727
| [SEP-1046](/community/seps/1046-support-oauth-client-credentials-flow-in-authoriza) | Support OAuth client credentials flow in authorization | <Badge color="green">Final</Badge> | Standards Track | 2025-07-23 |
28-
| [SEP-994](/community/seps/994-shared-communication-practicesguidelines) | Shared Communication Practices/Guidelines | <Badge color="green">Final</Badge> | Standards Track | 2025-07-17 |
28+
| [SEP-994](/community/seps/994-shared-communication-practicesguidelines) | Shared Communication Practices/Guidelines | <Badge color="green">Final</Badge> | Process | 2025-07-17 |
2929
| [SEP-990](/community/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o) | Enable enterprise IdP policy controls during MCP OAuth flows | <Badge color="green">Final</Badge> | Standards Track | 2025-06-04 |
3030
| [SEP-986](/community/seps/986-specify-format-for-tool-names) | Specify Format for Tool Names | <Badge color="green">Final</Badge> | Standards Track | 2025-07-16 |
3131
| [SEP-985](/community/seps/985-align-oauth-20-protected-resource-metadata-with-rf) | Align OAuth 2.0 Protected Resource Metadata with RFC 9728 | <Badge color="green">Final</Badge> | Standards Track | 2025-07-16 |

‎seps/994-shared-communication-practicesguidelines.md‎

Lines changed: 99 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,107 @@
11
# SEP-994: Shared Communication Practices/Guidelines
22

33
- **Status**: Final
4-
- **Type**: Standards Track
4+
- **Type**: Process
55
- **Created**: 2025-07-17
6-
- **Author(s)**: localden
6+
- **Author(s)**: @localden
77
- **Issue**: #994
8+
- **PR**: #1002
89

9-
> [!NOTE]
10-
> This is **draft placeholder** for the detailed SEP.
10+
## Abstract
1111

12-
Outline the shared practices and locations for MCP-related communication/community.
12+
This SEP establishes the communication strategy and framework for the Model Context Protocol community. It defines the official channels for contributor communication, guidelines for their use, and processes for decision documentation.
1313

14-
Related change: https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1002
14+
## Motivation
15+
16+
As the MCP community grows, clear communication guidelines are essential for:
17+
18+
- **Consistency**: Ensuring all contributors know where and how to communicate
19+
- **Transparency**: Making project decisions visible and accessible
20+
- **Efficiency**: Directing discussions to the most appropriate channels
21+
- **Security**: Establishing proper processes for handling sensitive issues
22+
23+
## Specification
24+
25+
### Communication Channels
26+
27+
The MCP project uses three primary communication channels:
28+
29+
1. **Discord**: For real-time or ad-hoc discussions among contributors
30+
2. **GitHub Discussions**: For structured, longer-form discussions
31+
3. **GitHub Issues**: For actionable tasks, bug reports, and feature requests
32+
33+
Security-sensitive issues follow a separate process defined in SECURITY.md.
34+
35+
### Discord Guidelines
36+
37+
The Discord server is designed for **MCP contributors** and is not intended for general MCP support.
38+
39+
#### Public Channels (Default)
40+
41+
- Open community engagement and collaborative development
42+
- SDK and tooling development discussions
43+
- Working and Interest Group discussions
44+
- Community onboarding and contribution guidance
45+
- Office hours and maintainer availability
46+
47+
#### Private Channels (Exceptions)
48+
49+
Private channels are reserved for:
50+
51+
- Security incidents (CVEs, protocol vulnerabilities)
52+
- People matters (maintainer discussions, code of conduct)
53+
- Coordination requiring immediate focused response
54+
55+
All technical and governance decisions must be documented publicly in GitHub.
56+
57+
### GitHub Discussions
58+
59+
Used for structured, long-form discussion:
60+
61+
- Project roadmap planning
62+
- Announcements and release communications
63+
- Community polls and consensus-building
64+
- Feature requests with context and rationale
65+
66+
### GitHub Issues
67+
68+
Used for actionable items:
69+
70+
- Bug reports with reproducible steps
71+
- Documentation improvements
72+
- CI/CD and infrastructure issues
73+
- Release tasks and milestone tracking
74+
75+
### Decision Records
76+
77+
All MCP decisions are documented publicly:
78+
79+
- **Technical decisions**: GitHub Issues and SEPs
80+
- **Specification changes**: Changelog on the MCP website
81+
- **Process changes**: Community documentation
82+
- **Governance decisions**: GitHub Issues and SEPs
83+
84+
Decision documentation includes:
85+
86+
- Decision makers
87+
- Background context and motivation
88+
- Options considered
89+
- Rationale for chosen approach
90+
- Implementation steps
91+
92+
## Rationale
93+
94+
This framework balances openness with practicality:
95+
96+
- **Public by default**: Maximizes transparency and community participation
97+
- **Private when necessary**: Protects security and personal matters
98+
- **Channel separation**: Keeps discussions organized and searchable
99+
- **Documentation requirements**: Ensures decisions are preserved and discoverable
100+
101+
## Backward Compatibility
102+
103+
This SEP establishes new processes and does not affect existing protocol functionality.
104+
105+
## Reference Implementation
106+
107+
The communication guidelines are published at: https://modelcontextprotocol.io/community/communication

0 commit comments

Comments
 (0)