The basic principle is that decisions are based on consensus. If this decision-making process takes too long or a decision is required, the project committee has the authority to make a decision.
The Technical Steering Committee (TSC) is responsible for:
- General ambitions, objectives and goals of this project
- Guidelines and procedures and tool selection
- Guidelines and procedures and tool selection
- Architectural and (development) infrastructure choices
- Raise subjects/issues that are important for the direction/development of this project
The community council consists of the following members:
- Tim Weelinck - API development
- Raoul Linnenbank - Active API Development, Geo positioning, CDS ERA5, caching, remodeling, Harmonie Arome and optimisation
- Joan Ressing - Infrastructure and deployment
Tim Weelinck will chair the TSC.
Maintainers are responsible for maintaining parts of the code-base. Maintainers have the following responsibilities
- Coordinate development activity
- Make sure code/documentation reviews are being done
- Coordinate pull-requests
- Coordinate bug follow-ups
- Coordinate questions
- In case of long discussions or arguments, maintainers or other can request a community council decision.
The current maintainers of this project are:
- Raoul Linnenbank - Active API Development, debugging, repository management
- Joan Ressing - Infrastructure and deployment, back-up for Raoul Linnenbank
Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the project.
Anyone can become a contributor. There is no expectation of commitment to the project, no specific skill requirements and no selection process. To become a contributor, a community member simply has to perform one or more actions that are beneficial to the project.