OME Governance Charter

1. Purpose and Scope

The Open Microscopy Environment (OME) develops and maintains open-source software, specifications, and community infrastructure that support interoperable biological imaging workflows and data management. OME provides shared technologies, standards, and coordination mechanisms intended to support sustainable and reusable scientific infrastructure across the bioimaging ecosystem.

This charter defines a lightweight governance framework intended to support the long-term sustainability, continuity, transparency, and scalability of OME. The framework defines responsibilities, decision-making pathways, and coordination structures that enable contributors and projects to operate effectively within a shared ecosystem.

OME governance is intended to support operational continuity, responsible stewardship, and constructive collaboration. Authority and responsibility are delegated to individuals and groups with demonstrated and sustained operational involvement in the work of the community. Governance exists to support contribution, maintain continuity, and ensure that critical infrastructure and standards remain stable, accessible, and community-driven.

This framework is intended to evolve incrementally over time as projects, responsibilities, and community needs change.

2. Guiding Principles

OME governance is guided by the following principles:

• Governance should remain lightweight and operationally focused, minimising unnecessary bureaucracy while preserving accountability and continuity.
• Responsibility follows sustained contribution and active engagement.
• Decision-making should be transparent and documented whenever practical.
• Authority should be delegated to the groups closest to the relevant technical or organizational work.
• OME should remain open to new contributors, projects, and collaborations. Growth should strengthen rather than dilute the integrity, sustainability, and shared identity of the OME ecosystem.
• Processes and structures should evolve incrementally in response to operational experience and community needs.

3. Governance Structure

OME governance is organized as a layered structure that separates ecosystem-level coordination from project-level operational governance.

3.1 OME Participation Agreement

The Agreement defines the shared expectations and participation framework across the OME ecosystem. It establishes baseline principles for collaboration, contribution, stewardship, and community participation across all governance bodies and registered projects. Decision-makers in all governance structures are required to publicly acknowledge the agreement before contributing.

3.2 OME Management Group (OMG)

The OME Management Group (OMG) is responsible for the strategic coordination, continuity, and operational oversight of the OME ecosystem as a whole. This includes facilitating funding, partnership, and strategic opportunities, encouraging OME projects to present a coherent voice where appropriate, and fostering a culture of mutual support and collaboration among OME projects for the benefit of the whole project.

Further, the OMG:

• Maintains the overall governance framework.
• Oversees the recognition and review of OME Registered Projects.
• Coordinates responsibilities not delegated to specific projects.
• Provides escalation and conflict-resolution pathways where necessary.
• Supports continuity of shared infrastructure, standards, and community processes.
• Maintains ecosystem-level governance records and rosters.

The OMG delegates operational authority wherever practical and is not intended to centralize all technical or project-level decision-making within OME.

3.3 OME Registered Projects (ORPs)

OME Registered Projects (ORPs) are recognized projects operating within the OME ecosystem. ORPs are responsible for advancing clearly defined technical, organizational, or community goals aligned with the mission of OME.

Each ORP:

• Maintains a defined scope and governance structure, which may define additional internal governance layers where appropriate.
• Operates day-to-day according to its own charter and processes.
• Provides clear onboarding and participation pathways for contributors.
• Coordinates with the OMG on high-level governance changes and ecosystem-wide concerns.
• Maintains public governance and participation information wherever practical.

ORPs may manage multiple code repositories, specifications, services, datasets, websites, or related resources. These resources are not required to reside within a single organization or infrastructure platform.

The OMG may approve new ORPs based on demonstrated activity, sustainability, governance readiness, and relevance to the broader OME mission.

4. Operational Coordination

The OMG coordinates the operation of the OME ecosystem through regular communication with OME Registered Projects and other governance bodies.

This coordination includes:

• Maintaining shared governance documents and public rosters.
• Tracking delegated responsibilities across projects and governance bodies.
• Providing escalation pathways where cross-project coordination or conflict resolution is required.
• Supporting continuity of critical infrastructure, standards, code repositories, services, and community resources.
• Encouraging collaboration and information sharing between ORPs.
• Coordinating ecosystem-wide meetings, announcements, and governance updates.

Governance authority is delegated together with responsibility for timely execution, public communication, and operational continuity.

OME governance bodies are expected to operate transparently wherever practical. Governance decisions, membership changes, major procedural updates, and significant structural changes should be documented publicly.

ORPs are expected to maintain:

• Public communication channels.
• Clear onboarding pathways for contributors.
• Publicly accessible governance documentation.
• Timely responsiveness to community questions and coordination requests.

The OMG may periodically review governance structures, delegated responsibilities, and project activity to ensure that responsibilities remain sustainable and appropriately maintained.

5. Governance Documents

OME governance is described through a set of related documents that define responsibilities, membership, authority, and operational procedures at different levels of the ecosystem.

These documents include:

• Governance Charter (this document)
• Participation Agreement
• Management Group Roster
• Project Roster

OME governance is organized as a layered structure:

• The Participation Agreement defines ecosystem-wide participation expectations.
• The OMG Charter and OMG Roster define ecosystem-level coordination and oversight.
• The Project Roster defines recognized OME Registered Projects.
• ORP Charters and Rosters define the governance and participation structures of individual projects.
• Project-specific governance documents, e.g. Policies, may define additional operational or technical governance where necessary.

This layered approach allows ecosystem-level governance structures to remain stable while enabling projects and operational groups to evolve their procedures independently as needed.

6. Decision-Making

OME governance bodies should prioritize consensus-based decision-making wherever practical. When consensus cannot be reached within a reasonable timeframe, formal voting mechanisms may be used.

Each governance body shall define:

• Quorum requirements
• Voting procedures
• Escalation pathways
• Membership expectations
• Documentation practices

Operational decisions should be made by the most appropriate delegated group whenever possible. Escalation to higher governance levels should occur only when necessary to resolve conflicts, procedural failures, or questions of ecosystem-wide impact.

Governance bodies are expected to make decisions within reasonable timeframes and avoid unnecessary procedural blocking.

7. Participation and Membership

Participation within OME is open to contributors who engage constructively with the community and its projects.

Governance responsibilities are earned through sustained and substantive contribution, operational involvement, and demonstrated commitment to the long-term health of the ecosystem.

OME governance is intended to support active contributors rather than function as a broad representative structure. Contributors are encouraged to participate through projects, working groups, specifications, software maintenance, documentation, outreach, infrastructure support, and related activities.

Projects and governance bodies should maintain clear and accessible pathways for contributors to increase their responsibilities over time.

8. Creation and Evolution of ORPs

The OMG may recognize new OME Registered Projects based on:

• A clear and relevant mission
• Demonstrated activity and sustainability
• Defined governance structures
• Active contributors or maintainers
• Alignment with OME objectives and values

ORPs are expected to maintain public documentation describing:

• Their scope
• Governance structure
• Membership
• Communication channels
• Participation pathways

The OMG may periodically review ORPs to ensure continued activity, sustainability, and alignment with the broader OME ecosystem.

The OMG may also restructure, merge, sunset, or reassign responsibilities between ORPs where necessary to maintain operational continuity and ecosystem sustainability.

9. Community Coordination

OME maintains a set of shared coordination mechanisms intended to support communication and collaboration across projects and governance bodies.

These may include:

• Recurring community meetings
• Annual or periodic community events
• Shared communication channels
• Public governance discussions
• Shared infrastructure and services
• Cross-project technical coordination activities

Representatives of governance bodies and ORPs are encouraged to participate regularly in ecosystem-wide coordination activities.

10. Transparency and Records

OME governance documents, project rosters, charters, policies, and major governance decisions should be publicly accessible wherever practical.

Governance bodies are encouraged to:

• Publish meeting summaries or decision logs.
• Maintain up-to-date membership rosters.
• Clearly document delegated responsibilities and escalation pathways.
• Record significant governance changes publicly.
• Maintain publicly accessible governance and participation documentation.

Transparency is intended to support continuity, accountability, operational clarity, and community participation without introducing unnecessary procedural overhead.

11. Amendments and Evolution

This governance framework is expected to evolve over time in response to operational experience and community growth.

The OMG is responsible for maintaining and updating this charter. Subordinate governance documents, including ORP Charters and operational policy documents, may define additional procedures consistent with this framework.

Changes to ecosystem-level governance structures should be documented publicly and reviewed through transparent community processes wherever practical.

The OMG may delegate responsibility for maintaining subordinate governance documents to ORPs or other governance bodies where appropriate.