Sudo room/Governance Structure

From Sudo Room
Revision as of 17:49, 8 July 2012 by Mk30 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This is a DRAFT that requires major INPUT


Resources

Research, background investigations, early ideas can go (and come from) here:

Draft

  • Premise: A decision needs to be made. Why? Either a concern is raised, a goal is suggested, or a proposal is made.
  • Step 1: Discuss at large in the group (with a time limit, and/or feedback can be gathered online instead of taking in-person meeting time).
  • Step 2: A Senate takes this "raw material" and generates a proposal.
  • Step 3: The Senate puts the proposal to the group for amendments & voting. We can do majority vote or total consensus. If the vote is a "no", the Senate goes back and drafts another proposal.
  • End Result: A decision is made


The "Senate" Could be comprised of elected representatives (or volunteers, or super-volunteers). TBD.

Who makes up this Senate? And why them and not others? Are those not participating doing so because of disinterest and/or exclusion? Does this group of people constitute a representation of the whole body, however that is determined?

It is worth considering whether or not there should be checks and balances between the Senate and the whole body in terms of decision-making. Perhaps the people on the Senate developing an idea or proposal should be separated to some extent from the decision process, in order to avoid undue influence?

Could this be another form of sudo group? Would we convene different councils for different issues or is it always the same people, rotating out every month or year? It's important to have a way for people to organically form the groups that bring proposals at least some of the time. This allows new users with good ideas to bubble up.


Blocking

I'm seeing that the tool of "blocking" can be used in consensus voting, but some groups think of it more as a nuclear option (hence the opportunity to offer amendments and give feedback). This is something else for us to figure out.

in different existing models, a blocker is variously:

  • required to help the proposers rework the proposal
  • required to have a fundamental moral issue with the proposal or otherwise defend their block in debate or gain supporters for their position
  • required to have membership or other status
  • perhaps here, required to block in correct stage of detail?


Alternative Option 1 by Matt

Summary:

Articles of Association

(equivalent in name to a Constitution or By-Laws)

Organizational purpose
  • Sudo Room is an association of individuals established to open and collectively support a hacker space under the definition here and with values articulated here, i.e.:
    • Sudo Room is an open, non-hierarchical, collaborative community of humans, including tech developers, citizen scientists, activists, artists--and all combinations in between and beyond!--who are interested in and working towards social change. Our goal is to create the first inclusive, dedicated hackerspace in downtown Oakland, to share ideas and projects in citizen science, digital citizenship and literacy, environmental sustainability, community engagement, and self-government.
    • Sudo Room is committed to access, empowerment, transparency, and public/social good. Sudoers have a great diversity of interests and we emphasize respect and solidarity among ourselves and with others.
    • Sudo Room has the flexible agility to never wholly exclude possibilities, but instead, to give clear visions of some values over other values:
      1. Value open, public discourses over closed, proprietary processes.
      2. Value access and transparency over exclusivity.
      3. Value present concerns over hypotheticals, but respect visions of the future.
      4. Value community and interconnectivity over seclusion and territoriality.
      5. Value do-ocracy over bureaucracy
Organizational structure
Qualifications for membership
Methods for appointing leaders
Procedures
  • Internal procedural guidelines, such as frequency of meetings and authority for handling finances
Tax status

Brief Alternate Ideas for Making Decisions

Alternate Draft 1

Anyone who considers themselves a member can vote. Proposals are brought up on a given week and discussed. Additional discussions and edits take place on the wiki during the week. Following week's meeting includes discussions and final edits to the proposal (maybe cap discussions and editing per proposal at X # minutes?). Voting is open online for a week and at the following week's meeting online numbers are added to in-person numbers. This can work with unanimity, majority, etc.

Alternate Draft 2

Anyone who shows up at meetings is a voting member. Proposals are brought up on a given week and discussed. Additional discussions and edits take place on the wiki during the week with a final proposal presented at the following week's meeting. Only in-person votes that week count. This can work with unanimity, majority, etc.

Alternate Draft 3

Proposal