1105a3af08* Update meeting notes and discussion links to main MCP repo Meeting notes are published in the main modelcontextprotocol repo discussions, not in this IG repo. Update CONTRIBUTING.md and README.md to reflect this and note that future meetings/surveys are posted in the Discord channel. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add out of scope item for plugin/bundle packaging in README * Revert "Add out of scope item for plugin/bundle packaging in README" This reverts commit 75b962ea59f0af0b29e3bd1fcb0994eb2ff0b73d. --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2.8 KiB
2.8 KiB
Contributing
How to Participate
This Interest Group welcomes contributions from anyone interested in skills distribution over MCP. You can participate by:
- Joining discussions in the #skills-over-mcp-ig Discord channel (info on joining the Discord server here)
- Opening or commenting on GitHub Discussions in the main MCP repo
- Sharing experimental findings from your own implementations
- Contributing to documentation and pattern evaluation
Communication Channels
| Channel | Purpose | Response Expectation |
|---|---|---|
| Discord #skills-over-mcp-ig | Quick questions, coordination, async discussion | Best effort |
| GitHub Discussions | Meeting notes, long-form technical proposals, experimental findings | Weekly triage |
| This repository | Living reference for approaches, findings, and decisions | Updated after meetings |
Meetings
Meeting notes are published in the main MCP repo discussions. Future meetings will be scheduled and scheduling surveys posted in the #skills-over-mcp-ig Discord channel.
Meeting norms:
- Agendas published 24 hours in advance
- Notes published within 48 hours
Decision-Making
As an Interest Group, we operate by rough consensus — we're exploring and recommending, not deciding. Outputs include:
- Documented requirements and use cases
- Evaluated approaches with findings
- Recommendations to relevant WGs or as SEP proposals
Contribution Guidelines
Documenting Approaches and Findings
When adding experimental findings or new approaches:
- Include enough detail for others to reproduce or evaluate
- Note which clients and servers were tested
- Be explicit about what worked, what didn't, and what remains untested
- Attribute community input with GitHub handles and link to the source where possible
Community Input
When adding quotes or input from community discussions:
- Attribute to the contributor by name and GitHub handle
- Link to the original source (Discord thread, GitHub comment, etc.) where possible
- Present input as blockquotes to distinguish it from editorial content
Filing Issues
Use GitHub Issues for:
- Proposing new approaches or use cases
- Reporting gaps in documentation
- Tracking action items from meetings