-
Notifications
You must be signed in to change notification settings - Fork 89
Governance
Heads-up: Our project is currently undergoing organizational changes and the information below is partially outdated!
As a young project, we feel formal governance bodies would currently add too much unnecessary, and therefore unwanted, bureaucracy. Instead, we rely on mailing list discussion and weekly chat meetings that are open to everyone. There, we hear out everyone's arguments and try to reach a consensus or at least find a vast majority for a single option.
Note, that decisions can be made on either the mailing list or a chat meeting, as the involved parties (or topic owners) see fit.
Project governance is de-facto split in two (overlapping) areas or groups:
-
Developers,
who are dealing with everything related to development. They primarily use their dedicated chat channel and mailing list to communicate with each other.
-
The Community Council,
which consists of everyone interested in fostering our community and deals with all matters that are not directly related to development. There's currently no dedicated mailing list or chat channels for the members of this group, but as they deal with the most general matters, they also use our most general communication channels.
To be clear, neither group consists of elected members. Instead, everyone can bring in their voice and cast votes.
In addition to the above mentioned communication channels, both groups use the #meetings channel for their scheduled, weekly meetings.
It has been agreed, that we adopt the Fedora Project's way to reach a decision by "lazy consensus":
Any of our decisions can be made through "lazy consensus". Under this model, an intended action is announced on the mailing list, discussed, and if there is no controversy or dissenting views with a few days, simply done.
However, thinking that "a few days" is a bit vague, we defined the necessary period to be "10 days (i.e. 240h) from the time the original email has been written".