Skip to content

Latest commit

 

History

History
113 lines (74 loc) · 4.76 KB

governance.md

File metadata and controls

113 lines (74 loc) · 4.76 KB

BioContextAI Governance Structure

Community

The BioContextAI community consists of anyone using, developing with, or contributing to the project in any way - including users of the Registry, developers of community MCP servers, and contributors to BioContextAI-maintained infrastructure and services. We welcome and value contributors from all backgrounds, identities, and experience levels, and are committed to fostering an inclusive environment where diverse perspectives strengthen our collective impact on biomedical research.

Contributors

Community members become contributors by:

  • Submitting MCP servers to the Registry
  • Contributing code, documentation, or bug reports to BioContextAI repositories
  • Participating in discussions on GitHub issues or community forums
  • Helping with community support, documentation or events

All contributors must adhere to the Contributor Covenant Code of Conduct. We actively encourage participation from underrepresented groups in technology and science, recognizing that diverse voices and perspectives are essential for building tools that serve the global biomedical research community.

Repeat community contributors with demonstrated interest in continued contributions may request to join the GitHub organization for enhanced collaboration privileges.

Project Structure

1. Maintainers

Role: Maintain and develop all BioContextAI infrastructure, services, and the Registry.

Responsibilities:

Registry Operations:

  • Review and approve MCP server submissions to the Registry
  • Develop schema definitions
  • Ensure submitted servers meet metadata and licensing requirements
  • Oversee the evolution of acceptance requirements
  • Document the Registry

Infrastructure & Services:

  • Develop and maintain the BioContextAI website, including the Registry web interface and BioContextAI Chat
  • Develop and maintain the BioContextAI Knowledgebase MCP implementation and related interfaces or specialized applications
  • Make technical decisions about server architecture and supported APIs
  • Maintain hosting infrastructure for remote server access

Community Support:

  • Handle Registry-related issues and community support
  • Review and approve changes to BioContextAI components
  • Community outreach and engagement

Selection: Initially appointed by project founders, expanded through nomination by existing maintainers based on continued active contribution to BioContextAI repositories.

Current Members:

  • Malte Kuehl
  • Darius Schaub
  • Malte Hellmig
  • Nico Kaiser

2. Community MCP Developers

Role: Develop independent MCP servers indexed in the Registry.

Responsibilities:

  • Maintain their own MCP server implementations
  • Ensure compliance with Registry submission requirements
  • Provide support for their tools within the community

Autonomy: Complete autonomy over their MCP server design, implementation, and maintenance, as long as they meet Registry standards and follow the Code of Conduct.

3. Advisory Committee

Role: Provide strategic guidance and conflict resolution when requested.

Responsibilities:

  • Offer strategic advice for the project when consulted
  • Resolve conflicts when escalated by maintainers or community
  • Provide domain expertise and community perspective

Selection: Initially appointed by original authors, consisting of community representatives and advanced career scientists. Members may be added, removed or replaced based on recommendation from maintainers or community feedback.

Current Members:

  • Victor G. Puelles
  • Julio Saéz Rodríguez
  • Lukas Heumos
  • Sebastian Lobentanzer

Decision Making Process

Registry and Technical Decisions

  • Routine submissions: Any Maintainer can approve
  • Technical decisions: Simple majority among Maintainers
  • Policy changes: Simple majority among Maintainers
  • Major changes: Maintainers may optionally consult Advisory Committee for guidance

Community MCP Servers

  • Individual servers: Complete developer autonomy
  • Registry inclusion: Must meet published standards, approved by Maintainers

Project-wide Decisions

  • Governance changes: 2/3 majority among Maintainers, with Advisory Committee consultation recommended
  • Code of Conduct enforcement: Maintainers handle enforcement, escalating to Advisory Committee for complex cases
  • Strategic partnerships: Maintainer decision, with Advisory Committee consultation recommended

Communication and Transparency

  • Public Discussion: GitHub issues, GitHub pull requests, community forums
  • Decision Documentation: All major decisions documented in BioContextAI repositories and websites
  • Contact Points: