Meeting Notes 2015 04 21

From Noisebridge
Jump to: navigation, search

These are the notes from the The 421st Meeting of Noisebridge. Note-taker: Kevin; Moderators: J.

  • One or two bullet points of high-level meeting summary.


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?
  • Olivier - Came to Noisebridge in February, does finance.
  • Jade - tutor Python + neurohacking on Wednesday
  • Dan - been coming from three years, also participate in neurohacking
  • Mike - third time there
  • Josh - I tinker
  • Frank - been coming for about a month
  • Alex - will start teaching video game design class again
  • John - Book scanner
  • J - helping with table for MakerFaire
  • David - food hacker

Short announcements and events[edit]

  • Cool new projects? Something you'd like people to know? Say now, but keep it short!
  • 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!
  • Alex will be teaching game development class on Tuesdays after the Noisebridge meeting.
  • http://pegasus/mute to quite the Noisebridge voice
  • Mike form the Nametag project (giving away 25,000 nametags in San Fran: Castro, Delores Park, Ocean Beack, Hayes Valley, possibly the Marina, possibly somewhere in Oakland) seeks Noisebridge involvement - possibly including electronic "Hello" name tags in the event would be great.

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.
  • Alex - week 1

Financial Report[edit]

  • Funds in bank: $31,378.56
  • Noisetor (See the bulletpoints at the bottom of $11,000.00 (approximate)
  • Any other details by those participating in handling our financials

We're above our 3 month buffer, but we're not yet cash-flow positive. I'm hoping to get more recent figures together as to the composition of our monthly income.

Consensus and Discussion[edit]

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

No pending consensus items

Proposals for next week [edit]

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

No new consensus items

Discussion Items[edit]

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

Nametag Day[edit]

Nametag -- 12,000 distributed in NYC last two years.

Governance -- a few people running it and a bunch of 'nametag day fanatics'

exists in four cities this year. goal to have it all over the planet and get people talking together.

Confusion with conferences?

Happens on the weekend, in parks.

Posters at Noisebridge work stations[edit]

Will be iconic and beginner friendly. Alex will put them up and if someone doesn't like them they can take them down.

Opening the space with the sun[edit]

Will not depend on goverenment time (Ex PDT), strictly sunrise. Call a webservice to get the daily sunrise time.

The space opens when someone is here to open it.

Clarification - the RFID cards should function to open the doors at sunrise.

Currently three types of keys:
0 - anon, expires 30 days, access 11:00-22:00
1 - not anon, does not expire, access 11:00-22:00
2 - not anon, does not expire, access 24hr, can enter new anon keys into DB

By policy, the space is as open as possible and members should have 24hr access. Open hours help to maintain safety.

End of Meeting[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.
  • 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.