OME Bio-Formats — Roster

1. Overview

The OME Bio-Formats is a recognized part of the OME ecosystem, responsible for reading and writing a variety of image file formats.

This document records the current roster of individuals contributing to and maintaining the project, along with their roles and responsibilities.

Participation in this roster reflects sustained and substantial contributions aligned with the goals of the project and the broader OME mission.

2. Scope of the Project

• Primary focus: Bio-Formats is primarily a library to read and write images and metadata in open and proprietary scientific image file formats.
• Key responsibilities:
  • Providing functionality reading images and metadata from many image file formats, based on the OME model
  • Providing functionality to write images and metadata to select open image file formats, including but not limited to OME-TIFF
  • Where appropriate, maintaining plugins, examples, and/or documentation to allow Bio-Formats to be used within other open source software packages.
• Out of scope (if needed):
  • Image processing or analysis
  • Image visualization, other than a simple command-line viewer and plugins to facilitate using Bio-Formats in existing visualization tools
  • Writing data to proprietary file formats
  • Reading data from non-scientific file formats
  • Reading data that is not, or cannot be represented as, an image

3. Roles and Responsibilities

Roles within the project are aligned with the GitHub permissions model and reflect increasing levels of responsibility and trust. Assignment of roles is based on sustained and substantial contributions, as well as demonstrated reliability in supporting the project.

3.1 Steward (triage rights)

Individuals with the Triage role support the organization and flow of contributions by:

• Reviewing and labeling issues and pull requests
• Helping prioritize work and identify duplicates
• Assisting contributors with initial feedback and guidance

This role is often an entry point for deeper involvement in project maintenance.

Current Triage Members:

• (none currently)

  3.2 Core Dev (commit rights)

Individuals with Write access actively contribute to the codebase and project materials by:

• Submitting and updating pull requests
• Contributing code, documentation, or specifications
• Collaborating with maintainers on implementation details

This role reflects consistent contribution and familiarity with project practices.

Current Write Members:

• (none currently)

  3.3 Maintainer

Individuals with the Maintain role are responsible for the ongoing development and direction of the project. This includes:

• Reviewing and merging pull requests
• Guiding technical direction and roadmap
• Ensuring alignment with OME standards and practices
• Facilitating discussions and decision-making

This role corresponds to a maintainer-level responsibility, requiring sustained engagement and stewardship of the project.

Current Maintainers:

• Sébastien Besson (Glencoe Software)

• Melissa Linkert (Glencoe Software)

  3.4 Admin

Administrative authority should reflect responsibility for the long-term success and sustainability of the project. Individuals with Admin access provide structural and operational support for the repository and project. This includes:

• Managing repository settings, permissions, and integrations
• Supporting release processes and infrastructure
• Ensuring continuity and stability of project operations

Admin responsibilities are assigned sparingly and typically overlap with experienced maintainers or members coordinating across the broader OME ecosystem. While many Administrators emerge through sustained technical contribution, projects may also appoint individuals whose responsibilities primarily relate to leadership, stewardship, funding, operations, community coordination, or institutional commitments. The criteria for such appointments should be documented by the project and reflected in its roster.

Current Admins:

• Sébastien Besson (Glencoe Software)
• Jean-Marie Burel (University of Dundee)
• Melissa Linkert (Glencoe Software)
• Josh Moore (German BioImaging/Image Coop)

4. Membership Expectations

Membership in the roles outlined above is open to individuals who wish to contribute. Becoming part of the roster (e.g. Contributor or Maintainer) is based on:

• Sustained and meaningful contributions
• Alignment with project goals
• Demonstrated reliability and collaboration

These roles within the project, however, are not fixed and may evolve over time:

• Contributors may become Maintainers through sustained engagement
• Maintainers are expected to remain active and responsive

To ensure continued progress:

• Individuals who become inactive may be moved to an inactive or alumni status
• Responsibilities may be reassigned as needed to maintain momentum

5. Decision-Making

Decisions within the project are made through:

• Open discussion and consensus where possible
• Voting or escalation when necessary, following OME governance practices

Maintainers are responsible for ensuring that decisions are made in a timely and transparent manner.

6. Relationship to OME Governance

The OME Bio-Formats operates as an OME Recognized Project (ORP) and aligns with the broader governance framework.

• The project contributes to and is supported by the OME ecosystem
• Coordination with the OMG occurs as needed
• The project follows shared principles for openness, contribution, and sustainability

7. Maintenance of This Document

This roster is maintained by the project Maintainers and updated as needed to reflect:

• Changes in participation
• Role transitions
• Project evolution