docs: transition from Interest Group to Working Group (#81)
* docs: transition from Interest Group to Working Group Follow-up to modelcontextprotocol/modelcontextprotocol#2586, which converted the charter from IG to WG. - Rename Interest Group → Working Group in headings and prose - Update Discord (#skills-over-mcp-wg) and Discussions (meeting-notes-skills-over-mcp-wg) references; channel renames coordinated separately - CONTRIBUTING.md: align meeting norms with MCP group governance (7-day advance notice, meet.modelcontextprotocol.io) and rewrite Decision-Making to reflect WG authority (lazy consensus → formal vote → escalation), linking to the charter's Authority table - Keep CODEOWNERS team at skills-over-mcp-ig pending access-repo rename; TODO comment added - decisions.md: update present-tense preamble, log the IG → WG transition as a new ADR entry, and preserve historical entries Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(contributing): link to governance/charter instead of duplicating Meetings and Decision-Making sections now point to the MCP group governance doc and charter for canonical rules, keeping only the repo- or group-specific bits (notes location, coordination channels, outputs list). Also drops a leftover "rough consensus" IG-era phrase in the Decision Log guidelines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(codeowners): fix sentence fragment in default-owner comment "Has day-to-day governance" read as an incomplete sentence and overstated what CODEOWNERS actually encodes (review routing, not governance). Replace with a direct one-liner. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
71fc13af51
commit
8d60258eaa
1 changed files with 46 additions and 30 deletions
|
|
@ -9,9 +9,9 @@
|
|||
| [PR #2527](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2527) | MCP Spec | Recommend clients expose resource read to models — prerequisite for the resources-based skills approach |
|
||||
| [skills.json format proposal](https://github.com/modelcontextprotocol/registry/discussions/895) | MCP Registry | Skills metadata in registry schema |
|
||||
|
||||
## IG Member Implementations
|
||||
## Working Group Member Implementations
|
||||
|
||||
Work by IG facilitators and active participants that directly implements the group's core patterns: SKILL.md with YAML frontmatter, `skill://` resource URIs, and progressive disclosure via MCP primitives.
|
||||
Work by WG leads and active participants that directly implements the group's core patterns: SKILL.md with YAML frontmatter, `skill://` resource URIs, and progressive disclosure via MCP primitives.
|
||||
|
||||
| Implementation | Author | Organization | URL | Notes |
|
||||
| :--- | :--- | :--- | :--- | :--- |
|
||||
|
|
@ -21,7 +21,7 @@ Work by IG facilitators and active participants that directly implements the gro
|
|||
|
||||
## Alternative Approaches
|
||||
|
||||
Work by IG members and MCP maintainers that explores skills over MCP through different technical approaches than the core SKILL.md / `skill://` pattern.
|
||||
Work by WG members and MCP maintainers that explores skills over MCP through different technical approaches than the core SKILL.md / `skill://` pattern.
|
||||
|
||||
| Implementation | Author | Organization | URL | Notes |
|
||||
| :--- | :--- | :--- | :--- | :--- |
|
||||
|
|
|
|||
Loading…
Reference in a new issue