Support for Consensus-Based Governance Models

Open
#36 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
authorization

Research direction

Start by reviewing the specification and the listed user stories for voting, quorum, delegation, and permission changes. Determine whether consensus-based governance is in scope or whether the admin-focused approach is intentional; done requires a documented decision about accommodating these models.

Written by the indexing model from the issue text.

Description

user story

I believe some groups may want to manage themselves through consensus rather than admin-only control. Some relevant user stories might include:

  • A group wants to vote on new member requests rather than having a single admin approve them
  • A group wants to rotate admin privileges among trusted members rather than having permanent admins
  • A group wants to remove an admin if a majority of members agree
  • A group wants to elect a temporary moderator for a specific event rather than assigning a permanent admin
  • A group wants to require a quorum of existing members to endorse a new applicant before they join
  • A group wants to vote on transferring group ownership rather than allowing a single admin to hand it off unilaterally
  • A group wants members to collectively moderate posts, with removal requiring agreement from multiple trusted members rather than one admin
  • A group wants to update group metadata (name, description, privacy settings) only after consensus among members
  • A group wants to distribute permission levels (who can invite, who can post, who can remove content) through member voting rather than admin assignment
  • A group wants different thresholds for different types of decisions (example: simple majority for posts, supermajority for membership changes)

Has the task force considered whether the specification should accommodate these alternative governance models, or is the admin-focused approach intentional?

Dominant language
HTML
Stars
8
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from swicg/groups

All issues in swicg/groups

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.