Governance
How decisions are made
A short account of who decides what in OspreyFlow, and how that can change.
The steward
Solirius Reply created OspreyFlow, employs its project leads and looks after the project: its name, its repository, its releases and its security process. The code is released under the Apache License 2.0, which lets anyone use, change and distribute it.
Who decides what
| Decision | Who decides |
|---|---|
| What the product does next (the roadmap) | The Product Lead, after hearing from users, maintainers and the steward. |
| Architecture and design | The Chief Architect. Each decision is written down as a numbered record with its reasons. |
| Whether a change is merged | A maintainer of that area. Changes to access control need two. |
| Who becomes a maintainer | The project leads together. |
| Releases | The project leads, once every check has passed. |
Principles the project holds to
- Decisions are recorded, with their reasons, where everyone can read them.
- The same checks apply to everyone's changes, the project leads' included.
- A disagreement is settled by the person who answers for that area, and the decision is written down.
- The open-source product is the whole product. Solirius Reply sells services around it, not a separate edition.
Changing this
This page describes how the project runs today, with a small founding team. As contributors join, it will change, and changes will be proposed in the open. A governance file and a list of maintainers are not yet in the repository.
Want help to run it? Solirius Reply offers pilots, builds and support: ospreyflow.net.