This document applies to every repository of
ELIXIR On-Cloud; repositories don't
have their own GOVERNANCE.md. It describes who decides what, how decisions
are made, how the community relates to ELIXIR and GA4GH, and how
contributors take on more responsibility. It names roles, not people.
- ELIXIR On-Cloud builds and maintains open-source implementations of the GA4GH Cloud APIs, and the framework and patterns behind them.
- It is governed by the ELIXIR Compute Platform, one of the five Platforms of ELIXIR (Data, Tools, Interoperability, Compute, Training). Its work is funded through multi-year Work Packages (typically two to three years) with defined milestones and deliverables, which set the main priorities.
- ELIXIR On-Cloud (formerly known as "ELIXIR Cloud & AAI") is a Driver Project of GA4GH: it implements GA4GH standards and feeds implementation experience back into them.
- Contributors: anyone who contributes issues, discussions, reviews, documentation or code, following the code of conduct and the contributing guidelines.
- Members (team
members): contributors who are ELIXIR members. Only ELIXIR members can join teams of the organisation other thanoss-contributors. - Verified open-source contributors (team
oss-contributors): regular contributors who aren't ELIXIR members. - Maintainers: per repository, the code owners (
CODEOWNERS). They review and merge pull requests and decide technical choices in their repository, within the org policies. Every repository has at least one code owner and a backup code owner. - Leads (team
leads): set the org policies (community files, contributing rules, CI, releases, security), are responsible for releases and the response to vulnerabilities, and appoint maintainers. The maintainers of the affected repository handle individual vulnerability reports as described in the security policy; the leads oversee the response.
- Day to day: through issues and pull requests with review, by lazy consensus: a proposal goes ahead unless someone objects.
- Within a repository: its maintainers decide.
- Across repositories, on org policies and on disputes: the leads decide, after a discussion on the discussion board or in an issue.
- Org policies apply to every repository of the organisation; they are not optional.
Maintainers are contributors with sustained contributions and reviews in a repository. A maintainer or lead nominates them, and the leads appoint them. Maintainers who are inactive for a long time become emeritus; repositories that keep a list of maintainers list them as such in their documentation or README.
Propose changes by pull request to this repository, as described in the contributing guidelines.