Meeting Notes 2017 11 14 - Revision history

Patrickod: Reverted edits by Biz (talk) to last revision by 192.195.83.130

2017-11-16T21:00:02Z

Reverted edits by Biz (talk) to last revision by 192.195.83.130

← Older revision		Revision as of 14:00, 16 November 2017
Line 182:		Line 182:

	Patrick: Meetings every Saturday on this, so please come.		Patrick: Meetings every Saturday on this, so please come.

	~~[[File:Techshop.gif]]~~

Biz at 18:38, 16 November 2017

2017-11-16T18:38:35Z

← Older revision		Revision as of 11:38, 16 November 2017
Line 182:		Line 182:

	Patrick: Meetings every Saturday on this, so please come.		Patrick: Meetings every Saturday on this, so please come.

			[[File:Techshop.gif]]

192.195.83.130: /* Safe Space */

2017-11-15T05:36:12Z

Safe Space

← Older revision		Revision as of 22:36, 14 November 2017
Line 57:		Line 57:
	* Darryl - we want people to be as comfortable as possible in the space, so when topics or behavior in the space make people uncomfortable they are within their right to ask that it stop. This doesn't translate into topics being off-limits, it just means that you should be considerate both to those around you and also the people that you're with. If you're uncomfortable you can find someone at Noisebridge that you trust or mention it in the #space-guardians channel. If you're comfortable doing so you can also ask someone to leave.		* Darryl - we want people to be as comfortable as possible in the space, so when topics or behavior in the space make people uncomfortable they are within their right to ask that it stop. This doesn't translate into topics being off-limits, it just means that you should be considerate both to those around you and also the people that you're with. If you're uncomfortable you can find someone at Noisebridge that you trust or mention it in the #space-guardians channel. If you're comfortable doing so you can also ask someone to leave.
	* Lizzie - sometimes it's not easy or clear asking someone to leave and so you can ask one of the people with their hands raised to help you out.		* Lizzie - sometimes it's not easy or clear asking someone to leave and so you can ask one of the people with their hands raised to help you out.

	J		J

	Scotty		Scotty

	Darryl		Darryl

	Lizzie		Lizzie

	Zach		Zach

	Kevin		Kevin

	Ryan		Ryan

	Trent		Trent

192.195.83.130: /* Introductions */

2017-11-15T05:35:55Z

Introductions

192.195.83.130 at 05:34, 15 November 2017

2017-11-15T05:34:07Z

Show changes

Patrickod: Reverted edits by 中国 (talk) to last revision by Phong

2017-11-12T22:00:29Z

Reverted edits by 中国 (talk) to last revision by Phong

← Older revision		Revision as of 15:00, 12 November 2017
Line 1:		Line 1:
	~~[[File:屁股.jpg]]~~
	----------->8----------		----------->8----------
	DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!		DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!

中国 at 21:43, 12 November 2017

2017-11-12T21:43:47Z

← Older revision		Revision as of 14:43, 12 November 2017
Line 1:		Line 1:
			[[File:屁股.jpg]]
	----------->8----------		----------->8----------
	DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!		DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!

Phong: Created new meeting page

2017-11-08T22:17:26Z

Created new meeting page

New page

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

Meetings should be limited to an hour when possible. Shorter is fine, but avoid rushing.

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
# Take new notes
# 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.'''

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

← Older revision		Revision as of 22:35, 14 November 2017
Line 2:		Line 2:

	* '''Invite a knowledgeable volunteer to explain''' [[Noisebridge_Vision\|what Noisebridge is about]]:		* '''Invite a knowledgeable volunteer to explain''' [[Noisebridge_Vision\|what Noisebridge is about]]:

			Trent - An imaginary future from the past that people believe existed from 1995 to 2001

	<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>		<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.		* Introduce any experimental or unusual moderation techniques that may be using during the meeting like: direct responses, limited speaking time, orderless stack, &c.
Line 10:		Line 13:
	** if you are new: how did you hear about Noisebridge?		** if you are new: how did you hear about Noisebridge?

	Trent ~~- An imaginary~~ future ~~from the past that people believe existed from 1995 to 2001~~		Trent (he/him), Living in my cyber future by buying things/consumerism

	~~Trent (he/him), Living in my cyber future by buying things/consumerism~~
	Lizzie (she/her), Audio electronics and music and computer security		Lizzie (she/her), Audio electronics and music and computer security

	Darryl (they/them), Functional programming and laser stuff and teach laser stuff		Darryl (they/them), Functional programming and laser stuff and teach laser stuff

	J (he/she) - Kane from kung fu, roams earth, solves problems.		J (he/she) - Kane from kung fu, roams earth, solves problems.

	Paddy (he/him) - regular visitor.		Paddy (he/him) - regular visitor.

	Ryan (He/ElJefe)- does game dev, enjoys hanging out at Noisebridge		Ryan (He/ElJefe)- does game dev, enjoys hanging out at Noisebridge

	Marco (he) - building a search engine for (code learning?) resources		Marco (he) - building a search engine for (code learning?) resources

	Zach (he) - likes to build things, learn things, meet new people, and help out noisebridge (and move it if that's what's going on)		Zach (he) - likes to build things, learn things, meet new people, and help out noisebridge (and move it if that's what's going on)

	Rich (he) - likes to hack around, playing w/ an rpi currently. Making real things w/ hims programming knowledge		Rich (he) - likes to hack around, playing w/ an rpi currently. Making real things w/ hims programming knowledge

	Lucas - likes networking. Been here a few times before		Lucas - likes networking. Been here a few times before

	Kelly (she/her) - does infosec and 3d printing stuff.		Kelly (she/her) - does infosec and 3d printing stuff.

	Cole (he) - makes robots		Cole (he) - makes robots

	Kevin (they/them) - likes microcontroller stuff, is helping out w/ circuit hacking mondays		Kevin (they/them) - likes microcontroller stuff, is helping out w/ circuit hacking mondays

	Patrick (he/him) - fight computer security for a living		Patrick (he/him) - fight computer security for a living

	Scotty (he/him) - writing memory back to permanent storage. it's super great. He even remembers people.		Scotty (he/him) - writing memory back to permanent storage. it's super great. He even remembers people.


	= Short announcements and events =		= Short announcements and events =