Governance: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
}} | }} | ||
Up to [[Part Of::Mastodon]] | Up to [[Part Of::Mastodon]] | ||
Neuromatch.social is a cooperatively governed instance that is operated with shared control over financial, labor, and structural decisions. Membership is not passive - members that make use of the instance are expected to make contributions to running the instance according to their ability and the need of the instance. | Neuromatch.social is a cooperatively governed instance that is operated with shared control over financial, labor, and structural decisions. Membership is not passive - members that make use of the instance are expected to make contributions to running the instance according to their ability and the need of the instance. | ||
| Line 16: | Line 12: | ||
== Overview == | == Overview == | ||
Most of the everyday work of the instance is done by [[Mastodon/Working Groups|working groups]], but their structure and the rest of the operations of the instance are decided by the membership. Changes to the instance are made with [[#Proposals]] | * Most of the everyday work of the instance is done by [[Mastodon/Working Groups|working groups]], but their structure and the rest of the operations of the instance are decided by the membership. | ||
* Changes to the instance are made with [[#Proposals]], which can be made by any member or working group | |||
* Proposals are typically preceded with [[#Discussions]], where a member consults a relevant working group or refines their language before proposing | |||
* Proposals follow some expected pattern of consensusmaking with a specific duration and threshold for consensus, depending on what type of proposal it is (see [[#Administrative Objects]]). | |||
== Administrative Objects == | == Administrative Objects == | ||
| Line 28: | Line 23: | ||
See [[:Category:Administrative_Object]] | See [[:Category:Administrative_Object]] | ||
The instance | The instance is governed by several different types of [[Administrative Objects]], each of which is operationalized as a wiki page with a particular [[Special:Categories|category]], which in turn has a [[mediawikiwiki:Extension:PageSchemas|page schema]]<ref>ie. a [[Special:Templates|template]] that sets [[Special:Properties|properties]] and a [[Special:Forms|form]] for interacting with it</ref>. | ||
=== [[Mastodon/Bylaws|Bylaws]] === | === [[Mastodon/Bylaws|Bylaws]] === | ||
| Line 40: | Line 35: | ||
|transpose=yes | |transpose=yes | ||
}} | }} | ||
The bylaws determine the basic structure of the instance: what its purpose is, how it is to be run, and what its relationship is with its parent, [[Neuromatch]]. Bylaws require a higher vote threshold (or, fewer blocks are allowed) in order to change, since changes could dramatically change the instance. As a result they should be written generally enough to not micromanage the unpredictable policies that are needed to enact them. | |||
=== Policies === | === Policies === | ||
| Line 51: | Line 48: | ||
|transpose=yes | |transpose=yes | ||
}} | }} | ||
Policies operationalize the bylaws, and set core rules for how the instance is to be run. Policies should be consistent with bylaws. Members of the instance are expected to contribute to, know, and follow the policies. Each member is able to modify and create policies, so if they are missing or don't fit the needs of the membership, they should be changed :). | |||
=== Norms === | === Norms === | ||
| Line 62: | Line 61: | ||
|transpose=yes | |transpose=yes | ||
}} | }} | ||
Norms are useful for suggesting the "vibe" of the instance and supporting new members understand how things work. Norms offer suggested ways to do things, how members typically expect things to happen, and so depending on the content of the norm members might be encouraged, but are not required to abide by norms. Since each norm could have potentially multiple conflicting viewpoints, it is possible to approve multiple versions and amendments to norms without necessarily needing to make them consistent with previous norms. | |||
== Actions == | == Actions == | ||
| Line 67: | Line 68: | ||
''What kind of things can be done by a member of neuromatch.social'' | ''What kind of things can be done by a member of neuromatch.social'' | ||
Any member can | Any member can make a '''proposal''' for the instance to take some action or change some structure. | ||
=== Discussions === | === Discussions === | ||
Revision as of 01:48, 9 December 2022
| Governance | |
|---|---|
| Part Of | Mastodon, Mastodon/Bootstrapping |
| Contributors | Jonny Saunders
|
| Completion Status | In Progress |
| Active Status | Active |
| Approval Status | Provisional |
Up to Mastodon
Neuromatch.social is a cooperatively governed instance that is operated with shared control over financial, labor, and structural decisions. Membership is not passive - members that make use of the instance are expected to make contributions to running the instance according to their ability and the need of the instance.
Overview
- Most of the everyday work of the instance is done by working groups, but their structure and the rest of the operations of the instance are decided by the membership.
- Changes to the instance are made with #Proposals, which can be made by any member or working group
- Proposals are typically preceded with #Discussions, where a member consults a relevant working group or refines their language before proposing
- Proposals follow some expected pattern of consensusmaking with a specific duration and threshold for consensus, depending on what type of proposal it is (see #Administrative Objects).
Administrative Objects
What kinds of things exist in the governance system of neuromatch.social
See Category:Administrative_Object
The instance is governed by several different types of Administrative Objects, each of which is operationalized as a wiki page with a particular category, which in turn has a page schema[1].
Bylaws
| Bylaw | |
| Description | A basic operating principle of neuromatch.social. Should be general enough to allow refinement by policies. |
| Voting Period | 14 Days2 Weeks <br /> |
| Block Threshold | 0.1 |
The bylaws determine the basic structure of the instance: what its purpose is, how it is to be run, and what its relationship is with its parent, Neuromatch. Bylaws require a higher vote threshold (or, fewer blocks are allowed) in order to change, since changes could dramatically change the instance. As a result they should be written generally enough to not micromanage the unpredictable policies that are needed to enact them.
Policies
| Policy | |
| Description | A collective decision that structures the operation of neuromatch.social. Must be consistent with any existing bylaws. |
| Voting Period | 7 Days1 Weeks <br /> |
| Block Threshold | 0.2 |
Policies operationalize the bylaws, and set core rules for how the instance is to be run. Policies should be consistent with bylaws. Members of the instance are expected to contribute to, know, and follow the policies. Each member is able to modify and create policies, so if they are missing or don't fit the needs of the membership, they should be changed :).
Norms
| Norm | |
| Description | Nonbinding statements about the way that things are usually done, or suggested behavior on neuromatch.social. Sometimes norms can be akin to guides. Norms are intended to be fluid and reflect the current practices of the membership. Norms are not intended to be logically complete or settled, and can contain multiple conflicting perspectives or variants. |
| Voting Period | 3 Days0.429 Weeks <br /> |
| Block Threshold | 0.5 |
Norms are useful for suggesting the "vibe" of the instance and supporting new members understand how things work. Norms offer suggested ways to do things, how members typically expect things to happen, and so depending on the content of the norm members might be encouraged, but are not required to abide by norms. Since each norm could have potentially multiple conflicting viewpoints, it is possible to approve multiple versions and amendments to norms without necessarily needing to make them consistent with previous norms.
Actions
What kind of things can be done by a member of neuromatch.social
Any member can make a proposal for the instance to take some action or change some structure.
Discussions
discussion structure
Proposals
proposal structure
Working Groups
Bounded Discretion
Voting
See also: Consensus
Neuromatch.social decisions are made with a modified form of consensus for large asynchronous groups.
Voting in a Consensus system is not like voting in a majoritarian system: rather than voting for the thing that would be best for you, you are voting for
elaborate...
consensus thresholds....
See also
- ↑ ie. a template that sets properties and a form for interacting with it