Kalessin: more discussion notes

2015-03-18T03:14:22Z

more discussion notes

← Older revision		Revision as of 20:14, 17 March 2015
Line 66:		Line 66:
	* Steve & Louis: we think that the access control we have in place is one of the success of this reboot;		* Steve & Louis: we think that the access control we have in place is one of the success of this reboot;
	* Dan: I sympathize with Kevin's feelings, but giving the space hours helps bringing-in balance to it;		* Dan: I sympathize with Kevin's feelings, but giving the space hours helps bringing-in balance to it;
	* Mohammed: tell the people that get kicked out in the evening or who are stuck in the mornings to come at the meeting. Scheduling members who open and close the space is interesting because it makes you identify regulars.		* Mohammed: tell the people that get kicked out in the evening or who are stuck in the mornings to come at the meeting. Scheduling members who open and close the space is interesting because it makes you identify regulars;
			* Louis: I really like the concept of balance, I think closing and opening hours bring balance to the space; I also really like Mohammed idea of a schedule of people to open or close the space.

	= End of Meeting =		= End of Meeting =

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

Kalessin: most notes

2015-03-18T03:12:40Z

most notes

Show changes

Kalessin: create page before meeting

2015-03-18T02:05:28Z

create page before meeting

New page

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The 502nd Meeting of Noisebridge]. Note-taker: [[User:Kalessin | louis ]]; Moderators: FIXME THEIR NAME HERE.

* '''One or two bullet points of high-level meeting summary.'''

= 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!
* 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.
<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 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]]

Meeting Notes 2015 03 17 - Revision history

Kalessin: more discussion notes

Kalessin: most notes

Kalessin: create page before meeting