SEP-994: Shared Communication Practices/Guidelines#1002
Conversation
There was a problem hiding this comment.
Thanks for making efforts to improve transparency in MCP. Just a few clarifying Q's:
- Do you see this as a clarification/standardization of existing practices, or a proposed major change?
- What about the "other" repo/discord (community/wg) - I don't see that mentioned anywhere. It seems relevant.
- What Discord server is actually being discussed here? The one called "Model Context Protocol"? https://discord.gg/6F2KaEYg ? Who is (to be) moderating that? is there (to be) accountability?
This PR says:
For real-time contributor discussion, support, and collaboration. The server is designed around MCP contributors and is not intended
to be the place for general MCP support.
So is there (to be) a more general MCP server as well? Maybe i'm not getting this, or I don't know which server we're talking about. That seems like a big change for the MCP one listed above, maybe I'm confused.
- Is there a channel (in the general sense, not just "Discord" channel) for "grievances" that contributors might wish to make privately?
- Are there any plans/commitments regarding maintenance/'triage" of Issues and Discussions? For instance there are open Issues that have not been commented on in many months.
- When (if ever) is it acceptable to "ping" maintainers about Issues/PRs that are going un-reviewed? And whom?
So yeah just a few QQ's. 🙃 Thanks this is much appreciated though.
|
Fair questions @hesreallyhim
I think there are two options for those (and doesn't necessarily need to be decided in this SEP):
No, the Discord being discussed in this SEP is the "CWG Discord". It will be owned and moderated by the MCP steering group. This is not a major change for that Discord besides a shift in positioning from "unofficial community working groups" to "official MCP contributor community". |
Co-authored-by: Tadas Antanavicius <tadas@tadasant.com>
Co-authored-by: Cliff Hall <cliff@futurescale.com>
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
Co-authored-by: Che Liu <cheliu@google.com>
|
@000-000-000-000-000 - we'll just snap to the regular SEP review process. Anyone can submit a SEP. Maintainers and core maintainers will triage the list regularly. Beyond that, folks will be able to connect with maintainers on Discord. |
|
This was voted on by @modelcontextprotocol/core-maintainers asynchronously in the current Steering Committee discord and accepted 7 - 0 (1 outstanding vote), under the assumption that we update the discord link, once the discord rework is done. We also decided to ensure that we need to setup a GH disclosure mechanism or a mailinglist. However we don't want to wait for merging this SEP until then, and will defer to only link to SECURITY.md for now. |
Co-authored-by: Paul Carleton <paulc@anthropic.com>
The SEP was previously just a placeholder. Added complete content based on the communication guidelines implementation in docs/community/communication.mdx.
…1002 The SEP was previously just a placeholder. Added complete content based on the communication guidelines implementation in docs/community/communication.mdx.
Motivation and Context
Outlines general guidelines for communication, focused on MCP contributors. This builds on the existing community work and standardizes the approach.
Types of changes
Checklist
Additional context
N/A