Editing Meeting Notes 2012 07 03

= Instructions =
* '''Delete these instructions section before posting completed minutes.'''
* Pick a moderator and a note-taker.
* Optionally: pick a membership-binder-wrangler; otherwise the moderator can take care of it.

== Note-taker ==
* Open a text editor to take notes on the major points of the meeting, using this page at the template.
* Project the draft meeting notes and agenda in real time throughout the meeting.
* 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 out a summary with a link.
* Tell treasurer@noisebridge.net and secretary@noisebridge.net if there are new members.

== Moderator==
* 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 ==
* 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.

= Agenda =

[https://www.noisebridge.net/wiki/Category:Meeting_Notes The 223rd Meeting of Noisebridge]

Note-taker: FIXME YOUR NAME HERE

Moderator: FIXME THEIR NAME HERE
 
== Introduction and Names ==

* '''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>
* '''Invite a knowledgeable volunteer to give '''[[Consensus Process|a brief primer on consensus process]]: We agree and so should you! Only paid-up members can block consensus.
* Introduce any new or unusual moderation techniques that you 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, 
** are you a member,
** what do you do, and
** if you are new: how did you hear about Noisebridge?

== Short Announcements ==
* 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.

== New or Stale Events ==
* Is there anything new happening at the space?
* Is there anything that has stopped happening at the space?
* If this is the first meeting of the month, review all the [[Category:Events | events at the space]] and try to weed out stale events.

== [[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 better than it is today.</blockquote>
* Read off any names from the binder for the past month. Write a check on every open application.
* 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):

== Consensus items ==
You may wish to '''invite a knowledgeable volunteer to repeat '''[[Consensus Process|a brief primer on the consensus process]].

=== Proposals from last week ===

''(Add any items which pass or are blocked to the [[Consensus Items History]] page.)''

=== Proposals for next week ===

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

== Discussion Items ==

If an item of discussion drags on too long, further discussion may be postponed until after the meeting ends.

During discussion, it is not necessary to write down exact what each person says. Record the topics of discussion, and any items of consensus or controversy here. Detailed descriptions of the conversation should go on the discuss page for this meeting.

== End of Meeting ==
* [[PGP|PGP Key Signing]] could happen now, check the [[PGP|list]] to see who wants in on the action.
* Return the [[membership binder]] to it's rightful location.
* Clean and tidy the meeting notes, then save them to the wiki.
* Send a summary of the meeting notes to the discussion list.
* Enjoy the company of your fellow hacker or robot.
* Discuss any items for which there was not time during the meeting.

[[Category:Meeting Notes]]