Open-Media-Network
/
openwebgovernancebody
8
4
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

master
Captain_Noodles 2021-05-04 15:11:25 +00:00
parent 67d37a9fc2
commit 10c3c1ca4b
1 changed files with 13 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
Online-governance-.md

@ -38,7 +38,7 @@ On registration you are in the lottery to get working roles in the governance [S
Only people who want to be part of the governing body AND play an active role are enrolled in the lottery. The code is the management, users are just user accounts, stakeholders are mods, voices are admins.
every time a position opens the lottery picks a stakeholder to fill it if it is you and you would like to do the job – get to it. If you do not wont the job then resign and the lottery will pick a new person.
Every time a position opens the lottery picks a stakeholder to fill it, if it is you and you would like to do the job – get to it. If you do not want the job then resign and the lottery will pick a new person.
**The power of the voice**
@ -54,6 +54,7 @@ reach a core consensus they can create a group around the issue.
* Consensus of Voices (-1) makes agreements THE "voice of the Fediverse".
The actual number of voices are dynamic depending on the number of stakeholders but between 3-5 is likely a good number.
**What are the risks:**
@ -64,57 +65,37 @@ reach a core consensus they can create a group around the issue.
* Bad group of voices - are flagged by other body members. When the flagging reaches a criteria the security group can act to reach an aggreement on these flags. If the bad voices sneak through these checks, we have an exeptional case, where the body acts as an admin by flagging over a threshold by a set period.
Basic security and checks – to see if an instance still exists and is real. If a member account is actively posting or a puppet – all of this can be done with member flagging, some automated others by people – flagged accounts and posts goes to the “security group”
It’s a lottery, it’s up to the groups to influence and as a last resort “recall” if one goes a new one is chosen by lottery.
The actual number of voices are dynamic depending on the number of stakeholders but between 3-5 is likely a good number.
Basic security and checks – to see if an instance still exists and is real. If a member account is actively posting or a puppet – all of this can be done with member flagging, some automated others by people – flagged accounts and posts goes to the “security group”. It’s a lottery, it’s up to the groups to influence and as a last resort “recall” if one goes a new one is chosen by lottery.
**The work flow would be:**
Sign up for the site, then don’t untick the box for “do work” if you become a “stakeholder”
Sign up for the site, then don’t untick the box for “role” if you become a “stakeholder”
If you are not picked by the lottery for a job opening the is still a meany things you can do as a stakeholder in the groups. If you are not picked as a stakeholder you can still put ideas for the stakeholders to make into group decisions.
If you are not picked by the lottery for a role there is still many things you can do as a stakeholder in the groups. If you are not picked as a stakeholder you can still put proposals for the stakeholders to make into group decisions.
The outcome is something much more representative of the #Fediverse than we can currently think about let alone implement.
The outcome is something much more representative of the #Fediverse than we can currently think about, let alone implement.
The is #nothingnew in this idea.
There is #nothingnew in this idea.
![](http://hamishcampbell.com/wp-content/uploads/2021/03/organise.jpg)
**We now have a yearly voting/consensus (online) body made up of “stakeholders”
**
Who are the bulk stakeholders-representatives:
One voice one instance – if you run an instance you get a vote – put the URL in as long as it’s online last year your vote counts.
The is then an equal/matching number of votes based on a “user” lottery – have to opt in by adding your account name. This is refreshed every year.
Then we have other more “affiliate” stakeholders that have to be “ratified” through the body
Codebases – could be factored by installed based on instance registered above. Over a basic threshold and the body agrees.
fedivers events – any group that regularly runs events gets a “affiliate” vote based on them doing it last year. If the body agrees to this.
fedivers support organizations get a vote if the body agrees to this.
activitypub standards crew – get votes through all the rest and can have a vote as a founding fedivers org.
**The representative “stakeholder” body accepts proposals and make decisions**
Some stats
Some stats for the fediverse:
population ~ 4.152.753 accounts
active users ~ 1.192.023people
active users ~ 1.192.023 people
servers > 6.828 instances
Let’s be optimistic and say half the instances signed up that would be over 3000 instances stakeholders and thus 3000 user stakeholders for a total of 6000 and a number from affiliate groups. This number is likely too much, so we can put a limit to 100 chosen by lottery from the stakeholders instances, this is then matched by 100 from the user stakeholders for 200 stakeholders + 5-10 affiliates it’s up to the "admin group" to choice the right number to build a working community, if you don’t have enough good workers open the pool up if the is to much dicushern close the pool down, try different approaches.
Let’s say a tenth of the instances signed up, that would be over 600 Instances Stakeholders and thus 600 Users Accounts for a total of 1200 members of the body and a smaller number from Affiliate Stakeholders. For easier decision making, this number is likely too high, so we can put a limit to 100 chosen by lottery from the instances Stakeholders, this is then matched by 100 from the User accounts making a total of 200 Members of the Body + small number of affiliates. It’s up to the "admin group" to choose the right number to build a working community. If you don’t have enough good people to fill roles, open the pool up, if there is too much discussion reduce the size of the pool. Try different approaches.
A 3 way split of stakolder groups: instances/users/builders&supporters with the last group in big groups could be the size of the others so just to higlight they would be treted in exactly the same way if they are over the number of the body then they would be chosen by lottery just like the others.
A 3 way split of stakeholders: instances/users/affiliates (builders&supporters). If the affiliate group becomes larger than the number of instances, they would be be chosen by lottery just like the others.
“serving the humans trying to communicate.” we get out of the way and let the humans work it out – we provide structer for the groups, we don’t define the groups.
More info:
https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody/wiki/Looking-at-existing-projects
https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody/wiki/The-Tyranny-of-Stuctureless---tick-box-list
“serving the humans trying to communicate.” we get out of the way and let the humans work it out – we provide structer for the groups, we don’t define the groups.