The basic principle is that decisions are based on consensus. If this decision making process takes too long or a decision is required, the Technical Steering 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, procedures and tool selection
- Architectural and (development) infrastructure choices
- Raising subjects/issues that are important for the direction/development of this project
The Technical Steering Committee consists of the following members:
- Nico Rikken, Open Source Ambassador, Alliander
- Jonas van den Bogaard, Open Source Program Office Lead, Alliander
The Open Source Ambassador will chair the TSC.
We will develop a process for appointments to the TSC with the community when the project has grown enough to need this.
Maintainers are responsible for maintaining parts of the codebase. 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 others can request a Technical Steering Committee decision.
The current maintainers of this project are:
- Nico Rikken - Open Source Ambassador, Alliander
We will develop a process for appointing additional maintainers with the community when the project has grown enough to need this.
See the list of OSPO Code Scanner contributors.
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.