Designing an election mechanism
Openopened 3 months ago by fr33domlover · 4 comments
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
We don't yet have an explicit process for assigning roles to people in the project. The general decision-making process is a good basis, but it doesn't tackle all the questions and challenges related to election (e.g. who facilitates the election process; how to determine (and who determines) who's a relevant candidate for a given role, etc.)
An election process is a significant component of the project's governance, and it can be challenging (and has been challenging) to maintain trust in a globally-distributed-community all-volunteer project, especially with the high pace of governance issues and proposals being made (ironically this issue is another one).
The current roles and teams are in TEAMS.md.
Who will facilitate the decision-making process, in which an initial election process will be designed?
And who will be the people to the design the election mechanism? And how many parallel proposals shall we create as a community?
So if you'll want to participate in the proposal-writing step (when we get to that step), you can:
The process of deciding on the election mechanism will be our general decision-making process :-) (I hope that's not too confusing)
tl;dr I'm proposing to: (1) facilitate (i.e. guide/lead) the community process of designing an election mechanism (2) to co-author one of the mechanism proposals, via a Jitsi meeting anyone can join
Is the above clear? If you have any clarification question to ask, comment and ask.
If it's clear, does it make sense? Are you comfortable with what I'm proposing?
Who will design an election processto Designing an election mechanism 3 months ago
Why would we need that in a do-ocracy ?
@KaKi87, look at TEAMS.md. Can you see the value of having the teams listed there? e.g.:
Do we give anyone who asks the access to passwords, cryptographic keys for signing release, etc.? If not, who are the people we entrust to hold these sensitive resources? How do we select these people?
While we have fun coding stuff, who does the task making a monthly release? It doesn't make sense for 50 people to gather on Matrix and do it somehow together, but 3 is enough and effective, and allows us to trust that releases happen because those 3 people are on it - how do we choose them? How often do we re-elect this release team?
When we have a conflict between team members and we need help with mediation, who do we ask for help? Who in the team can mediate a conflict, who do we trust to do so without taking one side and neglecting the other? How do we choose these people together?
And so on.
Also, without roles,
@KaKi87, is this helpful in clarifying the need for roles and teams?
Is very ironic and sad that the single thumb up to your proposal in this community have been mine @fr33domlover. I really appreciate your effort to give it to Forgejo.