Apply suggestions from Den

Co-authored-by: Den Delimarsky <[email protected]>

Author: tadasant

MAINTAINERS.md

@@ -88,7 +88,7 @@ This document lists current maintainers in the Model Context Protocol project.
 
 ## Working Group & Interest Group Maintainers
 
-Working Groups and Interest Groups are not required to have maintainers (they can be managed by informal "facilitators"), but maintainers may be appointed on a case-by-case basis.
+Working Groups and Interest Groups are not required to have maintainers (they can be managed by informal facilitators), but maintainers may be appointed on an as-needed basis.
 
 ### Security Interest Group
 

docs/community/governance.mdx

@@ -70,9 +70,11 @@ Core and lead maintainers are responsible for all aspects of Model Context Proto
 
 ### Working and Interest Groups
 
-The MCP project is organized into two main structures: [Working Groups and Interest Groups](/community/working-interest-groups).
+The MCP collaboration and contributions are organized around two structures: [Working Groups and Interest Groups](/community/working-interest-groups).
 
-Interest Groups work to define _problems_ that MCP should solve by facilitating _discussions_, while Working Groups push forward specific _solutions_ by collaboratively producing _deliverables_ (in the form of SEPs or community-owned implementations of the specification). Interest Group input is a welcome (but not required) justification for creation of a Working Group. Interest Group or Working Group input is collectively a welcome (but not required) input into a SEP or other community contribution.
+Interest Groups are responsible for identifying and articulating problems that MCP should address, primarily by facilitating open discussions within the community. In contrast, Working Groups focus on developing concrete solutions by collaboratively producing deliverables, such as SEPs or community-owned implementations of the specification. While input from Interest Groups can help justify the formation of a Working Group, it is not a strict requirement. Similarly, contributions from either Interest Groups or Working Groups are encouraged, but not mandatory, when submitting SEPs or other community proposals.
+
+We strongly encourage all contributors interested in working on a specific SEP to first collaborate within an Interest Group. This collaborative process helps ensure that the proposed SEP aligns with protocol needs and is the right direction for its adopters.
 
 #### Governance Principles
 

docs/community/working-interest-groups.mdx

@@ -3,64 +3,67 @@ title: Working and Interest Groups
 description: Learn about the two forms of collaborative groups within the Model Context Protocol's governance structure: Working Groups and Interest Groups.
 ---
 
-Interest Groups work to define _problems_ that MCP should solve by facilitating _discussions_, while Working Groups push forward specific _solutions_ by collaboratively producing _deliverables_ (in the form of SEPs or community-owned implementations of the specification). Interest Group input is a welcome (but not required) justification for creation of a Working Group. Interest Group or Working Group input is collectively a welcome (but not required) input into a SEP or other community contribution.
+Interest Groups are responsible for identifying and articulating problems that MCP should address, primarily by facilitating open discussions within the community. In contrast, Working Groups focus on developing concrete solutions by collaboratively producing deliverables, such as SEPs or community-owned implementations of the specification. While input from Interest Groups can help justify the formation of a Working Group, it is not a strict requirement. Similarly, contributions from either Interest Groups or Working Groups are encouraged, but not mandatory, when submitting SEPs or other community proposals.
 
-Long-running Projects (such as SDKs, Inspector, Registry, etc) are maintained by a Working Group dedicated to each respective Project.
+We strongly encourage all contributors interested in working on a specific SEP to first collaborate within an Interest Group. This collaborative process helps ensure that the proposed SEP aligns with community needs and is the right direction for the protocol.
+
+Long-term projects in the MCP ecosystem, such as SDKs, Inspector, or Registry are maintained by a dedicated Working Group.
 
 ## Purpose
 
 These groups exist to:
 
-- **Facilitate high signal spaces for discussion** such that those opting into notifications and meetings feel most content is relevant to them and they can meaningfully contribute their experience and learn from others
-- **Create norms, expectations, and single points of involved leadership** around making collaborative progress towards concrete deliverables that help evolve MCP
+- **Facilitate high-signal spaces for focused discussions** - contributors who opt into notifications, expertise sharing, and regular meetings can engage with topics that are highly relevant to them, enabling meaningful contributions and opportunities to learn from others.
+- **Establish clear expectations and leadership roles** - guide collaborative efforts and ensure steady progress toward concrete deliverables that advance MCP evolution and adoption.
 
 ## Mechanisms
 
 ### Interest Groups (IGs)
 
-**Goal**: facilitate discussion and knowledge-sharing among MCP community members with similar interests surrounding some MCP sub-topic or context. The focus is on collecting _problems_ that may or may not be worth solving with SEPs or other community artifacts.
+**Goal:** Facilitate discussion and knowledge-sharing among MCP contributors who share interests in a specific MCP sub-topic or context. The primary focus is on identifying and gathering problems that may be worth addressing through SEPs or other community artifacts, while encouraging open exploration of protocol issues and opportunities.
 
 **Expectations**:
 
-- Some regular cadence of async conversations in the corresponding Discord channel
-- AND/OR a recurring live meeting attended by 3+ unaffiliated individuals
+- Regular conversations in the Interest Group Discord channel
+- **AND/OR** a recurring live meeting regularly attended by Interest Group members
 
 **Examples**:
 
 - Security in MCP
 - Auth in MCP
-- Using MCP in an internal enterprise setting
+- Using MCP in enterprise settings
 - Tooling and practices surrounding hosting MCP servers
 - Tooling and practices surrounding implementing MCP clients
 
 **Lifecycle**:
 
 - Creation begins by filling out a template in the \#wg-ig-group-creation [Discord](/community/communication#discord) channel
-- A community moderator will review and call for a vote in the (private) \#community-moderators Discord channel. Majority positive vote by members over a 72h period approves creation of the group. Can be reversed at any time (e.g. after more input comes in). Core and lead maintainers can veto.
+- A community moderator will review and call for a vote in the (private) \#community-moderators Discord channel. Majority positive vote by members over a 72h period approves creation of the group.
+  - The creation of the group can be reversed at any time (e.g., after new information surfaces). Core and lead maintainers can veto.
 - Facilitator(s) and Maintainer(s) responsible for organizing IG into meeting expectations
   - Facilitator is an informal role responsible for shepherding or speaking for a group
-  - Maintainer is an official representative from the MCP steering group (not required for every group to have this)
-- IG is retired only when community moderators or core+ maintainers decide it is not meeting expectations
-  - This means successful IG’s will live on in perpetuity
+  - Maintainer is an official representative from the MCP steering group. A maintainer is not required for every group, but can help advocate for specific changes or initiatives.
+- IG is retired only when community moderators or Core or Lead Maintainers determine it's no longer active and/or needed
+  - Successful IGs do not have a time limit or expiration date - as long as they are active and maintained, they will remain available
 
 **Creation Template**:
 
 - Facilitator(s)
 - Maintainer(s) (optional)
-- Flag potential overlap with other IG’s
-- How this IG differentiates itself from the related IG’s
-- First topic you want to discuss
+- IGs with potentially similar goals/discussions
+- How this IG differentiates itself from the related IGs
+- First topic you to discuss within the IG
 
-There is no requirement to be part of an IG to start a WG, or even to start a SEP. However, forming consensus in IG’s to support justifying the creation of a WG is often a good idea. Similarly, citing IG or WG support of a SEP helps the SEP as well.
+Participation in an Interest Group (IG) is not required to start a Working Group (WG) or to create a SEP. However, building consensus within IGs can be valuable when justifying the formation of a WG. Likewise, referencing support from IGs or WGs can strengthen a SEP and its chances of success.
 
 ### Working Groups (WG)
 
-**Goal**: facilitate MCP community collaboration on a specific SEP, themed series of SEPs, or officially endorsed Project.
+**Goal:** Facilitate collaboration within the MCP community on a SEP, a themed series of SEPs, or an otherwise officially endorsed project.
 
 **Expectations**:
 
-- Monthly progress towards at least one SEP or spec-related implementation OR holds maintenance responsibilities for a Project
-- Facilitator(s) is/are responsible for fielding status update requests by community moderators or maintainers
+- Meaningful progress towards at least one SEP or spec-related implementation **OR** hold maintenance responsibilities for a project (e.g., Inspector, Registry, SDKs)
+- Facilitators are responsible for keeping track of progress and communicating status when appropriate
 
 **Examples**:
 
@@ -72,38 +75,41 @@ There is no requirement to be part of an IG to start a WG, or even to start a SE
 **Lifecycle**:
 
 - Creation begins by filling out a template in \#wg-ig-group-creation Discord channel
-- A community moderator will review and call for a vote in the (private) \#community-moderators Discord channel. Majority positive vote by members over a 72h period approves creation of the group. Can be reversed at any time (e.g. after more input comes in). Core and lead maintainers can veto.
+- A community moderator will review and call for a vote in the (private) \#community-moderators Discord channel. Majority positive vote by members over a 72h period approves creation of the group.
+  - The creation of the group can be reversed at any time (e.g., after new information surfaces). Core and lead maintainers can veto.
 - Facilitator(s) and Maintainer(s) responsible for organizing WG into meeting expectations
   - Facilitator is an informal role responsible for shepherding or speaking for a group
-  - Maintainer is an official representative from the MCP steering group (not required for every group to have this)
+  - Maintainer is an official representative from the MCP steering group. A maintainer is not required for every group, but can help advocate for specific changes or initiatives
 - WG is retired when either:
-  - Community moderators or core+ maintainers decide it is not meeting expectations
-  - The WG does not have a WIP Issue/PR for at least a month, or has completed all Issues/PRs it intends to pursue.
+  - Community moderators or Core and Lead Maintainers decide it is no longer active and/or needed
+  - The WG no longer has an active Issue/PR for a month or more, or has completed all Issues/PRs it intended to pursue.
 
 **Creation Template**:
 
 - Facilitator(s)
 - Maintainer(s) (optional)
-- Explanation of interest/use cases (ideally from an IG but can come from anywhere)
-- First Issue/PR/SEP you intend to procure
+- Explanation of interest/use cases, ideally originating from an IG discussion; however that is not a requirement
+- First Issue/PR/SEP that the WG will work on
 
 ## WG/IG Facilitators
 
-A “Facilitator” role in a WG or IG does _not_ result in a [maintainership role](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) across the MCP organization. It is an informal role into which anyone can self-nominate, responsible for helping shepherd discussions and collaboration within the group.
+A **Facilitator** role in a WG or IG does _not_ result in a [maintainership role](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) across the MCP organization. It is an informal role into which anyone can self-nominate.
+
+A Facilitator is responsible for helping shepherd discussions and collaboration within an Interest or Working Group.
 
-Core Maintainers reserve the right to modify the list of Facilitators and Maintainers for any WG/IG at any time.
+Lead and Core Maintainers reserve the right to modify the list of Facilitators and Maintainers for any WG/IG at any time.
 
 ## FAQ
 
-> How do I get involved contributing to MCP?
+### How do I get involved contributing to MCP?
 
 These IG and WG abstractions help provide an elegant on-ramp:
 
 1. Join the Discord, follow the conversation in IGs relevant to you. Attend live calls. Participate.
 2. Offer to facilitate calls. Contribute your use cases in SEP proposals and other work.
 3. When you're comfortable contributing to deliverables, jump in to contribute to WG work.
-4. Do this for a period of time, get noticed by WG maintainers to get nominated as a new maintainer.
+4. Active and valuable contributors will be nominated by WG maintainers as a new maintainer.
 
-> Where can I find a list of all current WGs and IGs?
+### Where can I find a list of all current WGs and IGs?
 
-On the [MCP Contributor Discord](/community/communication#discord), there is a section of channels for each Working Groups and Interest Groups.
+On the [MCP Contributor Discord](/community/communication#discord), there is a section of channels for each Working and Interest Group.