master
Admin 2021-05-03 08:15:39 +00:00
parent 9a904189a4
commit 5362e43fa3
1 changed files with 27 additions and 1 deletions

@ -41,4 +41,30 @@ The outcome is something much more representative of the #Fediverse than we can
The is #nothingnew in this idea or implementation, some examples from Wikipedia
![](http://hamishcampbell.com/wp-content/uploads/2021/03/organise.jpg)
![](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 its 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 “stakeholder” 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
population ~ 4.152.753 accounts
active users ~ 1.192.023people
servers > 6.828 instances
Lets 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 its up to the admin group to choice the right number to build a working community, if you dont have enough good workers open the pool up if the is to much dicushern close the pool down, 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.