Meeting Notes 2017 11 21
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
Congratulations and/or condolences! You're reading this because you're participating in a meeting of Noisebridge!
Meetings should be limited to an hour when possible. Shorter is fine, but avoid rushing.
You should read this instructional section thoroughly, and treat them as a guideline for how to host a meeting of Noisebridge. There are three ingredients to an Excellent meeting: A number of note takers, some facilitators, and participants.
Meetings are just one of the tools used at Noisebridge to create net forward progress on whatever it is we're all trying to do. Meetings aren't the only way to make decisions or have discussions, and in fact its usually a much better idea to talk about things outside the meeting before dragging the entire community kicking and screaming into it.
 Note Takers
- Confirm last meeting was saved
- Take new notes
- Save and share the notes at the end of the meeting (instructions at the bottom).
There are generally two kinds of facilitator roles at a Noisebridge meeting:
- Stack taker - Useful when a lot of folks want to hop on the discussion stack. This gives everyone a turn to have their feelings heard. Usually only works when there is exactly one stack taker.
- Moderators - Keeps the meeting moving and prevents everyone from wasting too much time on one subject. Anyone is free to pick up moderation and move the meeting along.
In general, moderators should:
- Understand the structure of Noisebridge decision-making
- Make sure everyone gets a chance to speak.
- Speak only minimally yourself.
- Keep the meeting moving, and avoid getting bogged down.
- Identify discussion items, arrange times limits for talking about each item.
- Identify and summarize consensus, suggest things that need to be done.
- Get the membership binder and ensure that it is returned safely.
Everyone at a Noisebridge meeting who has consented to participating in one is a participant!
- Say your name before you talk.
- Remain on-topic, and speak as concisely as possible.
- Assist the note-taker with any links or corrections that are needed.
- Remain respectful of other participants, their time, and the consensus and moderation process.
DELETE EVERYTHING ABOVE THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
These are the notes from the The XXXth Meeting of Noisebridge. Date: FIXME THE DATE HERE Note-taker: FIXME YOUR NAME HERE; Moderators: FIXME THEIR NAME HERE.
- One or two bullet points of high-level meeting summary.
 Meeting Summary
FIXME FILL OUT AT END OF MEETING AND SEND TO MAILING LIST TLDR what happened at the meeting:
- New members:
- New philanthropists:
- Consensus Items:
- Discussion Items:
- Invite a knowledgeable volunteer to explain what Noisebridge is about:
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's your preferred pronoun?
- What do you do?
- What do you maintain at Noisebridge?
- if you are new: how did you hear about Noisebridge?
 Short announcements and events
- 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!
 Safe Space
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?
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
- 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(?)
- 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.
 Financial Report
- Funds in bank:
- Noisetor (See the bulletpoints at the bottom of http://noisetor.net/finances/#summary):
- Any other details by those participating in handling our financials
- 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.
(Add any items which are consensed upon or someone has raised a principle objection for to the Consensus Items History page.)
(Add any new items for consensus to the Current Consensus Items page.)
Longer discussion items belong here. This is the last part of the meeting so that people can break off and continue their discussion afterwards.
 Discussion Items
If any important discussion happens, it should be happening after forward progress is made during consensus.
 End of Meeting
- Return the membership binder to its rightful location.
- Discuss any items for which there was not time during the meeting.
- Enjoy the company of your fellow hacker, robot, or robothacker.
 Note taker posts the notes
- Clean and tidy the meeting notes including removing all these really verbose instructions.
- Fill out the short summary at the top listing just announcements, consensus items, discussion topics, and names of new members and philanthropists.
- Copy paste the notes to the next meeting page. (They will become Last meeting at midnight.)
- Email the meeting summary to Noisebridge Discuss and Noisebridge Announce lists.
- CC on the email firstname.lastname@example.org and email@example.com if there are new members and philanthropists.
- Edit the Current Consensus Items if anything is proposed for consensus next week.
- Edit the Consensus Items History if anything was reached consensus or failed to reach consensus this week.