Meeting Notes 2015 02 03

From Noisebridge
Jump to navigation Jump to search


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

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

Introductions[edit]

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?
  • Naomi Has been coming to NB since 2009
  • Signal - is into Activism
  • Calvin- Chess is better than iPad
  • Monad - A tinkerer that likes beer
  • Jarrod - I like to make things
  • J - Has been coming since last year before the reboot (has a truck)
  • Sam _ Sofware Eng in Biotech.
  • Joakim - 1st tme. Research about 3D Printer
  • Anastasia - Came in 2 days ago
  • John Foot - Long time NB. CNC Mill. Ran Dorkbot party. Internet control Xmas lights
  • Steve- Software Engineer
  • Henner - 4 yrs helping with the infrastrcture. RFID
  • Mickey - Has been a member since 2008
  • Daniella- Has been coming to NB for 3yrs
  • Ana Rose - Silicon Wafers.
  • Gautal - 1st at NB
  • Chris - Working on a Cat Scraching post. He is in Education
  • Roger - From Philly
  • Genine- Is into City Planning Urban Studies
  • Mischief
  • Evan - Into TV be gone. Is working on shooting a documentary
  • Josh-
  • John Major- Scientist, 2 story glowing
  • Yannick - Been here for a few months. Would like to organize a workshop on javascript
  • Yury
  • Scottie - Working on building the library
  • Patrick - He into Hardware and Security. Working on NB infrastructure talk to him the next 6 weeks


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!

'''Announcements'''

Yannik: Workshop on Web Technologies.

    • Find s time and a place to do it
    • Put it on the events Calendar
    • It should be opened to anybobody
    • It may be a good idea to build a Wiki

Jarrod: MakerFaire

    • Exibits: Present NoiseBridge on a good light
    • Plans on table presented
    • Plans to work every Thursday
    • LED Lights

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.

* No binder was found. No new members at the meeting

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

Financial Report[edit]

  • Funds in bank: NB has a out 6 weeks of Operating income. Need ideas for fundraising. Need to generate a lump sum to create 10K.

It cost 4800 to run NB per month. About 78K a year. Current Members is on the teens Employers matching donations are welcome (Tax deductible) MS and Google are already doing it


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

Proposals for next week [edit]

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

Discussion Items[edit]

Membership discussion

    • Fill out application
    • Get 2 sponsors
    • Read statements
    • Concense the Person
    • $80 dollars a month.

Access Control Discussion

    • Keys, minimize the number of keys to upstairs

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

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.