Meeting Notes Template: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
m (Moved summary to top)
(50 intermediate revisions by 22 users not shown)
Line 1: Line 1:
<!-- best practices for meeting notes template. 
----------->8----------
#1 copy the template to the correct date for the upcoming meeting
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
#2 edit the meeting notes date to reflect the date of the meeting
#3 edit the meeting number to reflect the nth meeting of Noisebridge
#4 (wish all this was programmatic!)
#5 this page often 'dead-ends' and is consequently difficult to navigate usefully.  Add and update links in the meeting notes template as necessary to make the notes more dynamic and useful for all
-->


== HOWTO moderate a meeting ==
= Instructions =


Anyone can moderate the meeting, though it helps a great deal if you have been to meetings before.
Congratulations and/or condolences! You're reading this because you're participating in a meeting of Noisebridge!


0. '''Say "Five minutes to meeting!".''' This will give you time to read these instructions.
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.


1. Get someone to '''grab the membership binder'''. It is kept near the shrine, which is currently on the south wall, between the electronics and sewing areas.  
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.


2. '''Get someone to take notes.''' Point the shocked and bemused note-taker to the sub-instructions below these instructions.  
== Note Takers ==
# Confirm last meeting was saved
## Check [http://www.noisebridge.net/Last_meeting Last meeting] page to confirm the Riseup pad notes were saved there at end of last meeting.
## Does the text date match the page date? Great!
## If not and the [http://pad.riseup.net/p/nbmeeting Riseup pad] looks like last week, copy the unsaved  notes into [http://www.noisebridge.net/Last_meeting Last meeting]. If you need to clear up confusion, check the [https://noisebridge.net/wiki/Category:Meeting_Notes meeting notes archive] to make sure.
# Take new notes
## Open the shared text editor pad [http://pad.riseup.net/p/nbmeeting pad.riseup.net/nbmeeting].
## Project the notes in real time for all to see and announce the URL to collaboratively take notes on the major points of the meeting.
## Copy paste the [https://noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit Meeting Notes Template]] markup into the Riseup pad.
## Begin lines with * or separate lines with blank space because [https://www.mediawiki.org/wiki/Help:Formatting Mediawiki syntax] ignores single carriage returns.
# Save and share the notes at the end of the meeting (instructions at the bottom).


3. (Optional) '''Get someone to put this wiki page up on the projector'''.
== Facilitators ==


4. Skim '''read through the Agenda''' below that to get a feel for what a meeting will looks like.
There are generally two kinds of facilitator roles at a Noisebridge meeting:


5. People may have added '''Discussion Items''' to this page, or they may raise them during the meeting. If they emerge during the meeting, suggest that they be discussed _in_ the Discussion Item section, rather than derail other sections of the meeting. Discussion for these can be open-ended, but you should aim to wrap up the meeting within an hour. It can be handy to explicitly summarise what people intend to do as a result of the discussion. There is no requirement on you, Noisebridge the organization, or anyone else to do anything as a result of a discussion item.
* 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.


6. If there are '''Consensus Items''', ensure that they were raised in meeting last week (the membership needs a week's warning for consensus items). Your main job in consensus is to listen to what everyone is saying, make sure everyone gets a chance to say something, and then -- if the debate is beginning to go round in circles or settle -- propose a Position that everyone seems to agree on. If people disagree with the Position, they will wrangle some more, or someone else will propose a Position. If no-one disagrees with the Position, say "So do we consense on $POSITION?". If no one objects, ask the note-taker to record the Position. If things are getting nowhere and we're all getting bored and antsy, identify the people objecting, and ask them to discuss the problem with the proposers of Consensus Item outside the meeting, and return next week with a compromise solution.
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.'''


7. '''Shout "Meeting starts now!" now''', and start reading (out loud) through the Agenda!
== Participants ==


8. '''When you are done, consult with the note-taker,''' and make sure they know what they have to do to finish their job -- especially updating the wiki, and mailing nb-discuss, and the treasurer with new membership details.
Everyone at a Noisebridge meeting who has consented to participating in one is a participant!


9. '''Put back the membership binder''' by the Shrine.  
* 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.


10. '''Bathe in the glow''' of the respect of your fellow Noisebridgers.


DELETE EVERYTHING ABOVE THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
----------->8----------


=== HOWTO note-take a meeting ===
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.'''


0. Your moderator should give you five minutes to '''read these instructions'''. If they don't, say "Woah there cowboy, I need to know what I'm doing. Five minutes, por favor!". Use exactly those words.
== 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:


1. This page should have a URL like "https://www.noisebridge.net/wiki/Meeting_Notes_2010_12_28", with today's year, month and date in it. If doesn't, copy [Meeting Notes Template] to a wiki page with that kind of URL. If you don't know how to copy wiki pages, say, "Can someone help me with the Noisebridge Wiki?", and get them to create a page with that kind of URL, and then show you how to copy this page to it and edit it.
= Introductions =


2. '''Edit this page.''' Add notes under each category -- you can delete any placeholder explanatory text as you go.
* '''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?


3. '''Save the wiki page when you're done''' (no-one expects you to finish as the meeting is finished; it usually takes a half-hour or so after the meeting to get everything in order). Try to hyperlink stuff that should be linked. You can delete all this patronising instructional crap. Here's [Meeting_Notes_2010_12_28 an example] of a finally edited meeting.
= 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!


4. '''Create a page for next week's meeting''', by copying over [[Meeting Notes Template]] to an URL with next week's date in it (see step 1). If anybody proposed Consensus Items for next week, write them in here, and add them to the [[Current Consensus Items]].
= [[ Membership Binder ]] =


5. If there were any consensus items decided at your meeting, '''add them to [[Consensus Items History]], and take them out of the [[Current Consensus Items]]'''.
* '''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.


6. Go to [https://www.noisebridge.net/&action=edit&section=3 the front page meetings notice] and edit the page that ''so that the Prev and Next meetings now point to this meeting notes, and the new meeting notes you just created respectively'''. (If that link is broken, it's a section half-way down the [[https://www.noisebridge.net/ front page]]
= [[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(?)


7. '''Important!''' Send a final copy of the notes to '''noisebridge-discuss''', and '''email treasurer@noisebridge.net the details of any new members''' (you can get all the details from the membership binder, which may now be hidden over by the shrine.)
= 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


8. Chill out, have a cocktail with a friendly robot, continue to rock the world.
= Consensus and Discussion =


== Agenda ==
* '''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.


[https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]
== [[ 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.)''


Note-taker: FIXME YOUR NAME HERE
== [[ Current Consensus Items | Proposals for next week ]] ==
''(Add any new items for consensus to the [[Current Consensus Items]] page.)''


Moderator: FIXME THEIR NAME HERE
== Discussion Items ==


=== Introduction and Names ===
If any important discussion happens, it should be happening after forward progress is made during consensus.
* [[Noisebridge_Vision|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'."
* Round of introductions: What's your name, what do you do, and if you are new, how did you hear about Noisebridge? Start with the moderator and go left.
* [[Consensus Process|A brief primer on consensus process]]: We agree and so should you! Only paid-up members can block consensus.


=== Announcements ===
= End of Meeting =


=== Financial Report ===
# Return the [[membership binder]] to its rightful location.
Funds in bank:
# Discuss any items for which there was not time during the meeting.
# Enjoy the company of your fellow hacker, robot, or robothacker.


=== Membership Binder ===
== Note taker posts the notes ==
* Read off any names from the binder for the past month.
# Clean and tidy the meeting notes including removing all these really verbose instructions.
* Anyone up for join this week should introduce themselves then leave the area in search of gifts (traditionally beer and a lime) for the rest of the group. The rest of the meeting should consense on whether they may join.
# 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.


=== What's Going On at Noisebridge ===
== Fun things to do after ==
''One '''short''' sentence about each of the following:''
* 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.


===== Weekly =====
<!----
The following events are listed with day of week, time the session starts, and location.
For locations at Noisebridge, see a map of the [[2169_map|2169]] location of Noisebridge.
--->
For locations at Noisebridge, see a map of the [[2169_map|2169]] location of Noisebridge.
* [[Circuit_Hacking_Mondays|Circuit Hacking Mondays]] (Monday, 7PM,  E Lab)
* [[iPhone OS developer weekly meetup]]  -- (Monday, 6PM, A. Church) Meetups are becoming increasingly well attended, interested Noisebridge folks are encouraged to sign up at http://meetup.com/iphonedevsf , as that is where any important announcements and discussions take place. Contact [[User:Nickthedude | Nickthedude]] with any questions.
* [[Pyclass]] - Mondays (Monday, 7PM, A. Turing)
* [[Cooking_Classes |Tastebridge cooking class]] - (Tuesday, ~5PM, NoiseKitchen)
* [[Probability]] (Tuesdays, 7.30pm, A. Church)
* [[Unityversity |GameDevelopment]] - (Wednesday, 7PM, E Lab/Main Hall]]
* [[Cultured_Drinks_Brewing_Program |Tastebridge culturing]] - (Wednesday, ~6PM, NoiseKitchen)
* [[SCoW]] craft group - (Wednesday, 7PM, SCoW area)
* [[Machine_Learning]] - (Wednesday, 7:30PM, A. Church)
* Linux System administration certification study group - (Wednesday, 6PM, A. Turing)
* [[Spacebridge]] - (Sundays, Main Hall)
* Knots, [[Go]], and [[Locks!]] - (Sunday afternoon, Main Hall)
===== Non-weekly =====
* [[Second Saturdays]] are Noisebridge buildout days.
* [[Five Minutes of Fame]]
* Bay Area Hackers Association - (Second Sunday, 2PM)
=== Project Updates ===
(Anyone doing interesting projects is welcome to chip in here.)
=== Consensus items ===
=== Discussion Items ===
''(Add any new items for consensus to the [[Current_Consensus_Items|Current Consensus Items]] page.)''
=== End of Meeting ===
* [[PGP|PGP Key Signing]] could happen now, check the [[PGP|list]] to see who wants in on the action.
* Put back the membership binder by the Shrine at the northeast corner.
* Save the meeting notes to the wiki.
* Send a copy of the meeting notes to the discussion list.
* Copy the [[Meeting Notes Template]] for next week's agenda and update the main wiki page's link to it.
* Enjoy a cocktail with your fellow hacker or robot.


[[Category:Meeting Notes]]
[[Category:Meeting Notes]]

Revision as of 18:50, 9 December 2015


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

  1. Confirm last meeting was saved
    1. Check Last meeting page to confirm the Riseup pad notes were saved there at end of last meeting.
    2. Does the text date match the page date? Great!
    3. If not and the Riseup pad looks like last week, copy the unsaved notes into Last meeting. If you need to clear up confusion, check the meeting notes archive to make sure.
  2. Take new notes
    1. Open the shared text editor pad pad.riseup.net/nbmeeting.
    2. Project the notes in real time for all to see and announce the URL to collaboratively take notes on the major points of the meeting.
    3. Copy paste the Meeting Notes Template] markup into the Riseup pad.
    4. Begin lines with * or separate lines with blank space because Mediawiki syntax ignores single carriage returns.
  3. Save and share the notes at the end of the meeting (instructions at the bottom).

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

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?

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!

Membership Binder

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

Philanthropists

  • Invite a knowledgeable member 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(?)

Financial Report

Consensus and Discussion

  • 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

(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

(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

  1. Return the membership binder to its rightful location.
  2. Discuss any items for which there was not time during the meeting.
  3. Enjoy the company of your fellow hacker, robot, or robothacker.

Note taker posts the notes

  1. Clean and tidy the meeting notes including removing all these really verbose instructions.
  2. Fill out the short summary at the top listing just announcements, consensus items, discussion topics, and names of new members and philanthropists.
  3. Copy paste the notes to the next meeting page. (They will become Last meeting at midnight.)
  4. Email the meeting summary to Noisebridge Discuss and Noisebridge Announce lists.
  5. CC on the email treasurer@noisebridge.net and secretary@noisebridge.net if there are new members and philanthropists.
  6. Edit the Current Consensus Items if anything is proposed for consensus next week.
  7. Edit the 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 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.