Meeting Notes 2017 07 11

From Noisebridge
Jump to navigation Jump to search

These are the notes from the The XXXth Meeting of Noisebridge. Date: 2017-07-11 Note-taker: Matthew; Moderators: Jarrod

Meeting Summary[edit]


  • Announcements: 10 year anniversary celebration in September
  • Finances: $79,430.79 in the bank. See below.
  • New members: Lee
  • New philanthropists: none
  • Consensus Items: none
  • Discussion Items: the 10 year anniversary logo was discussed


Noisebridge is a 501c3 nonprofit that provides a space for creation, collaboration, and learning about technology and creative projects. Noisebridge provides space, power tools, and infrastructure to help the public learn new skills and create cool things. Noisebridge continues to exist through and depends entirely on membership fees and donations. Our code of conduct is 'Be excellent to each other'."

  • Introduce any experimental or unusual moderation techniques that may be using during the meeting like: direct responses, limited speaking time, orderless stack, &c.
  • Round of introductions (remember, announcements come later):
    • What's your name
    • What do you do
    • What do you maintain at Noisebridge?
    • if you are new: how did you hear about Noisebridge?

- Jared: likes woodworking, tools - Sylium: wants to work on a cat feeder - Nick: electronics - Sophia: can help with android projects, exploring sewing - Maya: physical security, picking locks - Carly: wants to pick locks - Frank: interested in high speed data communications - Weston: power electronics, software security - Asya: RF trackers - Darrell: AI, functional programming, laser cutter - Claudia: came back after a while gone, brought people from Indivisible - SMP: sewing, - Michael: interface designer, C#, JS, 3D printing - Jeremy: organized NN event, laser cutter, network engineer - Manny: here for gamebridge, open to help people design characters - Nick: interested in everything - Trent: teaches Python class on Mondays, web developer - Kayta: iOS dev, has a meetup on Sundays for iOS stuff, interested in functional programming - Lee: works in information security, human rights, censorship intervention - Matt: interested in 3D printing, the library front end , - Matthew - moved here a few weeks ago. working at a software engineering company, interested in security/privacy tech and blockchain tech - Aleks - Danny

Short announcements and events[edit]

  • Cool new projects? Something you'd like people to know? Say now, but keep it short! One or two sentences please!
  • Any happenings at the space of which members should be made aware.
  • Don't hog everyone's time since we all just want to hack!

- Nick is asking for help taking stuff from storage. If anyone has a van let him know - Noisebridge 10 year anniversary Sept. 9th and 10th. Lots of stuff going on: a ball on the 9th, some workshops and celebrations. If you have projcets to show off, let Jared know There's also a wiki page for the event. There's also a planning meeting on Thursday at 8. And karaoke at some point - Lizzie says SF DSA is having a book club meeting on Monday the 17th at 6:30

Safe Space[edit]

Note: This section is experimental. We discussed it at Meeting_Notes_2016_06_28. We're going to try it for the next meeting, and see how it goes, and then discuss in the discussion section how it went, and how we'd like to tweak it.

Noisebridge is a safe space. Invite a volunteer to describe what that means.

Some specific points you might prompt the group to touch on, if it doesn't happen naturally:

  • What to do if you feel uncomfortable.
  • Noisebridge strives to be radically inclusive. What does that mean?
  • Noisebridge has an antiharassment policy. What does that mean?

Don't get in people's face and shout at them.

You have the right to feel safe and welcomed here.

If you're concerned about someone's behavior, you can point to one of the signs to that effect and ask them to leave. If you are asked to leave, probably the best thing to do is leave, but you're not necessarily banned.


Invite a knowledgable volunteer to describe who can participate at Noisebridge, including:

  • Describe how to get an rfid key for the door system
  • Describe how to get access to slack

Noisebridge is open during the day. If you're here late members have a responsibility to close up so they might ask you to leave. Be careful with the equipment and be mindful of others' activities.

Noisebridge makes decisions based on consensus processes


  • Invite a knowledgeable volunteer to describe Philantropy, and the application process.
  • Read off any names from the binder for the past month. Any applicants must have their sponsor present to vouch for them.
  • If there are no objections, they're a philanthropist! Their pledge should be handed over to the Secretary posthaste, after which their token will be updated to give them the 24/7 access they've earned(?)

If you donate to Noisebridge monthly you can apply to become one and that status can be granted to you at a meeting.

Danny is requesting philanthropist status and there were no objections.

Membership Binder [edit]

  • Invite a knowledgeable volunteer to describe membership, and the application process.

Being a member of Noisebridge is not like being a member of a gym or your local chess club. Anyone can come to Noisebridge to hack and learn: you don't need to be a member for that. At Noisebridge, membership is something different: it means taking responsibility and committing to help to maintain, improve, and govern Noisebridge. As a member of Noisebridge, you don't just come here to hack and learn, you actively work to improve what you see around you, help to deal with problems, and make this community and space better than it is today.

  • Read off any names from the binder for the past month. Mark down a check or other indicator on every open application to keep track of how many weeks they've been read out.
  • Anyone eligible to join this week should
    • introduce themselves,
    • answer any questions members may have for them, then
    • leave the area in search of gifts (traditionally beer and a lime, or cookies) for the rest of the group.
  • The rest of the meeting should reach consensus on whether they may join.
  • Remember to applaud new members when they return.

(Members can block in a consensus process, but everyone can come and use the space)

- Merlin applied for membership - week 3 - Lee applied as well

Financial Report[edit]

Financial report for the meeting 7/11/2017. We have $79,430.79 in the bank. ~$28,000 for Noisetor, $7,318.89 in the equipment fund, $1,117.29 in the laser maintenance fund, $1,291.81 in the Thomas J. Shutt Memorial Fund, and the rest (about $41,702.80) in the general fund. That is slightly over 8 months of regular expenses.


  • 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 [edit]

(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 [edit]

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

(no consensus items were brought up)


Longer discussion items belong here. This is the last part of the meeting so that people can break off and continue their discussion afterwards.

- Choosing a logo for the 10th anniversary celebration. See the wiki for the proposals. Consensus seemed to be around the ones at the bottom.

Discussion Items[edit]

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

discussion here

End of Meeting[edit]

  1. Return the membership binder to its rightful location.
  2. Discuss any items for which there was not time during the meeting.
  3. Enjoy the company of your fellow hacker, robot, or robothacker.

Note taker posts the notes[edit]

  1. Clean and tidy the meeting notes including removing all these really verbose instructions.
  2. Fill out the short summary at the top listing just announcements, consensus items, discussion topics, and names of new members and philanthropists.
  3. Copy paste the notes to the next meeting page. (They will become Last meeting at midnight.)
  4. Email the meeting summary to Noisebridge Discuss and Noisebridge Announce lists.
  5. CC on the email and if there are new members and philanthropists.
  6. Edit the Current Consensus Items if anything is proposed for consensus next week.
  7. Edit the Consensus Items History if anything was reached consensus or failed to reach consensus this week.

Fun things to do after[edit]

  • 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.