Fair questions @hesreallyhim

What about the "other" repo/discord (community/wg) - I don't see that mentioned anywhere. It seems relevant.

I think there are two options for those (and doesn't necessarily need to be decided in this SEP):

1. Just deprecate them, take the useful bits, and put them into the official repo's. That repository is an artifact from when CWG was "unofficial" and we just needed a place to put things.
2. If we decide that Working Groups / Interest Groups want a place to store incomplete artifacts en route to writing SEPs and finalized docs, we could repurpose it explicitly for that purpose. I think this was a use case that we envisioned when starting that repo but didn't really materialize.

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?
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.

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".

Are we going to define any formal communication pattern for community to get in touch with maintainers / core maintainers? For example, community may want to get input on whether something is worth investing in e.g. someone on my team asked me how he should know whether it is worth evolving his discussion (#1055) into a SEP.

@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.