Skip to content

Commit 7d65ac0

Browse files
localdentadasantcliffhalljonathanhefnerkoic
authored
SEP-994: Shared Communication Practices/Guidelines (modelcontextprotocol#1002)
* Create communication.mdx * Update communication.mdx * Update docs/community/communication.mdx Co-authored-by: Tadas Antanavicius <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Cliff Hall <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update communication.mdx * Update communication.mdx * Update communication.mdx * Update communication.mdx * Update docs/community/communication.mdx Co-authored-by: Cliff Hall <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Cliff Hall <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Tadas Antanavicius <[email protected]> * Update docs.json * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Jonathan Hefner <[email protected]> * Update docs/community/communication.mdx Co-authored-by: Koichi ITO <[email protected]> * Update communication.mdx * CoC reference * Update docs/community/communication.mdx Co-authored-by: David Soria Parra <[email protected]> * Update docs/community/communication.mdx Co-authored-by: David Soria Parra <[email protected]> * Update docs/community/communication.mdx Co-authored-by: David Soria Parra <[email protected]> * Update communication.mdx * Update docs/community/communication.mdx Co-authored-by: Che Liu <[email protected]> * Update communication.mdx * Update docs/community/communication.mdx Co-authored-by: Paul Carleton <[email protected]> --------- Co-authored-by: Tadas Antanavicius <[email protected]> Co-authored-by: Cliff Hall <[email protected]> Co-authored-by: Jonathan Hefner <[email protected]> Co-authored-by: Koichi ITO <[email protected]> Co-authored-by: David Soria Parra <[email protected]> Co-authored-by: Che Liu <[email protected]> Co-authored-by: Paul Carleton <[email protected]>
1 parent 0298beb commit 7d65ac0

File tree

2 files changed

+99
-0
lines changed

2 files changed

+99
-0
lines changed

‎docs/community/communication.mdx‎

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
---
2+
title: Contributor Communication
3+
description: Communication strategy and framework for the Model Context Protocol community
4+
---
5+
6+
This document provides practical guidance for communicating and collaborating within the Model Context Protocol (MCP) project. It outlines the communication channels, workflows, and processes used by the MCP community.
7+
8+
All communication within the MCP community is governed by our [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md). We expect all participants to maintain respectful, professional, and inclusive interactions across all channels.
9+
10+
## Communication Channels
11+
12+
We support three primary communication channels: the public Discord server, [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues), and [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) in the [main project repository](https://github.com/modelcontextprotocol/modelcontextprotocol).
13+
14+
### Discord
15+
16+
For real-time contributor discussion and collaboration. The server is designed around **MCP contributors** and is not intended
17+
to be a place for general MCP support.
18+
19+
The Discord server will have both public and private channels.
20+
21+
#### Public Channels (Default)
22+
23+
- **Purpose**: Open community engagement, collaborative development, and transparent project coordination.
24+
- Primary use cases:
25+
- **Public SDK and tooling development**: All development, from ideation to release planning, happens in public channels (e.g., `#typescript-sdk-dev`, `#inspector-dev`).
26+
- **Working and interest group discussions** (`#client-implementors`, `#agents-wg`, etc.)
27+
- **Working Group**: Some specific goal or project in mind (such as an SDK, inspector, registry, server-identity, load-balancing, etc).
28+
- **Interest Group**: An abstract gathering of folks that might raise a range of various topics. Some might get actioned on as one-offs, others might spin into Working Groups.
29+
- **Community onboarding** and contribution guidance.
30+
- **Community feedback** and collaborative brainstorming.
31+
- Public **office hours** and **maintainer availability**.
32+
- Avoid:
33+
- MCP user support: participants are expected to read official documentation and start new GitHub Discussions for questions or support.
34+
- Service or product marketing: interactions on this Discord are expected to be vendor-neutral and not used for brand-building or sales. Mentions of brands or products are discouraged outside of being used as examples or responses to conversations that start off focused on the specification.
35+
36+
#### Private channels (Exceptions)
37+
38+
- **Purpose**: Confidential coordination and sensitive matters that cannot be discussed publicly. Access will be restricted to designated maintainers.
39+
- **Strict criteria for private use**:
40+
- **Security incidents** (CVEs, protocol vulnerabilities).
41+
- **People matters** (maintainer-related discussions, code of conduct policies).
42+
- Select channels will be configured to be **read-only**. This can be good for example for maintainer decision making.
43+
- Coordination requiring **immediate** or otherwise **focused response** with a limited audience.
44+
- **Transparency**:
45+
- **All technical and governance decisions** affecting the community **must be documented** in GitHub Discussions and/or Issues, and will be labeled with `notes`.
46+
- **Some matters related to individual contributors** may remain private when appropriate (e.g., personal circumstances, disciplinary actions, or other sensitive individual matters).
47+
- Private channels are to be used as **temporary "incident rooms,"** not for routine development.
48+
49+
Any significant discussion on Discord that leads to a potential decision or proposal must be moved to a GitHub Discussion or GitHub Issue to create a persistent, searchable record. Proposals will then be promoted to full-fledged PRs with associated work items (GitHub Issues) as needed.
50+
51+
### GitHub Discussions
52+
53+
For structured, long-form discussion and debate on project direction, features, improvements, and community topics.
54+
55+
When to use:
56+
57+
- Project roadmap planning and milestone discussions
58+
- Announcements and release communications
59+
- Community polls and consensus-building processes
60+
- Feature requests with context and rationale
61+
- If a particular repository does not have GitHub Discussions enabled, feel free to open a GitHub Issue instead.
62+
63+
### GitHub Issues
64+
65+
For bug reports, feature tracking, and actionable development tasks.
66+
67+
When to use:
68+
69+
- Submit SEP proposals (following the [SEP guidelines](./sep-guidelines))
70+
- Bug reports with reproducible steps
71+
- Documentation improvements with specific scope
72+
- CI/CD problems and infrastructure issues
73+
- Release tasks and milestone tracking
74+
75+
### Security Issues
76+
77+
**Do not post security issues publicly.** Instead:
78+
79+
1. Use the private security reporting process. For protocol-level security issues, follow the process in [SECURITY.md in the modelcontextprotocol GitHub repository](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/SECURITY.md).
80+
2. Contact lead and/or [core maintainers](./governance#current-core-maintainers) directly.
81+
3. Follow responsible disclosure guidelines.
82+
83+
## Decision Records
84+
85+
All MCP decisions are documented and captured in public channels.
86+
87+
- **Technical decisions**: [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs.
88+
- **Specification changes**: [On the Model Context Protocol website](https://modelcontextprotocol.io/specification/draft/changelog).
89+
- **Process changes**: [Community documentation](https://modelcontextprotocol.io/community/governance).
90+
- **Governance decisions and updates**: [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs.
91+
92+
When documenting decisions, we will retain as much context as possible:
93+
94+
- Decision makers
95+
- Background context and motivation
96+
- Options that were considered
97+
- Rationale for the chosen approach
98+
- Implementation steps

‎docs/docs.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -281,6 +281,7 @@
281281
"pages": [
282282
"community/governance",
283283
"community/sep-guidelines",
284+
"community/communication",
284285
"development/roadmap",
285286
"development/contributing",
286287
"clients",

0 commit comments

Comments
 (0)