Add FSIG repository structure (#1)
- Add README with mission, meeting info, and quick start guide - Add CHARTER with scope and extension promotion strategy - Add GOVERNANCE with decision-making model, roles, and members - Add CONTRIBUTING guide referencing MCP standards - Add CODEOWNERS for @modelcontextprotocol/ig-financial-services
This commit is contained in:
parent
6b226de731
commit
6b0dd7f13a
1 changed files with 450 additions and 0 deletions
157
GOVERNANCE.md
Normal file
157
GOVERNANCE.md
Normal file
|
|
@ -0,0 +1,157 @@
|
|||
# FSIG Governance & Members
|
||||
|
||||
This document describes the governance model, roles, and current members of the MCP Financial Services Interest Group (FSIG).
|
||||
|
||||
## Governance Model
|
||||
|
||||
FSIG operates with a **lightweight, consensus-driven governance model**:
|
||||
|
||||
- **Decision-making:** Consensus among maintainers
|
||||
- **Maintainer responsibilities:** Coordinate meetings, maintain repo hygiene, facilitate collaboration, review/merge PRs, make governance decisions
|
||||
- **Transparency:** All decisions documented in meeting notes or GitHub issues
|
||||
- **Open participation:** Anyone can contribute, attend meetings, and provide input
|
||||
|
||||
### Decision-Making Process
|
||||
|
||||
1. **Proposals** are raised via GitHub Issues or during meetings
|
||||
2. **Discussion** happens in public channels (Discord, GitHub, meetings)
|
||||
3. **Consensus** is reached when no maintainer objects (lazy consensus)
|
||||
4. **Objections** trigger further discussion to find compromise or alternative approaches
|
||||
5. **Documentation** of decisions happens in meeting notes or issue threads
|
||||
|
||||
For technical decisions, maintainers may defer to subject matter experts or request broader community input.
|
||||
|
||||
### Core Principles
|
||||
|
||||
1. **Open participation** — Anyone can contribute regardless of affiliation or background
|
||||
2. **Transparent decisions** — All work happens in public with documented rationale
|
||||
3. **Consensus-driven** — Decisions made by maintainer consensus with community input
|
||||
4. **[Antitrust compliance](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)** — Stay within technical scope and avoid competitive coordination
|
||||
5. **Community-aligned** — Collaborate with other MCP groups and align with broader ecosystem goals
|
||||
|
||||
## Roles & Responsibilities
|
||||
|
||||
### Maintainers
|
||||
|
||||
Maintainers are trusted members who steward the FSIG's direction and operations.
|
||||
|
||||
**Responsibilities:**
|
||||
- Review and merge pull requests
|
||||
- Coordinate meetings and set agendas
|
||||
- Maintain repository hygiene and organization
|
||||
- Make governance decisions via consensus
|
||||
- Enforce scope and conduct standards
|
||||
- Mentor and support contributors
|
||||
- Represent FSIG in broader MCP community
|
||||
|
||||
**Privileges:**
|
||||
- Write access to the repository
|
||||
- Voting rights on group decisions
|
||||
- Ability to approve new maintainers
|
||||
|
||||
**Becoming a Maintainer:**
|
||||
1. Demonstrate sustained contribution to the group (code, documentation, or leadership)
|
||||
2. Nomination by an existing maintainer
|
||||
3. Consensus approval from current maintainers
|
||||
4. Repository access and onboarding to governance processes
|
||||
|
||||
### Active Contributors
|
||||
|
||||
Active Contributors are community members who regularly participate in FSIG activities.
|
||||
|
||||
**Characteristics:**
|
||||
- Regularly participate in meetings or discussions
|
||||
- Contribute to the codebase, documentation, or proposals
|
||||
- Provide domain expertise and feedback
|
||||
|
||||
**Privileges:**
|
||||
- Triage permissions to the repository
|
||||
- Recognition in this document
|
||||
- Voice in technical discussions
|
||||
|
||||
**Becoming an Active Contributor:**
|
||||
- Simply start contributing! No formal approval needed
|
||||
- Maintainers may grant triage permissions after sustained participation
|
||||
- Self-nominate or be nominated by others for recognition
|
||||
|
||||
### Contributors
|
||||
|
||||
Anyone can contribute to FSIG by:
|
||||
- Joining discussions in Discord or GitHub
|
||||
- Attending meetings and providing feedback
|
||||
- Opening issues for new ideas or problems
|
||||
- Submitting pull requests
|
||||
- Reviewing proposals and providing expertise
|
||||
|
||||
No approval or membership is required to contribute.
|
||||
|
||||
## Current Members
|
||||
|
||||
### Maintainers
|
||||
|
||||
Maintainers have review/merge permissions on the repository and voting rights on group decisions.
|
||||
|
||||
| Name | Organization | GitHub |
|
||||
|------|-------------|---------|
|
||||
| Sambhav Kothari | Bloomberg | [@sambhav](https://github.com/sambhav) |
|
||||
|
||||
### Active Contributors
|
||||
|
||||
Contributors who regularly participate in meetings, discussions, or contribute to the codebase:
|
||||
|
||||
| Name | Organization | GitHub |
|
||||
|------|-------------|---------|
|
||||
| Xin Fu | Bloomberg | [@imfing](https://github.com/imfing) |
|
||||
| Kengo Arao | Bloomberg | [@KengoA](https://github.com/KengoA) |
|
||||
|
||||
_To add yourself to this list, open a PR after attending at least 2 meetings or making substantive contributions._
|
||||
|
||||
### Emeritus Maintainers
|
||||
|
||||
Former maintainers who have stepped down but made significant contributions:
|
||||
|
||||
_None yet._
|
||||
|
||||
## Meetings
|
||||
|
||||
All FSIG meetings must include:
|
||||
|
||||
1. **Antitrust Reminder** — Brief reminder at the start that we must comply with the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)
|
||||
2. **Published Agenda** — Posted at least 48 hours prior in Discord
|
||||
3. **Public Notes** — Meeting notes with decisions and action items published after each meeting
|
||||
4. **Open Attendance** — All interested participants welcome, no approval required
|
||||
|
||||
Meeting notes are maintained in a [shared Google Doc](https://docs.google.com/document/d/18lj9jcdNnr4m9d1RovotEko5LTP_9vsRTuZdfg0Igmw/edit?tab=t.0).
|
||||
|
||||
## Antitrust Compliance
|
||||
|
||||
The FSIG strictly adheres to the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md).
|
||||
|
||||
**Prohibited Topics:**
|
||||
- Pricing strategies, costs, or margins
|
||||
- Customer lists or market segmentation
|
||||
- Competitive strategies or market division
|
||||
- Confidential business information
|
||||
- Any coordination that could be construed as anti-competitive
|
||||
|
||||
**Enforcement:**
|
||||
- Maintainers are responsible for keeping discussions on track
|
||||
- Participants who repeatedly violate the policy may be excluded from meetings
|
||||
- Any concerns should be raised immediately with maintainers
|
||||
|
||||
## Amendments
|
||||
|
||||
This governance document may be amended by:
|
||||
1. Proposal via GitHub Issue or pull request
|
||||
2. Discussion in meetings and/or GitHub
|
||||
3. Consensus approval from maintainers
|
||||
4. Documentation of rationale in the PR or issue
|
||||
|
||||
Significant changes should be announced in Discord and allow for community input before finalization.
|
||||
|
||||
## Questions?
|
||||
|
||||
For questions about FSIG governance, please:
|
||||
- Ask in the `#financial-services-ig` Discord channel
|
||||
- Open a GitHub Issue
|
||||
- Contact the maintainers listed above
|
||||
Loading…
Reference in a new issue