mirror of https://github.com/deuxfleurs-org/garage.git synced 2026-07-26 07:58:14 +00:00

Files

T

Antonin Delpeuch a1f9c52563 docs: add GOVERNANCE.md (#1493 )

Documenting the structure of a team can be helpful to integrate newcomers, avoid some conflicts and to accompany the evolution of that structure as a FOSS project grows.

This is an attempt to do that for garage, after discussions with multiple maintainers. The aim of this text is to document the status quo, offering a start for further incremental updates.
I propose to put it as `GOVERNANCE.md` file because this naming has emerged as a sort of standard in FOSS projects.

I would be happy to help facilitate such updates if there is interest (while being aware that project members have other things on their plates and that governance work can be taxing).

Reviewed-on: https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/1493

2026-07-20 18:10:30 +00:00

2.2 KiB

Raw Permalink Blame History

Governance of Gararge

This documents how the Garage project operates. It reflects the state of the project as of July 2026 and is not optimal. The team is interested to improve it in the future.

Team organization

Contributors: anyone can contribute by proposing changes in issues and pull requests.
Maintainers: they are responsible for reviewing, merging pull requests, publishing releases and triaging issues. The current maintainers are:
- Alex (handle lx)
- Trinity (handle trinity-1686a)
- Quentin (handle quentin)
- Maximilien (handle halfa), who is in particular responsible for coordinating effort on the Kubernetes integration / Helm chart.
They are added to a white-list of the branch protection rule of the repository to enable them to merge pull requests. To become a maintainer, you need to be a long-term contributor and earn the personal trust of Alex. There is no set process for leaving the maintainer role.
Lead developer: Alex (handle lx) is the lead developer and is responsible of ensuring the correctness of Garage and stability between version upgrades. He may transfer this role to someone else as he sees fit.

Communication channels

The team coordinates in the following channels:

The issue tracker and pull requests of the official repository.
The #garage:deuxfleurs.fr matrix channel (in English), open to anyone. On this channel, users may ask for support and discussions about development also happen.
The #garage-dev:deuxfleurs.fr matrix channel (in French), not advertised to contributors but de facto accessible to anyone. Discussions about development and project coordination happen there.

The moderators for those discussion channels are the Garage maintainers.

Decision procedures

Decisions are taken by lazy consensus, with the lead developer settling discussions when a consensus cannot be reached.

Governance changes

There is no set process for changing the governance of garage.

2.2 KiB Raw Permalink Blame History