Meeting Notes 2015 08 18: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(Created new meeting page)
 
No edit summary
Line 1: Line 1:
----------->8----------
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
= Instructions =
Congratulations and/or condolences! You're reading this because you're participating in a meeting of Noisebridge!
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 discusions, 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 ==
* Open a text editor to take notes on the major points of the meeting, using this page as the template.
* Project the meeting notes in real time throughout the meeting. Its super cool to use a collaborative editor such as pad.riseup.net or piratepad so that everyone is free to participate in the note taking.
* 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.
* Post the meeting notes to this page, and email the announcement and discussion list with a short summary.
* Tell treasurer@noisebridge.net and secretary@noisebridge.net if there are new members.
== Facilitators ==
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 [[consensus|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.'''
== Participants ==
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!!!
----------->8----------
These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]. Note-taker: FIXME YOUR NAME HERE; Moderators: FIXME THEIR NAME HERE.
* '''One or two bullet points of high-level meeting summary.'''
= Introductions =
= Introductions =


* '''Invite a knowledgeable volunteer to explain''' [[Noisebridge_Vision|what Noisebridge is about]]:
* Yemel: argentina, works for a company in SF. worked remotely in Buenos Aires and rented a place where they all worked together. hacked projs in spare time. interested in the concept of a hacker space
<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>
* Paul: from montreal
* Introduce any experimental or unusual moderation techniques that may be using during the meeting like: direct responses, limited speaking time, orderless stack, &c.
* Jack: DC and boston. moved here in nov.
* Round of introductions (remember, announcements come later):
* Sloan: sf been involved in this space for a while
** What's your name
* Dan: conneticut, went to school in Philly, been here a year.  
** What do you do
* Gordon: works with yemel, read homeland and read about  noisebridge. found a hackerspace in atlanta.  
** What do you maintain at Noisebridge?
* Joyti: lawyer, but teaching herself to code. hoping to become philanthropist
** if you are new: how did you hear about Noisebridge?
* Andrew: makes music and games. likes creating stuff
 
* Ami: introduced through mari. here for Unity class.
= Short announcements and events =
* Luis: makes art and games. also here for runity
* Cool new projects? Something you'd like people to know? Say now, but keep it short! One or two sentences please!
* Yoshi: from japan. majoring in marketing and a bit of computer science. friend in japan told him about
* Any happenings at the space of which members should be made aware.
* Nathan: computer scientist by education, game designer by trade
* Don't hog everyone's time since we all just want to hack!
* Mark: game designer, interested in all sorts of game stuff. likes doing art, music, etc.  
 
* Mari: i like video games and i’m taking notes
= [[ Membership Binder ]] =
* J: been around nb for a while since teh reboot. sysadmin. #1 reasons why i love this place is that this reflects what i truly believe that knowledge should be f ree, available and accessible to everyone. all you need is desire and time, and that’s why i love NB
 
* '''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.
 
= [[Philanthropists]]=
* '''Invite a knowledgeable member 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(?)
 
= 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 and Discussion =
 
* '''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 Items ==
 
If any important discussion happens, it should be happening after forward progress is made during consensus.
 
= End of Meeting =
 
* 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.
* 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.
 
[[Category:Meeting Notes]]

Revision as of 22:05, 18 August 2015

Introductions

  • Yemel: argentina, works for a company in SF. worked remotely in Buenos Aires and rented a place where they all worked together. hacked projs in spare time. interested in the concept of a hacker space
  • Paul: from montreal
  • Jack: DC and boston. moved here in nov.
  • Sloan: sf been involved in this space for a while
  • Dan: conneticut, went to school in Philly, been here a year.
  • Gordon: works with yemel, read homeland and read about noisebridge. found a hackerspace in atlanta.
  • Joyti: lawyer, but teaching herself to code. hoping to become philanthropist
  • Andrew: makes music and games. likes creating stuff
  • Ami: introduced through mari. here for Unity class.
  • Luis: makes art and games. also here for runity
  • Yoshi: from japan. majoring in marketing and a bit of computer science. friend in japan told him about
  • Nathan: computer scientist by education, game designer by trade
  • Mark: game designer, interested in all sorts of game stuff. likes doing art, music, etc.
  • Mari: i like video games and i’m taking notes
  • J: been around nb for a while since teh reboot. sysadmin. #1 reasons why i love this place is that this reflects what i truly believe that knowledge should be f ree, available and accessible to everyone. all you need is desire and time, and that’s why i love NB