Meeting Notes 2015 12 08: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
Phong (talk | contribs)
Created new meeting page
 
Lxpk (talk | contribs)
No edit summary
Line 1: Line 1:
----------->8----------
These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]. Note-taker: Danukeru; Moderators: lxp.
DELETE EVERYTHING BELOW THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
* '''One or two bullet points of high-level meeting summary.'''


= Instructions =
8:30PM!
 
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 discusions, 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 ==
 
* Open a text editor to take notes on the major points of the meeting, using this page as the template.
* Project the meeting notes in real time throughout the meeting. Its super cool to use a collaborative editor such as pad.riseup.net or piratepad so that everyone is free to participate in the note taking.
* 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 the announcement and discussion list with a short summary.
* Tell treasurer@noisebridge.net and secretary@noisebridge.net if there are new members.
 
== 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.


= Introductions =


DELETE EVERYTHING ABOVE THIS LINE WHEN YOU POST THE MEETING MINUTES KTHX!!!
Steve: Noisebridge is a 501c3 since 2007. Teaches technical topics ot its visitors and members. Be your best self, follow your dreams and be excellent to each other. It is an extension on being 1337. You must also be excellent. Watch yo self before you noise yo self? He's Now out of energy
----------->8----------
Alex: Be cool. Seriously. Or be asked to leave..."nicely".


These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]. Note-taker: FIXME YOUR NAME HERE; Moderators: FIXME THEIR NAME HERE.
* '''One or two bullet points of high-level meeting summary.'''


= Introductions =
= Round of introductions (remember, announcements come later):
John: Met Alex at hackathon and got brainwashed. Likes VR and Unity. Building a grpahical programming language. Talk to him. He doesn't have a brother named Mark, but does have one named Theodore.
Frank: Works on RF SDR, but specifically high bandwith
Samir: Eating a burrito. COmes spo
Teopa: It's meeting time.
Steve: Theoreticla physicist and adata scientist.
Trave: Make games, and get paid. Likes 3D art.
Roger: Just fucks with the notes.
Dan: 3 years my senior at NB. Works on NN and NN concepts. Not propane. Neural Networks. Friend of the machines.
Chris: Student. Likes game dev and archtitecture.
Alex: Passionate about growin NB for a while now through gamedev, robotics, and SIGNAGE! IF YOU LIKE IT PUT A SIGN ON IT!
Trent: Python class organiser and web dev. Class  is out for December
Danukeru: I type things here today.


* '''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 =
* Cool new projects? Something you'd like people to know? Say now, but keep it short! One or two sentences please!
Teopa: [http://www.sparklecon.org/wiki/Main_Page SPARKLECON]! Google it...cba to type.
* Any happenings at the space of which members should be made aware.
Frank:  Next crypto challenge group is coming next Thursday.
* Don't hog everyone's time since we all just want to hack!


= [[ Membership Binder ]] =
= [[ Membership Binder ]] =
 
Alex: YUltimate way that NB stays open and stays awesome. Money -> Rent -> Fuel/Electricity -> Responsibility! There's also the power of blocking a concesnsus vote. (Dude does art in BG) DUDE IS DOING WALL ART! HE COULD DO IT IN PINK! Is that cool? If you don't think so you could block it. But first you must apply. Pop a slip from the binder, and find 2 sponsors who are form the memeber body. Sits there for 4 weeks before it can be reviwed for concensus on if they can be a member or not. If you're not cool, someone could block you from not becoming a member. So don't shit in the space.
* '''Invite a knowledgeable volunteer to describe''' [[membership]], and the application process.
The main reason is basically you love the space, and want to declare it your responsibility.
<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.


= [[Philanthropists]]=
= [[Philanthropists]]=
* '''Invite a knowledgeable member to describe''' [[Philanthropist/Pledge|Philantropy]], and the application process.
No, I don't remember. But I know I get 24hr access. I get to close up, and I cannot block in concensus items. All this for one easy payment of 79.99999999999999999999999999 a month. Or half of that.
* 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 =
Line 91: Line 43:
= Consensus and Discussion =
= Consensus and Discussion =


* '''invite a knowledgeable volunteer to give '''[[Consensus Process|a brief primer on consensus process]]
= New Member Crossexamination : Alex Peake
* It is important that everyone in attendance understands at least:
 
** Blocking with verbalized principled objections.
*Steve wants details regarding a missed payment.
** Why we use consensus over other approaches to decision making.
-Alex wanted to become a member to promote the space. He brought cash at the meeting that he would be approved. He gave to someone claiming they would take the cash on the space's behalf. However he now recogizes that he should have had received a receipt, meaning that only the treasurer could . The cash was dumped in the donation box (best guess). Peter corroborated the story, but Patrick had to abide by the rules to uphold the legal integrity of NoiseBridge as a charity. Kevin tried to convince Patrick to do otherwise, in addition to Alex being willing to add another 40$ donation on top of his repeated donation.
** How consensus isn't a legislative process
Patrick's refusal irked Alex, but he accepted the logic regarding the legal integrity of the hackerspace. Alex greatly respects Pattrick, and bares no ill will.
** Why consensus isn't applicable to some things like conflict resolution, resolution of time sinks, and the like.
 
*Trent asks what concensus is best used for?
- Best used to affect the most people in a positive way, should ussually only go to "c" concenssus
"C" concenssus should be for more serious aspects: Legal(questionable events), Financial(purchases), and maintaining the "Safe Space" though banning people.
Managing space resources that affect abslutely everyone.
 
*Trent asks what what Alex seeks in a new member.
Being able to judge safe people, he can then give out a token. He recommends philanthropy if he thinks that someone has pulled value from the space. For a member, he expects them to be trusted with the space long after he's gone, or stuck in another castle.
 
*Trent wants to know what he's done in the space.
Gamefication framework. Hackathon team organizer. Tactical corsets(pew pew). Code Hero. Teaches classes relating to gamedev, and this is ongoing. Did we mention he likes signs? Seriously...how can someone always have that much adhesive on hand?
 
He was once asked to stop sleeping on the couch. He understands now the effects from sensitivity of small group dynamics. He takes criticism much better now.
 
 
ALEX BLOCKS HAS NONE, SO NOISBRIDGE MEMBER IS HE. -Yoda


== [[ Consensus Items History | Proposals from last week ]] ==
== [[ Consensus Items History | Proposals from last week ]] ==
Line 107: Line 74:


If any important discussion happens, it should be happening after forward progress is made during consensus.
If any important discussion happens, it should be happening after forward progress is made during consensus.
Roger: Mattermost server Patrick put up is running. Go to chat.noisebridge.net/noisebridge to sign up for an account.
Alex: We've got a proposed 3D printer hack station enclosure design for signage and tools attached to peg board.
Paul: It would be better if the signs were less clear so the tools act as death traps. There can always be someone who thinks they understand the tool because they read the signage. Instructions should be about maintenance. I like the stuff Eric is making.
Alex: Yes this incorporates that.


= End of Meeting =
= 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]]
[[Category:Meeting Notes]]

Revision as of 22:30, 8 December 2015

These are the notes from the The XXXth Meeting of Noisebridge. Note-taker: Danukeru; Moderators: lxp.

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

8:30PM!

Introductions

Steve: Noisebridge is a 501c3 since 2007. Teaches technical topics ot its visitors and members. Be your best self, follow your dreams and be excellent to each other. It is an extension on being 1337. You must also be excellent. Watch yo self before you noise yo self? He's Now out of energy Alex: Be cool. Seriously. Or be asked to leave..."nicely".


= Round of introductions (remember, announcements come later): John: Met Alex at hackathon and got brainwashed. Likes VR and Unity. Building a grpahical programming language. Talk to him. He doesn't have a brother named Mark, but does have one named Theodore. Frank: Works on RF SDR, but specifically high bandwith Samir: Eating a burrito. COmes spo Teopa: It's meeting time. Steve: Theoreticla physicist and adata scientist. Trave: Make games, and get paid. Likes 3D art. Roger: Just fucks with the notes. Dan: 3 years my senior at NB. Works on NN and NN concepts. Not propane. Neural Networks. Friend of the machines. Chris: Student. Likes game dev and archtitecture. Alex: Passionate about growin NB for a while now through gamedev, robotics, and SIGNAGE! IF YOU LIKE IT PUT A SIGN ON IT! Trent: Python class organiser and web dev. Class is out for December Danukeru: I type things here today.


Short announcements and events

Teopa: SPARKLECON! Google it...cba to type. Frank: Next crypto challenge group is coming next Thursday.

Alex: YUltimate way that NB stays open and stays awesome. Money -> Rent -> Fuel/Electricity -> Responsibility! There's also the power of blocking a concesnsus vote. (Dude does art in BG) DUDE IS DOING WALL ART! HE COULD DO IT IN PINK! Is that cool? If you don't think so you could block it. But first you must apply. Pop a slip from the binder, and find 2 sponsors who are form the memeber body. Sits there for 4 weeks before it can be reviwed for concensus on if they can be a member or not. If you're not cool, someone could block you from not becoming a member. So don't shit in the space. The main reason is basically you love the space, and want to declare it your responsibility.

No, I don't remember. But I know I get 24hr access. I get to close up, and I cannot block in concensus items. All this for one easy payment of 79.99999999999999999999999999 a month. Or half of that.

Financial Report

Consensus and Discussion

= New Member Crossexamination : Alex Peake

  • Steve wants details regarding a missed payment.

-Alex wanted to become a member to promote the space. He brought cash at the meeting that he would be approved. He gave to someone claiming they would take the cash on the space's behalf. However he now recogizes that he should have had received a receipt, meaning that only the treasurer could . The cash was dumped in the donation box (best guess). Peter corroborated the story, but Patrick had to abide by the rules to uphold the legal integrity of NoiseBridge as a charity. Kevin tried to convince Patrick to do otherwise, in addition to Alex being willing to add another 40$ donation on top of his repeated donation. Patrick's refusal irked Alex, but he accepted the logic regarding the legal integrity of the hackerspace. Alex greatly respects Pattrick, and bares no ill will.

  • Trent asks what concensus is best used for?

- Best used to affect the most people in a positive way, should ussually only go to "c" concenssus "C" concenssus should be for more serious aspects: Legal(questionable events), Financial(purchases), and maintaining the "Safe Space" though banning people. Managing space resources that affect abslutely everyone.

  • Trent asks what what Alex seeks in a new member.

Being able to judge safe people, he can then give out a token. He recommends philanthropy if he thinks that someone has pulled value from the space. For a member, he expects them to be trusted with the space long after he's gone, or stuck in another castle.

  • Trent wants to know what he's done in the space.

Gamefication framework. Hackathon team organizer. Tactical corsets(pew pew). Code Hero. Teaches classes relating to gamedev, and this is ongoing. Did we mention he likes signs? Seriously...how can someone always have that much adhesive on hand?

He was once asked to stop sleeping on the couch. He understands now the effects from sensitivity of small group dynamics. He takes criticism much better now.


ALEX BLOCKS HAS NONE, SO NOISBRIDGE MEMBER IS HE. -Yoda

(Add any items which are consensed upon or someone has raised a principle objection for to the Consensus Items History page.)

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

Roger: Mattermost server Patrick put up is running. Go to chat.noisebridge.net/noisebridge to sign up for an account. Alex: We've got a proposed 3D printer hack station enclosure design for signage and tools attached to peg board. Paul: It would be better if the signs were less clear so the tools act as death traps. There can always be someone who thinks they understand the tool because they read the signage. Instructions should be about maintenance. I like the stuff Eric is making. Alex: Yes this incorporates that.

End of Meeting