Difference between revisions of "Meeting Notes 2017 05 02"

From Noisebridge
Jump to: navigation, search
(Created new meeting page)
 
Line 1: Line 1:
----------->8----------
+
introductions
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
+
Jarod - mostly works on woodworking and makerfaire project
 +
matt - new in the bay are, heard about noisebridge at an AI conference, excited ot be here
 +
Joyti - I'm a person
 +
Jacob - been coming for 3-4 months, gonna apply to be a member soon!
 +
Darrel - works on AI & functional programming stuff, teaches laser cutter
 +
Frank - studying methods in data communications
 +
Ryan - been coming for a couple of years, working on gamebridge, gonna teach some classes
 +
Noah - hosts Stupid hackathon, donated axidraw
 +
Diego - musician, works at gray area, learn ableton
 +
blaze - been coming for 3 months, donated occulos, wants to send a humanoid robot into space
 +
lizzy - works on computer security, electronics, and more!
 +
varun - first time here!
 +
Marco - working on a web application to help beginners learn web arcitecture, wants to work on a code education program
 +
Jonah - web dev affinity for collaborative community spaces
 +
Aaron - software engineer who enjoys functional programming
 +
Nicole - works on webdev and hosts a coding event on tuesdays
 +
Alex - !
 +
keita - working on iOS apps, organizes sunday morning iOS events
  
= Instructions =
+
Short announcements and events:
 +
Darrel:
 +
* Next wednesday at 7:30(?) Paul Sass - organizer of Bay CHI - is going to be giving a workshop about behavioral economics and polite robots.
 +
Marco:
 +
* Organizing code eductation co-working group, looking for a space, maybe noisebridge? Curious what day would be a good time for it. First event will be on May 9 from 6-9pm
 +
Diego:
 +
* Thurs-Sat Gray Area festival, come! Lots of music and talks! Only $5! grayarea.org
 +
Noah:
 +
* Stupid Hackathon May 13-14. Come early and help clean! Come during it and help people experience Noisebridge for the first time! But come!
 +
Jarod:
 +
* Makerfaire!!! Is 19-20-21, the photo booth is a project! Gamebridge university has a VR game as well. If you want to help with Makerfaire, send hicksu@gmail.com a message saying so!
 +
Darrel:
 +
* Tomorrow Yonas's future of programming meetup is happening (7:30am?) Come and chat about magic haskeller!
 +
Jarod:
 +
* Vice interview happening on thurs/fri, giving us a donation and will make sure to get consent before showing anyone's faces. mcscope can provide more info if needed.
  
Congratulations and/or condolences! You're reading this because you're participating in a meeting of Noisebridge!
+
Consensus:
 +
It's a thing
 +
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.
  
Meetings should be limited to an hour when possible. Shorter is fine, but avoid rushing.
+
Concensus whenever there are important issues
 +
two types large C- when ever there are any big issues the go through two weeks of deliberation tell people agree, or they can block it.
 +
Do-ocracy do what you want to do-
 +
blocking is a big deal, one block will halt that item instantly (only do it if you think it will ruin the space (IE lets set the building on fire)).
  
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.
+
Noisebridge as a safe space:
 +
You should feel safe here, if someone is making you uncomfortable you should feel able to ask them to leave.
 +
Read the noisebridge wiki to learn how to act around people and tools
  
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.
+
Participation:
 +
How to participate - there's a slack!
 +
If someone has been coming around for a while, someone will offer you slack access. We use slack unoficially to organize things in the space. It's not required but it's a nice way to keep up with what's going on.
 +
Access:
 +
the door is RFID, any member can give 30-day daytime access. If you need more access, become a member or talk to a philanthropist.
  
== Note Takers ==
+
Philanthropist:
# Confirm last meeting was saved
+
If you make a continued contribution to NB (monitarily) and take on more responsibility you can get more privileges. With great power comes great responsibility, you should know how to close up the space at night, and deal with space management. There's a binder to apply! Unlike members they're not central in voting and consensus.
# Take new notes
 
# Save and share the notes at the end of the meeting (instructions at the bottom).
 
  
== Facilitators ==
+
2 open applications:
 +
Nicole - sponsored by 2 people. No objections!
 +
Kevin - not here.
  
There are generally two kinds of facilitator roles at a Noisebridge meeting:
+
Membership:
 +
Takes on a larger role for organizing things and large C consensus things. Can activate other people's RFIDs and sponsor people. More of a process.
  
* 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.
+
No financial report on slack this week
* 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:
+
consensus items:
* Understand the structure of Noisebridge [[consensus|decision-making]]
+
no pending
* Make sure everyone gets a chance to speak.
+
no new
* 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.'''
 
  
== Participants ==
+
Discussion items:
 
+
Demitrius - Started a meet-up called SF innovators club, to help and support each other achieve goals. Had first meet-up a month and a half ago. Wants to do next meet-up here. In 2 weeks an Tuesday 6pm in Turin room. on meetup at sf innovator's club
Everyone at a Noisebridge meeting who has consented to participating in one is a participant!
+
Marco - J mentioned wednesday might be the best time. May 10 6-9pm?
 
+
Ryan - His high school is going to be gutted, it might have some things like lockers and screens - would people be interested in trying to get some of it donated? (people say 'yes, more lockers')
* 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!!!
 
----------->8----------
 
 
 
These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes 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:
 
* Announcements:
 
* Finances:
 
* New members:
 
* New philanthropists:
 
* Consensus Items:
 
* Discussion Items:
 
 
 
= Introductions =
 
 
 
* '''Invite a knowledgeable volunteer to explain''' [[Noisebridge_Vision|what Noisebridge is about]]:
 
<blockquote>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'."</blockquote>
 
* 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?
 
 
 
= 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?
 
 
 
= Participation =
 
 
 
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
 
 
 
= [[Philanthropist|Philanthropists]]=
 
* '''Invite a knowledgeable volunteer to describe''' [[Philanthropist/Pledge|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(?)
 
 
 
= [[ Membership Binder ]] =
 
 
 
* '''Invite a knowledgeable volunteer to describe''' [[membership]], and the application process.
 
<blockquote>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.</blockquote>
 
* 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
 
 
 
= Consensus =
 
 
 
* '''invite a knowledgeable volunteer to give '''[[Consensus Process|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.
 
 
 
== [[ Consensus Items History | 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.)''
 
 
 
== [[ Current Consensus Items | Proposals for next week ]] ==
 
''(Add any new items for consensus to the [[Current Consensus Items]] page.)''
 
 
 
 
 
= Discussion =
 
 
 
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 [http://www.noisebridge.net//Next_meeting next meeting] page. (They will become [[Last meeting]] at midnight.)
 
# Email the meeting summary to [mailto:noisebridge-discuss@lists.noisebridge.net?subject=MeetingNotes Noisebridge Discuss] and [mailto:noisebridge-announce@lists.noisebridge.net?subject=MeetingNotes Noisebridge Announce] lists.
 
# CC on the email treasurer@noisebridge.net and secretary@noisebridge.net if there are new members and philanthropists.
 
# Edit the [[Current_Consensus_Items|Current Consensus Items]] if anything is proposed for consensus next week.
 
# Edit the [[Consensus_Items_History|Consensus Items History]] if anything was reached consensus or failed to reach consensus this week.
 
 
 
== Fun things to do after ==
 
* Reprise of the [[Hackernationale]]. [This is anarchy - we do what the wiki says!]
 
* [[PGP|PGP Key Signing]] could happen now (if it doesn't happen '''before''' any given Meeting).  Ask others around the space or check the [[PGP|list]] to see who wants in on the action.
 
  
  
 
[[Category:Meeting Notes]]
 
[[Category:Meeting Notes]]

Revision as of 01:35, 6 May 2017

introductions Jarod - mostly works on woodworking and makerfaire project matt - new in the bay are, heard about noisebridge at an AI conference, excited ot be here Joyti - I'm a person Jacob - been coming for 3-4 months, gonna apply to be a member soon! Darrel - works on AI & functional programming stuff, teaches laser cutter Frank - studying methods in data communications Ryan - been coming for a couple of years, working on gamebridge, gonna teach some classes Noah - hosts Stupid hackathon, donated axidraw Diego - musician, works at gray area, learn ableton blaze - been coming for 3 months, donated occulos, wants to send a humanoid robot into space lizzy - works on computer security, electronics, and more! varun - first time here! Marco - working on a web application to help beginners learn web arcitecture, wants to work on a code education program Jonah - web dev affinity for collaborative community spaces Aaron - software engineer who enjoys functional programming Nicole - works on webdev and hosts a coding event on tuesdays Alex - ! keita - working on iOS apps, organizes sunday morning iOS events

Short announcements and events: Darrel:

  • Next wednesday at 7:30(?) Paul Sass - organizer of Bay CHI - is going to be giving a workshop about behavioral economics and polite robots.

Marco:

  • Organizing code eductation co-working group, looking for a space, maybe noisebridge? Curious what day would be a good time for it. First event will be on May 9 from 6-9pm

Diego:

  • Thurs-Sat Gray Area festival, come! Lots of music and talks! Only $5! grayarea.org

Noah:

  • Stupid Hackathon May 13-14. Come early and help clean! Come during it and help people experience Noisebridge for the first time! But come!

Jarod:

  • Makerfaire!!! Is 19-20-21, the photo booth is a project! Gamebridge university has a VR game as well. If you want to help with Makerfaire, send hicksu@gmail.com a message saying so!

Darrel:

  • Tomorrow Yonas's future of programming meetup is happening (7:30am?) Come and chat about magic haskeller!

Jarod:

  • Vice interview happening on thurs/fri, giving us a donation and will make sure to get consent before showing anyone's faces. mcscope can provide more info if needed.

Consensus: It's a thing 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.

Concensus whenever there are important issues two types large C- when ever there are any big issues the go through two weeks of deliberation tell people agree, or they can block it. Do-ocracy do what you want to do- blocking is a big deal, one block will halt that item instantly (only do it if you think it will ruin the space (IE lets set the building on fire)).

Noisebridge as a safe space: You should feel safe here, if someone is making you uncomfortable you should feel able to ask them to leave. Read the noisebridge wiki to learn how to act around people and tools

Participation: How to participate - there's a slack! If someone has been coming around for a while, someone will offer you slack access. We use slack unoficially to organize things in the space. It's not required but it's a nice way to keep up with what's going on. Access: the door is RFID, any member can give 30-day daytime access. If you need more access, become a member or talk to a philanthropist.

Philanthropist: If you make a continued contribution to NB (monitarily) and take on more responsibility you can get more privileges. With great power comes great responsibility, you should know how to close up the space at night, and deal with space management. There's a binder to apply! Unlike members they're not central in voting and consensus.

2 open applications: Nicole - sponsored by 2 people. No objections! Kevin - not here.

Membership: Takes on a larger role for organizing things and large C consensus things. Can activate other people's RFIDs and sponsor people. More of a process.

No financial report on slack this week

consensus items: no pending no new

Discussion items: Demitrius - Started a meet-up called SF innovators club, to help and support each other achieve goals. Had first meet-up a month and a half ago. Wants to do next meet-up here. In 2 weeks an Tuesday 6pm in Turin room. on meetup at sf innovator's club Marco - J mentioned wednesday might be the best time. May 10 6-9pm? Ryan - His high school is going to be gutted, it might have some things like lockers and screens - would people be interested in trying to get some of it donated? (people say 'yes, more lockers')