Project Governance#

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.

Technical Steering Committee#

The Technical Steering Committee (TSC) is responsible for:

  1. General ambitions, objectives and goals of this project

  2. Guidelines and procedures and tool selection

  3. Architectural and (development) infrastructure choices

  4. Raise subjects/issues that are important for the direction/development of this project

The TSC currently consists of the following members:

  1. Jonas van den Bogaard

  2. Jan Maarten van Doorn

  3. Daan van Es (chair)

  4. Maxime Fortin

  5. Bart Pleiter

Any community member or Contributor can ask that something be reviewed by the TSC by contacting the TSC at openstef@lfenergy.org.

Community Manager#

The openSTEF community manager is the primary point of contact for the OpenSTEF community and focuses on strengthening and growing the ecosystem. This includes:

  • facilitating community interactions and meetings including:

    • the 4-weekly community meetings

    • quarterly co-coding sessions

  • improves communication and documentation

  • supports users and contributors of OpenSTEF

  • structuring roadmap discussions and incorporating community feedback

The current community manager is: Leander van der Bijl

Maintainers#

Maintainers are responsible for maintaining parts of the code-base. Maintainers have the following responsibilities

  1. Coordinate development activity

  2. Make sure code/documentation reviews are being done

  3. Coordinate pull-requests

  4. Coordinate bug follow-ups

  5. Coordinate questions

  6. In case of long discussions or arguments, maintainers or other can request a community council decision.

The current maintainers of this project are:

  1. Daan van Es

  2. Jan Maarten van Doorn

  3. Bart Pleiter

  4. Marnix van Lieshout

  5. Egor Dmitriev

  6. Lars Schilders

Any community member or Contributor can ask a question or raise an issue to the maintainers by logging a GitHub issue.

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.

Our gratitude goes to the following all-time top contributors:

  1. Jan Maarten van Doorn

  2. Frank Kreuwel

  3. Egor Dmitriev

  4. Bram Harmsen

  5. Enrico Schmitz

  6. David Swinkels

  7. Bart Pleiter

  8. Lars Schilders

  9. Marnix van Lieshout

  10. Martijn Cazemier

PyPI project management#

Our Python projects are published on PyPI. On PyPI we have the following roles:

  • Owner: (part of) the TSC is owner of the project

  • Maintainer: the maintainers are also maintainer of PyPI projects