|
| 1 | +--- |
| 2 | +title: People |
| 3 | +description: Contributors, governance, code of conduct, and security stance for the Cytomining community. |
| 4 | +showDate: false |
| 5 | +showAuthor: false |
| 6 | +layout: simple |
| 7 | +--- |
| 8 | + |
| 9 | +The Cytomining ecosystem is maintained by a distributed community of contributors across academia and industry. |
| 10 | + |
| 11 | +## Contributors |
| 12 | + |
| 13 | +- Browse contributors and maintainers in the [Cytomining GitHub organization](https://github.com/cytomining) |
| 14 | +- See organization members directly in the [People directory](https://github.com/orgs/cytomining/people) |
| 15 | +- Explore project-level contribution history in each repository's contributors graph |
| 16 | + |
| 17 | +We welcome issues, bug reports, documentation improvements, and pull requests from the broader community. |
| 18 | + |
| 19 | +## Governance |
| 20 | + |
| 21 | +Cytomining uses a lightweight governance model centered on maintainers and public decision-making. |
| 22 | +We keep policy concise and bias toward transparent, repository-native workflows over heavy process. |
| 23 | + |
| 24 | +- **Stewardship:** Repositories are maintained by designated maintainers in the `Cytomining` organization. |
| 25 | +- **Decision-making:** Day-to-day technical decisions happen in public issues, pull requests, and our public [Discord](https://discord.gg/dgEDz6xzfJ). |
| 26 | +- **Consensus first:** Maintainers seek rough consensus from active contributors before merging impactful changes. |
| 27 | +- **Escalation path:** When consensus is unclear, maintainers make a final call, document rationale, and revisit with new evidence. |
| 28 | +- **Scope and ownership:** Changes are reviewed by maintainers closest to the affected project area, as defined by recent commits and other relevant ecosystem initiatives. |
| 29 | +- **Openness:** Design direction, roadmap changes, and tradeoffs are discussed in public whenever possible. |
| 30 | +- **Evolution:** Governance expectations are updated incrementally as the community and project complexity grow. |
| 31 | + |
| 32 | +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. |
| 33 | + |
| 34 | +## Code of Conduct |
| 35 | + |
| 36 | +Participation in Cytomining spaces is expected to follow the organization-wide Code of Conduct: |
| 37 | + |
| 38 | +- [Cytomining Organization Code of Conduct](https://github.com/cytomining/.github/blob/main/CODE_OF_CONDUCT.md) |
| 39 | + |
| 40 | +All contributors and community members are expected to uphold a respectful, inclusive, and professional environment. |
| 41 | + |
| 42 | +## Security Stance |
| 43 | + |
| 44 | +We take security seriously across our software and community operations. |
| 45 | + |
| 46 | +- [Cytomining Organization Security Policy](https://github.com/cytomining/.github/blob/main/SECURITY.md) |
| 47 | +- If you discover a potential vulnerability, please report it responsibly through GitHub security reporting mechanisms where available |
| 48 | +- Avoid opening public issues for unpatched security vulnerabilities |
| 49 | +- We aim to triage and respond to credible reports quickly and transparently |
| 50 | + |
| 51 | +For repository-specific security guidance, check each project's `SECURITY.md` (when present) and GitHub Security tabs. |
0 commit comments