Meeting Notes Template: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
m (Moved summary to top)
(15 intermediate revisions by 10 users not shown)
Line 1: Line 1:
You should read the [[meeting instructions]] forthwith!<br>
----------->8----------
Don't forget to '''post the meeting notes to the wiki''' and e-mail the discussion list with a short summary.
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!


These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The 286th Meeting of Noisebridge]. Note-taker: FIXME YOUR NAME HERE; Moderator: FIXME THEIR NAME HERE.
= 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 ==
# 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).
 
== 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]. 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.'''
* '''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 =
= Short announcements and events =
* Bullet point list of announcements and events
* Cool new projects? Something you'd like people to know? Say now, but keep it short! One or two sentences please!
5mof Thursday night 8pm
* Any happenings at the space of which members should be made aware.
Sudo room event Cryptoparty Sunday
* Don't hog everyone's time since we all just want to hack!
 
= [[ Membership Binder ]] =
= [[ Membership Binder ]] =


* The name of the applicant, the week of their application, and their sponsors.
* '''Invite a knowledgeable volunteer to describe''' [[membership]], and the application process.
Mary Panescus, week 2, no sponcers
<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>
Hilaire, AM week one, Justin, Monad
* 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.
Robert, w1 AM
* Anyone eligible to join this week should
Amber w1 stone AM
** introduce themselves,
Jay stone w1 AM
** answer any questions members may have for them, then
chritina w1 M 1s JC
** leave the area in search of gifts (traditionally beer and a lime, or cookies) for the rest of the group.
Andrew M
* The rest of the meeting should reach consensus on whether they may join.
Kiera Wong w1 1s
* 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 =
= Financial Report =
$1000 donated by art eventSudo room event Sunday
No treasurer report
* Funds in bank:
* Funds in bank:
* Noisetor (See the bulletpoints at the bottom of http://noisetor.net/finances/#summary):
* 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 =
NONE
== [[ Consensus Items History | Proposals from last week ]] ==
== [[ Consensus Items History | Proposals from last week ]] ==
''(Add any items which pass or are blocked to the [[Consensus Items History]] page.)''
''(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 ]] ==
== [[ Current Consensus Items | Proposals for next week ]] ==
''(Add any new items for consensus to the [[Current Consensus Items]] page.)''
''(Add any new items for consensus to the [[Current Consensus Items]] page.)''
monad:Asking Pidgeon to leave, exclusion... - moved to next week
Jake via proxy :


"Membership to Noisebridge should no longer be dependant on a person's
== Discussion Items ==
ability or willingness to pay money to noisebridge, or to bring food
or beer to a meeting, but only on their ability to acquire sponsorship
signatures and be consensed upon at a meeting, after leaving the
meeting to give opportunity for any objections to be discussed before
they return.
Members will thus enter and remain in good standing without regard to
any financial contributions they do or do not make in that time.
A Member can be suspended by consensus minus one, meaning that consensus
by the group can suspend indefinitely the membership of a person over that
person's objections."


General thoughts: should be addressed... amemd members don't have to pay, donors would be the new term for those that pay..
If any important discussion happens, it should be happening after forward progress is made during consensus.
If we restrict access, we cannot limit those who may not be able to afford the $40, and still want access to the space..
Govt should fund hackerspaces..
Volunteering should be alternative to paying cash, to be held accountable..
Monad: valuation?


= Discussion Notes =
= End of Meeting =
John - darkroom, misuse. Nadine sleeping there, do we need to exclude if she tries it again, (she in fact doesn't live here).. Lack of communication, better use of space
Rayc - announcment, $1000 was donated by Asterisk Gallery/Johan... Go Andrea


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


= Attendance =
== Fun things to do after ==
* List of names and short summary. For bonus points, link wiki user pages.
* Reprise of the [[Hackernationale]]. [This is anarchy - we do what the wiki says!]
Chelsea
* [[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.
Rohan
Chris - Book Scanner
Chris - Led strips
Brecken
Mike -game programmer
Card - bit coin x - bit box
merlin
tarin
Monad
Rayc - wifi link to delores park
Rodie - science Guy
CYnthia -
Hilaire
Vaughn
Dan - Computational Neuroscience
Pidgeon
Amin - MM Prod
Melissa




[[Category:Meeting Notes]]
[[Category:Meeting Notes]]
Now that the meeting is over, don't forget to '''post the meeting notes to the wiki''' and e-mail the discussion list with a short summary.

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.