↓Skip to main content

People

The Cytomining ecosystem is maintained by a distributed community of contributors across academia and industry.

Contributors #

We welcome issues, bug reports, documentation improvements, and pull requests from the broader community.

Governance #

Cytomining uses a lightweight governance model centered on maintainers and public decision-making. We keep policy concise and bias toward transparent, repository-native workflows over heavy process.

  • Stewardship: Repositories are maintained by designated maintainers in the Cytomining organization.
  • Decision-making: Day-to-day technical decisions happen in public issues, pull requests, and our public Discord.
  • Consensus first: Maintainers seek rough consensus from active contributors before merging impactful changes.
  • Escalation path: When consensus is unclear, maintainers make a final call, document rationale, and revisit with new evidence.
  • Scope and ownership: Changes are reviewed by maintainers closest to the affected project area, as defined by recent commits and other relevant ecosystem initiatives.
  • Openness: Design direction, roadmap changes, and tradeoffs are discussed in public whenever possible.
  • Evolution: Governance expectations are updated incrementally as the community and project complexity grow.

This reflects how the organization operates today and is intentionally compact so contributors can understand how decisions get made without navigating a large policy surface.

Code of Conduct #

Participation in Cytomining spaces is expected to follow the organization-wide Code of Conduct:

All contributors and community members are expected to uphold a respectful, inclusive, and professional environment.

Security Stance #

We take security seriously across our software and community operations.

  • Cytomining Organization Security Policy
  • If you discover a potential vulnerability, please report it responsibly through GitHub security reporting mechanisms where available
  • Avoid opening public issues for unpatched security vulnerabilities
  • We aim to triage and respond to credible reports quickly and transparently

For repository-specific security guidance, check each project’s SECURITY.md (when present) and GitHub Security tabs.