Meeting Notes 2015 04 14

These are the notes from the The 506th Meeting of Noisebridge. Note-taker: EMILY; Moderator: JARROD.

• This meeting covered three topics and attempted one consensus. A membership application was reviewed with the member applicant. There was a financial report and discussion of the renewal of the lease, and also a discussion of a summer camp that Emily is organizing for this summer with Noisebridge as the planned venue.

Introductions

• Jarrod
• Jay
• John
• Kevin
• Red
• Chris
• Trent
• Louis
• Torrie
• Dan
• Patrick
• David

Short announcements and events

• Torrie is sorting the electronics bins and would love some help
• The board collected 10 ballots and the results will be announced after this meeting
• Trent would like suggestions for the library
• Thurs night at 6-8 is a Maker teacher event with educators from around the Bay Area at the space
• Jarrod is working on the Maker faire booth and the build night is Thurs. Also Monday 4/20 he will be working on the LEDs and arduinos
• Sat from noon-2 is the Godwafel event
• Next Tues from 6-9 is an Android app building workshop
• Library conference is June 26
• LinuxFest Northwest is on April 25-26 in Bellingham, WA. If anyone wants to join a few members are taking the train there and hacking on the way, and they're calling it Hackers on a Train.

Membership Binder

• Louis has applied to be a member. The meeting interviews him about his application.

Louis says he loves Noisebridge and has been coming for two years. He is able to explain the consensus process. As far as projects he wants to do at Noisebridge, Louis says he wants to get to know everyone, give some talks about the projects he's working on, bridge communities with other creative spaces in San Francisco, do unofficial public relations for Noisebridge by spreading the word about the space, clean the windows, and inspire people in the space by his projects, such as how he uses techniques of system administration from big companies for his personal use. Louis has been working on research about how to improve coding for device drivers, and he is working on a project to control lightbulbs with an app. If Louis were to block a consensus, it would be about access control -- he believes the space needs to maintain access control based on the appearance of people ringing the doorbell for the safety and stability of the space and its participants. He would also try to block long discussions about why Noisebridge may want to ban certain people from the space.

Louis application for membership did not result in a consensus, and members ask him to continue to participate in the space and try again for membership later, when he has participated in more projects with other people in the space.

Financial Report

• Noisebridge has $19,000

Consensus and Discussion

• invite a knowledgeable volunteer to give a brief primer on consensus process
• It is important that everyone in attendance understands at least:
  • Blocking with verbalized principled objections.
  • Why we use consensus over other approaches to decision making.
  • How consensus isn't a legislative process
  • Why consensus isn't applicable to some things like conflict resolution, resolution of time sinks, and the like.

Proposals from last week

(Add any items which are consensed upon or someone has raised a principle objection for to the Consensus Items History page.)

Proposals for next week

(Add any new items for consensus to the Current Consensus Items page.)

Discussion Items

If any important discussion happens, it should be happening after forward progress is made during consensus.

End of Meeting

• Reprise of the Hackernationale. [This is anarchy - we do what the wiki says!]
• PGP Key Signing could happen now (if it doesn't happen before any given Meeting). Ask others around the space or check the list to see who wants in on the action.
• Return the membership binder to its rightful location.
• Clean and tidy the meeting notes including removing all these really verbose instructions, then save them to the wiki.
• Send a summary of the meeting notes to the discussion list.
• Enjoy the company of your fellow hacker, robot, or robothacker.
• Discuss any items for which there was not time during the meeting.