Current Consensus Items

From Noisebridge
Revision as of 23:21, 20 February 2014 by Flamsmark (talk | contribs) (We totally discussed this.)
Jump to: navigation, search

This is a page for hosting consensus items currently under debate, with their formal wording.

The Consensus Items History is the public record of consensus items that have been decided on in the past. Please move the records from the "Current" page to the "History" page once they've been approved/blocked.

Date First Discussed Proposed By Informal Title Summary and pull request. Author of this Record
2014-02-25 Tom House rules Pull request. Highlights:
  • We have a thing about telling people to leave.
  • Noisebridge is your hackerspace, not your home.
  • The basement, roof and fire escape are out of bounds.
2014-02-25 Tom Ban Josh Pull request. Tom
2014-02-18 N0_Hat Ban kyle, johnny, kara Ban kyle, johnny, kara from the space for reoccurring pattern of abusive behavior. N0_Hat
2014-02-18 N0_Hat Ban Robin Ban Robin from the space for reoccurring pattern of abusive behavior. N0_Hat
2014-02-18 Tom Only members can join the council. Pull Request. This also includes some clarifying re-structuring of the membership and council descriptions. Tom
2014-02-18 Tom Publish member list in our policies git repo. Github issue Tom
2014-02-11 Robin Ban Pidgeon Pidgeon is unwelcome at Noisebridge. They are prohibited from entering the space or participating in the community. Robin
2014-02-11 General Ban RAYC Pull request. Tom
2014-01-09 Dana Consensus process change 1. Consensus items at weekly meetings can be stopped from advancing by three member stand-asides or one block. Those objecting are encouraged to meet with proposal author(s) to develop mutually agreeable alternatives.

2. Membership meetings shall be scheduled and announced in advance. If a proposal cannot reach consensus or resolution at weekly meetings it may be added to a membership meeting agenda with sponsorship of three members. To take effect a proposal would require approval of 75% of members present physically or by proxy.

3. All current associate members shall be converted to full members, and the associate membership role abolished.

2013-12-10 Kevin Tabled until details are elaborated Expiration period for associate member policy Noisebridge should attach an expiration period of 90 days to the consensus decision to create new Member role. All subsequent mutations of the original consensus should be brought for a second consensus. If no consensus can be reached, Noisebridge will revert to being open to the public. Kevin