Noisebridge - User contributions [en]

Python Class Instructor Meeting 2018 01 23

2018-01-24T05:03:06Z

192.241.210.237: /* Attendees */

= Python Class Instructor Meeting 2018 01 23 =

= Next Meeting is scheduled for 2018 02 20, Tuesday, 7pm in Turing=

* Meeting Moderator: eenblam
* Note taker: also eenblam

== Attendees ==
* Lady Red
* Trent
* razzi
* eenblam

== New instructors added ==
None

== Discussion items for this week ==
Lady Red - I'm submitting a PyCon talk on controlling LEDs that I'd like to demo here first as a guest talk

Nick is going to focus on making an AI class (for a different time,) so he won't be working on Python Class in the immediate future.

==Schedule for next month==
* January 29 - sqlite3 (Razzi)
* February 5 - Algorithms (Elena)
* February 12 - Advanced Functions / Higher Order Functions (Jay?)
* February 19 - Flask (Ben)
* February 26 - Python + LEDs! (Lady Red)
* March 5 - tbd guest talk
* March 12 - tbd guest talk
* March 19 - Django! (Razzi)
* March 26 - Django! (Razzi?)
* April 22 - Django! (Razzi?)

== Things postponed for next meeting ==

== Actions for next week ==
# Pick a day to have guest talks concurrent with Razzi's Django classes (for all three weeks)
# Spend the last 20 minutes hacking on the repo to get it cleaned up (merge duplicate lessons, organize a bit better, etc.)
# Add the email template to the repo instructors folder
# Add the announcement checklist to the instructors folder
# Add a markdown file to instructors folder with both templates and instructions for how to use them.
# Add a markdown file for how to run/start your class - specifically donations for nb, who hasn't had a tour, brief info about nb (harassment pol. etc).

Wiki Upgrade

2017-12-24T07:16:33Z

192.241.210.237: /* Noisebridge Wiki Database Fixing w/ Kevin 2017.12.23 */

== Eternal Wiki Upgrade Quest ==

This is the beginning of the wiki upgrade page....

== Requirements ==

# https by letsencrypt
# debian 9
# no snowflakes, all our (known) devops culture at nb is ansible
# salt the passwords correctly

== Chosen Technologies ==

# Ansible
# Debian 9
# Caddy
# Letsencrypt / Certbot

== Ansible Roles ==

Noisebridge already has an ansible infrastructure repo, please join the Noisebridge github group and hack this: https://github.com/noisebridge/ansible/

# Certbot - https://github.com/geerlingguy/ansible-role-certbot
# Semantic Mediawiki - Mediawiki maintains some: https://phabricator.wikimedia.org/diffusion/1881/
## It may be useful to look at this one: https://github.com/yongxinL/ansible-mediawiki

== Database Hacking ==

We need to upgrade a really old version of mediawiki and will likely need to futz with the database.
# Migrate to postgresql?
## make a git repo to store migration sql and other sql used for massaging the database contents
# Delete old passwords (md5 with no salt) and expire all user passwords?
## Write/publish public sql script to clean up the production database for public publishing
# Clean the database of spam/cruft?
## publish these scripts to the same sql script repo

=== MediaWiki-Vagrant ===

This potentially is a good environment for testing and migrating the database: https://www.mediawiki.org/wiki/MediaWiki-Vagrant

(more OpenStack Semantic MediaWiki images: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS)

You'll need to follow this guide to get a dump of our database up and running: https://www.mediawiki.org/wiki/Manual:Moving_a_wiki

=== Password Rollover ===

Here is the mediawiki default user table data dictionary: https://www.mediawiki.org/wiki/Manual:User_table

We need to delete the password column and expire everyone's password. The old mediawiki only stores md5 hashed passwords with no salts, so we'll have to delete the whole thing

<code>
user_password_expires

MediaWiki version: ≥ 1.23

Date when user's password expires; null for no expiration date. Can also be set manually by calling User->expirePassword().

</code>

== Noisebridge Wiki Database Fixing w/ Kevin & Trent 2017.12.23 ==

This is a log of what we did to a local copy of Noisebridge wiki database. These changes were not propogated to the live/production Noisebridge MediaWiki instance.

=== Things We Deleted ===

## purged password hashes - noisebridge_mediawikiuser.user_password all set to '' (empty string)
### update <table> set <column>='';
## purged user emails - noisebridge_mediawikiuser.user_email all set to '' (empty string)
### update <table> set <column>='';

## purged noisebridge_mediawikiipblocks.ipb_address - replaced the composite primary key column with a sequence as follows: https://stackoverflow.com/questions/2643371/how-to-renumber-primary-index

## truncated user watchlists (these are private)
### truncate table noisebridge_mediawikiwatchlist;

## truncated all protected tables (these might give private info on who protected the page?)
### truncate table noisebridge_mediawikiprotected_titles;

=== Important How-tos and Gotchas ===
* MediaWiki upgrade for NB
** Follow directions for setting up local Vagrant instance on your development machine:
*** Install vagrant and virtualbox (OS X: http://sourabhbajaj.com/mac-setup/Vagrant/README.html)
*** $ cd vagrant
*** $ ./setup.sh
*** $ vagrant up
** How to copy files into virtualbox instance
*** Find your eth1 ip address:
**** $ /sbin/ifconfig # and remember that as MW_IP_ADDR
**** $ scp -i .vagrant/machines/default/virtualbox/private_key YOUR_FILE_HERE vagrant@MW_IP_ADDR:
** Noisebridge's MediaWiki database was configured with a tablename prefix of "noisebridge_mediawiki"
*** Change this in /vagrant/LocalSettings.php:
***: $wgDBprefix = "noisebridge_mediawiki";
** Use the default database name 'wiki' - do not be clever and configure a different name, because `wiki` is a baked-in default somewhere in vagrant's puppet scripts, or maybe in mediawiki's CLI scripts, but either way IT CANNOT BE OVERRIDDEN IN LocalSettings.php or DefaultSettings.php, or --conf, or the 'dbname-prefixname' CLI parameter
** You may need to drop and create the MySQL database 'wiki' to eliminate the default MediaWiki 1.31 structure, to avoid problems overwriting it with our old MW 1.19 schema mysqldump
:: $ mysql
:: > drop database wiki;
:: > create database wiki;
:: > ^D
:: $ mysql wiki < the-uncompressed-mysqldump-file-you-were-provided-with.sql
:: You may safely ignore messages like "Warning (Code 1300): Invalid utf8 character string: 'BD5A6D'"
** Now run the upgrade script:
:: $ cd /vagrant/mediawiki/maintenance/
:: $ mwscript update.php
:: If all goes as planned you'll see a bunch of advisory progress messages such as:
::: Your composer.lock file is up to date with current dependencies!
::: Going to run database updates for wiki-noisebridge_mediawiki
::: Depending on the size of your database this may take a while!
::: Abort with control-c in the next five seconds (skip this countdown with --quick) ... 0
::: Turning off Content Handler DB fields for this part of upgrade.
::: ...have ipb_id field in ipblocks table.
::: ...have ipb_expiry field in ipblocks table.
::: ...already have interwiki table
::: ...indexes seem up to 20031107 standards.
::: ...have rc_type field in recentchanges table.
::: ...index new_name_timestamp already set on recentchanges table.
::: ...have user_real_name field in user table.
::: ...
::: ...doing rev_id from 2001 to 2200
::: ...doing rev_id from 2201 to 2400
::: ...doing rev_id from 2401 to 2600
::: ...doing rev_id from 2601 to 2800
::: ...doing rev_id from 2801 to 3000
::: ...checking 40 revisions for IP edits that need copying, between rev_ids 20100 and 20300
::: ...checking 49 revisions for IP edits that need copying, between rev_ids 20301 and 20501
::: ...checking 74 revisions for IP edits that need copying, between rev_ids 20502 and 20702
::: ...checking 48 revisions for IP edits that need copying, between rev_ids 20703 and 20903
::: ...checking 41 revisions for IP edits that need copying, between rev_ids 20904 and 21104
::: ...et cetera.
** At this point you may be able to visit the Noisebridge site on your dev machine by going to:
:: http://127.0.0.1:8080/wiki/Noisebridge
** If this doesn't work it's likely some step was omitted from this doc, in which case ask Kevin or Trent for support.

=== FUTURE Database Hacking Plans ===

==== FUTURE ACTION: After Upgrading we can expire everyone's password ====

details here: https://noisebridge.net/wiki/Wiki_Upgrade
and here: https://www.mediawiki.org/wiki/Manual:User_table#user_password_expires

==== FUTURE ACTIONS ====

# reduce permissions for inactive moderators, admins, etc, to "user".
## really drop everyone and add current people back, to make it an intentional process
## be very restrictive about CURRENT active users

Wiki Upgrade

2017-12-24T04:02:58Z

192.241.210.237: added db hacking session

Wiki Upgrade

2017-12-24T02:34:36Z

192.241.210.237: added user table data dictionary

Meeting Notes 2017 10 24

2017-10-25T07:43:29Z

192.241.210.237: Clarified trent's "who am i" entry

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]. Date: 2017-10-24 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: (three applications are at 4 weeks but no one could attend!)
* New philanthropists: Kelly, Roy, Adrian, Kyle, Andrew, Elena

* Consensus Items: Establish an Elevator Repair Fund
* 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?

* Kelly - I do 3d printing and infosec stuff at NB
* Roy - Building stuff, learning about infosec and lockpicking
* Sebastian - pretty new to NB, into programming theory and math, introduced to nb by mitch to ask about nb fiscal sponsorship
* Jenn - From Chicago - things look amazing since I was here 2 years ago, I teach digital fabrication at The Museum Science and Industry in Chicago (a fablab)
* Dang - I haunt this place, I am an apparition. I enjoy long walks on the beach, complex systems, and scribbling illegibly in my notebook.
* Katherine - Wearables and working in the sewing area
* Chris - I am chris, I do stuff
* Trent - Started the current python class, developing python courses, and other stuff.
* Ryan - Noisebridge philanthropist, interested in just about everything, multidisciplinary specialist - love helping at nb and usually here every Tuesday for the unityversity gamebridge class.
* Will - 3D printing
* Joe - Playing with sensors
* Matt - I'm leaving, bye
* Daniel - breaks things in infosec
* Adrien - back after a year, 3D printer stuff, machine shop, starting a Fusion 360 class
* Travis - been here a few times before but not as much as I wanted to. Interested in programming python, js, web, interested in music for games.
* Mark - Been here before, working on robot, AI programming game, programming, circuits, robots
* Paddy - Always interested in learning about cool stuff.

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

* Adrian - Fusion 360 class coming up - CAD Design Class - Thursdays starting November 2nd. Approximately 7 PMish.
* Travis - Mark and I are going to work on halite - a programming competition for AI for games. Tonight, and whenever in the future. Competition runs until January at least.
* Mark - Annual bartending robot at DNA lounge. We want to give a heads up, it's in 9 months! Come ask us.

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

Ryan - Noisebridge a while back became what we consider a safe space, which is both an idea and implementation of beign a space that is both open to the communtiy but some place that people can come and feel safe no matter what opinions they may hold as long as they follow the rules of this place, people can come and relax or talk with someone. We have a sheet of people you can talk to if you are stressed out or emotional. We also have a safe space policy on the door. People can come here to feel safe no matter who they are as long as they can be excellent to each other. If you don't you can immediately bring it up with a person listed on the door or someone you know that comes around a lot and might know the protocol for dealing with when someone feel unsafe or uncomfortable.

Trent - Some opinions that some people hold might not be welcome here. The important thing is that Noisebridge used to be a place that was radically inclusive. But, by including some people, you exclude some people who are also worthwhile participants. Prejuduced people usually suck. Safe space analogy: woodshop -> loud instruments warning, tell them so they can protect hearing -- safe space is about warning people so they can prepare or leave a situation so they can feel safe. Side note: safe-space people on the door is not accurate anymore. We should replace it with something blank and have it be more accurate. Should do that today.

= 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

Dang - Everyone can participate at Noisebridge! You get an RFID tag by hanging out and proving you are most excellent. A member can give you an RFID tag. A philanthropist can renew you. To get access to slack, hang out and be excellent and you can ask for an invite in person.

= [[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(?)

Kelly - Philanthropy is a way for people to get 24 hour access to NB and contribute to the commuity with a monthly donation. A philanthropist doesn't participate fully in the consensus process (no blocking rights). You must put a paper in the binder and agree to the philanthropist pledge. Once you are confirmed in that meeting you are a philanthropist.

New Philanthropists:
- Kelly
- Roy
- Adrian
- Kyle
- Andrew
- Elena

* Trent - Any member can revoke someone's philanthropy. The revoked philanthropist can reapply.

= [[ 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.

Membership Applicants:
- Merlin (4 checkmarks) (More than that?!)
- Nichole (4 checkmarks)
- Lady Red (5 checkmarks)

Nick - A member is someone who wants to move the space forwards, the biggest thing is the ability to block consensus proposals. If you were to block something, it's more of a sign that we should continue to talk and deliberate about the item. It's like a steering group of sorts.

= 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

No details on the financial report this week (fill in later).

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

Roy - The idea of consensus is to get an outcome/proposal that everyone is comfortable with to move the space forwards to a better place. For small-c consensus, you might want to make a change to the space larger than one you would be comfortable making on your own. Big C Consensus is a more formal process, the exact nature of which is up for debate. My basic understanding is that a formal written proposal without changes between the two meetings has to come to two meetings and not be blocked. Must be posted on current consensus items and on the noisebridge-discuss mailing list. Once everyone is comfortable with it you can then consense on it.

== [[ 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.)''

Trent reading proposal from Zach - **Establish an Elevator Repair Fund** Establish a fund for repair and maintenance of the Noisebridge Elevator. The fund established and agreed upon should be a minimum of $400 per year drawn from the Noisebridge General Fund. The funds are to be used for 2 purposes: 1) To hire professional repair person(s) and 2) To pay for parts needed for the Elevator to be safe and 100% functional. The funds are not to be used to pay Noisebridge members who wish to do repairs.

Zach - 100% functionality is defined as: today we were fixing the call button to bring the elevator down to the lower level. While not necessary to move up and down the elevator, it is necessary for 100% functionality. Gate got jammed on the way up today. Zach knows how to fix it, but not everyone does. Defined as the gate works, 100% of the time, people don't get trapped.

Multiple discussion participants: we should strengthen the proposal by defining what "100% functional" means. What are the objective definitions?

Zach - From an electrical engineering background, 100% has a particular meaning. Would like to go to the tresurer and say "I need $35 for a lightbulb", seems unlikely that someone would block that.

Multiple discussion participants: Perhaps add a list of things on the Wiki that are expected to work?

Zach - What is there are intermittent issues that aren't captured by individual things on a list. Where is the line on a consensus proposal? Does this need to be proposed again from scratch as part of defining the "100% functional" term?

Ryan - One comment: I understand what electrically what 100% means, but I also understand that defining 100% is somewhat an issue. 100% of the time it works 60% of the time is not true 100%. Definitely think this is something that we can define over time. 100% for 100% of the time is probably impossible. Over time things wear down. I think 100% working should mean it should go where you want when you ask it to. We've had 10 major breakdowns in the past 2 years, if not more if you include smaller breakdowns. We get it to about 90% working order about 85% of the year. We do need the fund to improve.

Katherine - Trying to enumerate what counts as 100% is a bad idea, because it will be used to rule-lawyer. What's going to happen if there are 5 bullet points?

Kevin - There may be value in defining how the elevator works as a system on the wiki systematically.

Adrian - We're overthinking it!

Kevin - Context: elevator was out for 6 to 8 weeks. For some of our participants, it is their only way into the space. Imagine traveling from far away and not being able to get in at the gate. Part of a pattern of unconscious/inadvertent ableness, and we should be more cognizant of it. Important to have a consensus item to encourage discussion and stimulate efforts to improve things.

Trent - If we make changes to wording now, it doesn't slow down the consensus process for next week.

Zach - The way I think about 100% is if you take your car to a mechanic, if you've had a car, there are always little things. Cupholder rubber wears out. Fold-out cupholders wear out. Lightbulbs need replacement. Radio antenna needs replacement. Things in addition to alternator, transmission, etc., that's why I put in the word "maintenence" of the elevator. I want to prevent, as in the electrical repair community, do preventative maintenence. Spend a couple of dollars now. Save hundreds or thousands of dollars later. That's what I want to do with the elevator. That's what I was working on tonight, the call box and light. It "worked" but wiring was poor, close to shorting out, could have been a hazard. Don't want to turn people away from NB because the elevator is broken. Elevator is much more important to me because don't have an option anymore. As a result of the process, I've been building a Noisebridge Wiki page on the elevator. Took pictures. Sections on repairs and upgrades. Ways people can plug in and volunteer. I want to take a more active role, and the community is starting to see this as something that should be cared for. This is a step to removing a financial roadblock to working on this.

? - Perhaps instead of defining 100%, defer to the Wiki for operational optimum parameters.

Trent - Another way without invoking a specific document, instead of saying "safe and 100% functional", say "members of the community need to buy into and agree that the elevator is functional and safe".

Zach - Not trying to counter to be difficult, but that sounds like it might lead to requiring getting consensus to a consensed item. On deferring to a Wiki: that has an advantage of having a document/checklist, which should be relatively transparent. I will continue to work on it because I must. Darryl helped today with laser cutter skills that I don't have. I think it's a moot point, if there was something that was fuzzy, and I don't know what that would be (like an add-on?), and that was fuzzy? By definition that would make it not count. The community and treasurer would say "that's not required for the elevator to function" and that would be ok. Nobody wants a gate that gets jammed off the track. Nobody wants a callbox that doesn't work that's held up by masking tape with 100 live volts that they can shock themselves on.

Katherine - I think it's strage we're having this conversation at all. If the stairs caved in, we would just fix it. The elevator is broken, and people who give a lot to the space use it, and even if they don't, it should be accessible. If someone has a problem using NB money to fix the problem, that's wrong, and we should take care of each other. We go to great lengths to make this a safe space, let's make it a reliable space too. We have things that are janky, but we make them work. Let's make the elevator work, and it's strange we keep coming back to it and we should give money to this process.

Adrian - I definitely agree, this seems like a strange discussion. Clarifying question: in future, does using elevator money require big-C consensus to use it?

Zach - The think the way it works is I email the treasurer on the public noisebridge-discuss list, to say, I need $35 for elevator lights, send links, and everyone sees that. If someone has an objection, they make it. If not, John buys the part and mails it. The reason we do this with consensus now is so that's less necessary on a purchase-by-purchase basis.

Adrian - By going through the mailing list is less machinery than seeking consensus?

Zach - I'll try to answer this as best I can. Wish John was here, but he has another obligation. Don't want to put words in John's mouth: he keeps track of the money and where it is spent. When I buy $35 lightbulbs, it's $400 (fund size) - $35, and that shows up in public records. Reduce red-tape around the process. The way I see it, the elevator is broken a lot, and what usually happens (in the last 7 years), people say "oh, that kind of sucks", wait for the landlord or someone else's initiaive, and depending on how broken it is, controls how long it takes to get fixed. It's a long drawn out process. If the front door was broken, it would never happen. It would just be fixed. I want that kind of care/expiditeness for the elevator. By having a consensus item and discussion, it raises awareness that Noisebridge has this thing that needs work. Elevator is an ongoing project.

Darryl - The process around this shouldn't be much different from the equipment fund. The fact that there's any process around getting this, which is vital accessability equipment, is rediculous. If it's necessary, that's nonsense to discuss it.

Adrian - Whoever is repairing the elevator should be able to go buy what they need, right now, and know they will be reimbursed from the elevator fund.

Darryl - $400 a year is less than half of a philanthropist. We just added 6. We can accord a bunch of elevator fund.

Trent - If there's critical infrastructure that needs fixing, it can go through little-c consensus. Go to the treasurer. The process is not document.

Zach - There are some things about the elevator that are exception. That process is not well documented or well known. Initially went to Patrick because I thought he was still treasurer. A big question in this project is that it is the landlord's responsibility. Do we want for them? How do we (as a space) get reimbursed for it? Again, if this was the front door, I don't anticipate a long discussion. Someone would just go change the lock in an hour. It's reasonable to have the discussion and be concerned about this. I've had a lot of person-to-person conversations and tried a lot of avenues before bringing this up as a big-c consensus item. For people who haven't been in the space in recent weeks, especially on Tuesday, this might feel really out of the blue, and that's not the case, and that's been a huge part of my frustration with this entire process. This is something I have been championing since July. It would be great to publicize these (little-c) processes more, but the process isn't bulletproof either.

Trent - I told Zach this already: I do support this consensus proposal. The reason that the elevator took so long is because the elevator company physically locked the elevator, and they left it locked for 6 weeks. They finally came and "did the repair" where it was usable but unsafe when they unlocked it. There was some strangeness about locking/unlocking safe/unsasfe. Long talk with landlord, and were locked out by the elevator company for 6 weeks.

Kevin - How does the equipment fund balance get decided? What if the $400 vanishes, what then?

Zach - Can try to answer that: Part of why I chose $400 figure -- John was surprised it was low. Chosen very low on purpose. This is supposed to be a baby step. Challenges in process show how necessary it was to take a baby step. Chose a small dollar amount so that some amount of money set aside for the elevator is a good thing. If we agree it's a good thing, we can have another (hopefully easier) discussion should we need to expand. I'm down to take that through consensus. Let's just take a baby-step in that direction. Also, this is the first time I've heard about the elevator lockdown. On a larger note: I could not come to the space to continue learning some software, or come to a class. I was email and trying to talk to people to get updates. Was getting lots of vague messages. Sometimes heard elevator was partly working. If I take a bus and it isn't working, I turn around and go home. Had that happen. How do we handle dissemenation of this information, especially to members who need elevator access? All we had was an "elevator broken" sign, and sometimes it would go away, and that was infuriating. Many conditions require a lot of energy to be mobile, and get assistance to the space (para-transit). 1-3 days ahead to schedule a window. To find out it's broken after that is not a good way.

Kevin - I would like to return to how equipment fund is funded. How?

Trent - Equipment fund was a grant from Google with no strings attached. $15,000 once, and then another $15,000 on accident. Didn't want to spend it in case they wanted it back, but they said to deduct it from future invoices. No renewal process. Don't know how much is left. There's a wiki page which may (or may not) have information on it.

Adrian - ~$6000 left.

Kevin - Given ease of equipment fund allocation requests, how about adding verbiage to allow replenishing elevator fund from equipment fund?

Zach - That's probably a different consensus item.

Adrian - Get that written out formally as a separate consensus item.

Trent - We really do want to pass this next week.

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

Zach - A discussion on how consensus works at Noisebridge.
Trent - During the process of the elevator consensus item, people believed that this consensus item was passed at the meeting last week, but others felt that it hadn't reached consensus. This created a really big miscommunication due to people having different versions of the consensus process that was "the" way. In my view of what happened, we have a rich oral culture that breaks down when the wiki differs from the oral history. This lead to the situation being ripe for a miscommunication which, in my view, is what happened for this consensus item. This lead me to believe that we need a more conrete definition of what consensus is. Oral culture isn't going to cut it and we need a way that doesn't involve having to talk to every single person in the community.

Ryan - Has there ever been a proposal of making a large pre-discussion chat somewhere on consensus items.

Roy - There is a wiki page called "Current Consensus Items" and items can be sent out over the email list and a discussion there. There could also be a slack channel. I don't believe the proposal made it on the Current Consensus Items wiki page.

Adrian - It's good to get things on the wiki to have a record of how consensus works. But on the wiki you don't get notified when things change, and I don't check the wiki to see that things have changes. I agree that a slack channel would help.

Zach -

Travis - I have a question. Is it just me, or does it seem like the meeting notes haven't been going out to noisebridge-discuss.

Trent - unfortunately meetings haven't been happening every week.

Kevin - You can enable the setting on wikimedia to notify you of changes.

Adrian - there is a bias against people not using slack.

Zach - I want to talk about my view on how the process worked and my take away on it. Talking to people in person has been super helpful and made things way better. There's a few things I want to address. Firstly, does consensus require slack? I have been treated very differently as a noisebridge member for not using a program that is not used by noisebridge. This has influenced my ability to pass a consensus item. There is a huge divide between people who use Slack and those who do not. To try and follow the consensus, I read the consensus process wiki page and talked with many long time members. The consus process wiki page is marked do not edit and seems like a good regerence. I saw that this consensus process on the wiki process -- there was lots of discussions, lots of meetings about how people deliberately tried to manipulate the consensus process for shady ends. I think there is also a misunderstanding that we as a community have about how the consensus proces works. I started this as a little c consensus item and I asked J if I could start a consensus item and he suggested that I use little c consensus first. I waited two weeks and nothing had happened at all (keep in mind I started this in July). At the nest meeting, I said that I'd like to start a formal consensus process. Nobody at that meeting was super clear on how consensus works, partly since it's been so long that we're out of practice. We're trying to engage in a complicated process for which the rulebook is missing and we haven't practiced. So, even though I emailed the discuss with a formal proposal, answered many questions over email and in person, and although I did the best I could to make this an open proces, since I was not on slack, I was cut out of a separate set of discussion on slack about this process, so aside from a couple people who I worked with in process, there are apparently other discussions on Slack, but none of those people did not reach out to me and those disc
ussions happened exclusively on slack. My understanding is that consensus is coming to a meeting and bringing yourself and following the process. It says here on the wiki page, that a member must be physically present (or find a proxy to come for them) to block a proposal. A member who is physically not present is assenting to a consensus proposal. I have heard about "Quorum" and blocking without being present, but this isn't document anywhere.

Ryan - A big issue is just missed / locked out communication channels. I was wondering if there was a way to get slack shown a bit easier; maybe people people can see it, but not fully access it, or slack tells members who aren't here that they should check this, since we don't livestream this.

Daryl - if someone cares, they can read the meeting notes

Zach - When the consensus item is proposed, there is meeting notes for that. A lot of that makes sense, but I think part of the point Daryl was making is that Noisebridge has processes for informing the community of what is happening, but if people choose not to attend the meetings, not to read the meeting notes,

Ryan - It would be nice to notify people who are online of there being a new meeting and notes pad. The only reason that the proposal wasn't posted on the current consensus items wiki page was that no-one at the last three meetings mentioned it. I think having a physical copy of the consensus process in the space would be really helpful. I would love to hear from other people.

Trent - in the wiki page, and no-where that I can find, does it say that you must post the exact wording, but my understanding is that you must post the exact wording, so it's not clear if we have to do that.

Zack - [quotes wiki page on editing consensus items] It isn't clear what qualifies as a "radical" change.

Trent - I sent out what I thought was the consensus item text, but it apparently it was not.

Zack - I said that exact text (the current text), give or take a couple clauses, but it didn't get sent correctly. The changes that were made were not large changes, but the larger issue is that people did not attend the meeting.

Trent - I know what happened. The people who I talked to, since there was not a formal text, thought the proposal was not being formally consensed yet.

Zack - I think people need to come to meetings and read the meeting notes.

Adrian - I think it's important that the exact text of the consensus item needs to be posted. I shouldn't have to attend every meeting to know what's going on.

Zack - to think a formal consensus is not even happening, is just a matter of not paying attention. If you can alter it in the second meeting, what's the point of having the exact text.

Trent - the only canonical place we have is the meeting notes.

Roy - What about the consensus item wiki page.

Zack - I think it would help the community to have a big printout of exactly what the consensus process is. Lets cut out the unnecessary confusion, on the mailing list, on the wiki, and in the space, let's have physical signage in the space. For that to be even a little bit vague is really a problem.

Trent - can we say that we're agreeing we should do those things, and that, you can talk to Zack about more place through going that direction and talking to each other.

Zack - The 18 x N printer is SOOO shitty. That thing blows.

Trent - lets schedule an event to do that stuff.

Trent - You may not get any receipts if you don't have a meeting.

Adrian - does it require a consensus process to change / clarify the consensus process.

Zack - how is consensus notified to the community. Whose responsibility is it to notify the community. There should be clear verbiage on what the notification and consensus process is. Do people have objections to the current physically present at meeting part.

Trent - you can't just skate around and block it from Berlin. Also, there should be information on the process that tells the person trying to consense an item should make a good faith effort to reach out to members of the community.

Zack - we should define what reaching out is.

Trent - reaching out for me is sending email to people who are interested.

Zack - The only people who brought up issues with me were, in person, to Trent and John. I wish me and John had coordinated in person first, in hindsight. But I think that it's concerning that not more people were discussing with me.

Trent - for example, patrick pmed me saying that he agreed with me. I think people didn't want to pile on to this concern. There was a lot of back and forth and no-one wanted to pile on or interject.

Zack - I wish we could make the discussion m

Postponed Items:

Zach - How do we handle disseminating elevator information - clear process and signs, clear communication process
Zach - We could have more information about how to actually spend money on critical infrastructure at Noisebridge.
Kevin - How do we allocate more money to the elevator fund once depleted or in the future.

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

Meeting Notes 2017 10 24

2017-10-25T05:46:22Z

192.241.210.237: added raw notes

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge]. Date: 2017-10-24 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: (three applications are at 4 weeks but no one could attend!)
* New philanthropists: Kelly, Roy, Adrian, Kyle, Andrew, Elena

* Consensus Items: Establish an Elevator Repair Fund
* 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?

* Kelly - I do 3d printing and infosec stuff at NB
* Roy - Building stuff, learning about infosec and lockpicking
* Sebastian - pretty new to NB, into programming theory and math, introduced to nb by mitch to ask about nb fiscal sponsorship
* Jenn - From Chicago - things look amazing since I was here 2 years ago, I teach digital fabrication at The Museum Science and Industry in Chicago (a fablab)
* Dang - I haunt this place, I am an apparition. I enjoy long walks on the beach, complex systems, and scribbling illegibly in my notebook.
* Katherine - Wearables and working in the sewing area
* Chris - I am chris, I do stuff
* Trent - Started the python class, developing python courses, and other stuff.
* Ryan - Noisebridge philanthropist, interested in just about everything, multidisciplinary specialist - love helping at nb and usually here every Tuesday for the unityversity gamebridge class.
* Will - 3D printing
* Joe - Playing with sensors
* Matt - I'm leaving, bye
* Daniel - breaks things in infosec
* Adrien - back after a year, 3D printer stuff, machine shop, starting a Fusion 360 class
* Travis - been here a few times before but not as much as I wanted to. Interested in programming python, js, web, interested in music for games.
* Mark - Been here before, working on robot, AI programming game, programming, circuits, robots
* Paddy - Always interested in learning about cool stuff.

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

* Adrian - Fusion 360 class coming up - CAD Design Class - Thursdays starting November 2nd. Approximately 7 PMish.
* Travis - Mark and I are going to work on halite - a programming competition for AI for games. Tonight, and whenever in the future. Competition runs until January at least.
* Mark - Annual bartending robot at DNA lounge. We want to give a heads up, it's in 9 months! Come ask us.

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

Ryan - Noisebridge a while back became what we consider a safe space, which is both an idea and implementation of beign a space that is both open to the communtiy but some place that people can come and feel safe no matter what opinions they may hold as long as they follow the rules of this place, people can come and relax or talk with someone. We have a sheet of people you can talk to if you are stressed out or emotional. We also have a safe space policy on the door. People can come here to feel safe no matter who they are as long as they can be excellent to each other. If you don't you can immediately bring it up with a person listed on the door or someone you know that comes around a lot and might know the protocol for dealing with when someone feel unsafe or uncomfortable.

Trent - Some opinions that some people hold might not be welcome here. The important thing is that Noisebridge used to be a place that was radically inclusive. But, by including some people, you exclude some people who are also worthwhile participants. Prejuduced people usually suck. Safe space analogy: woodshop -> loud instruments warning, tell them so they can protect hearing -- safe space is about warning people so they can prepare or leave a situation so they can feel safe. Side note: safe-space people on the door is not accurate anymore. We should replace it with something blank and have it be more accurate. Should do that today.

= 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

Dang - Everyone can participate at Noisebridge! You get an RFID tag by hanging out and proving you are most excellent. A member can give you an RFID tag. A philanthropist can renew you. To get access to slack, hang out and be excellent and you can ask for an invite in person.

= [[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(?)

Kelly - Philanthropy is a way for people to get 24 hour access to NB and contribute to the commuity with a monthly donation. A philanthropist doesn't participate fully in the consensus process (no blocking rights). You must put a paper in the binder and agree to the philanthropist pledge. Once you are confirmed in that meeting you are a philanthropist.

New Philanthropists:
- Kelly
- Roy
- Adrian
- Kyle
- Andrew
- Elena

* Trent - Any member can revoke someone's philanthropy. The revoked philanthropist can reapply.

= [[ 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.

Membership Applicants:
- Merlin (4 checkmarks) (More than that?!)
- Nichole (4 checkmarks)
- Lady Red (5 checkmarks)

Nick - A member is someone who wants to move the space forwards, the biggest thing is the ability to block consensus proposals. If you were to block something, it's more of a sign that we should continue to talk and deliberate about the item. It's like a steering group of sorts.

= 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

No details on the financial report this week (fill in later).

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

Roy - The idea of consensus is to get an outcome/proposal that everyone is comfortable with to move the space forwards to a better place. For small-c consensus, you might want to make a change to the space larger than one you would be comfortable making on your own. Big C Consensus is a more formal process, the exact nature of which is up for debate. My basic understanding is that a formal written proposal without changes between the two meetings has to come to two meetings and not be blocked. Must be posted on current consensus items and on the noisebridge-discuss mailing list. Once everyone is comfortable with it you can then consense on it.

== [[ 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.)''

Trent reading proposal from Zach - **Establish an Elevator Repair Fund** Establish a fund for repair and maintenance of the Noisebridge Elevator. The fund established and agreed upon should be a minimum of $400 per year drawn from the Noisebridge General Fund. The funds are to be used for 2 purposes: 1) To hire professional repair person(s) and 2) To pay for parts needed for the Elevator to be safe and 100% functional. The funds are not to be used to pay Noisebridge members who wish to do repairs.

Zach - 100% functionality is defined as: today we were fixing the call button to bring the elevator down to the lower level. While not necessary to move up and down the elevator, it is necessary for 100% functionality. Gate got jammed on the way up today. Zach knows how to fix it, but not everyone does. Defined as the gate works, 100% of the time, people don't get trapped.

Multiple discussion participants: we should strengthen the proposal by defining what "100% functional" means. What are the objective definitions?

Zach - From an electrical engineering background, 100% has a particular meaning. Would like to go to the tresurer and say "I need $35 for a lightbulb", seems unlikely that someone would block that.

Multiple discussion participants: Perhaps add a list of things on the Wiki that are expected to work?

Zach - What is there are intermittent issues that aren't captured by individual things on a list. Where is the line on a consensus proposal? Does this need to be proposed again from scratch as part of defining the "100% functional" term?

Ryan - One comment: I understand what electrically what 100% means, but I also understand that defining 100% is somewhat an issue. 100% of the time it works 60% of the time is not true 100%. Definitely think this is something that we can define over time. 100% for 100% of the time is probably impossible. Over time things wear down. I think 100% working should mean it should go where you want when you ask it to. We've had 10 major breakdowns in the past 2 years, if not more if you include smaller breakdowns. We get it to about 90% working order about 85% of the year. We do need the fund to improve.

Katherine - Trying to enumerate what counts as 100% is a bad idea, because it will be used to rule-lawyer. What's going to happen if there are 5 bullet points?

Kevin - There may be value in defining how the elevator works as a system on the wiki systematically.

Adrian - We're overthinking it!

Kevin - Context: elevator was out for 6 to 8 weeks. For some of our participants, it is their only way into the space. Imagine traveling from far away and not being able to get in at the gate. Part of a pattern of unconscious/inadvertent ableness, and we should be more cognizant of it. Important to have a consensus item to encourage discussion and stimulate efforts to improve things.

Trent - If we make changes to wording now, it doesn't slow down the consensus process for next week.

Zach - The way I think about 100% is if you take your car to a mechanic, if you've had a car, there are always little things. Cupholder rubber wears out. Fold-out cupholders wear out. Lightbulbs need replacement. Radio antenna needs replacement. Things in addition to alternator, transmission, etc., that's why I put in the word "maintenence" of the elevator. I want to prevent, as in the electrical repair community, do preventative maintenence. Spend a couple of dollars now. Save hundreds or thousands of dollars later. That's what I want to do with the elevator. That's what I was working on tonight, the call box and light. It "worked" but wiring was poor, close to shorting out, could have been a hazard. Don't want to turn people away from NB because the elevator is broken. Elevator is much more important to me because don't have an option anymore. As a result of the process, I've been building a Noisebridge Wiki page on the elevator. Took pictures. Sections on repairs and upgrades. Ways people can plug in and volunteer. I want to take a more active role, and the community is starting to see this as something that should be cared for. This is a step to removing a financial roadblock to working on this.

? - Perhaps instead of defining 100%, defer to the Wiki for operational optimum parameters.

Trent - Another way without invoking a specific document, instead of saying "safe and 100% functional", say "members of the community need to buy into and agree that the elevator is functional and safe".

Zach - Not trying to counter to be difficult, but that sounds like it might lead to requiring getting consensus to a consensed item. On deferring to a Wiki: that has an advantage of having a document/checklist, which should be relatively transparent. I will continue to work on it because I must. Darryl helped today with laser cutter skills that I don't have. I think it's a moot point, if there was something that was fuzzy, and I don't know what that would be (like an add-on?), and that was fuzzy? By definition that would make it not count. The community and treasurer would say "that's not required for the elevator to function" and that would be ok. Nobody wants a gate that gets jammed off the track. Nobody wants a callbox that doesn't work that's held up by masking tape with 100 live volts that they can shock themselves on.

Katherine - I think it's strage we're having this conversation at all. If the stairs caved in, we would just fix it. The elevator is broken, and people who give a lot to the space use it, and even if they don't, it should be accessible. If someone has a problem using NB money to fix the problem, that's wrong, and we should take care of each other. We go to great lengths to make this a safe space, let's make it a reliable space too. We have things that are janky, but we make them work. Let's make the elevator work, and it's strange we keep coming back to it and we should give money to this process.

Adrian - I definitely agree, this seems like a strange discussion. Clarifying question: in future, does using elevator money require big-C consensus to use it?

Zach - The think the way it works is I email the treasurer on the public noisebridge-discuss list, to say, I need $35 for elevator lights, send links, and everyone sees that. If someone has an objection, they make it. If not, John buys the part and mails it. The reason we do this with consensus now is so that's less necessary on a purchase-by-purchase basis.

Adrian - By going through the mailing list is less machinery than seeking consensus?

Zach - I'll try to answer this as best I can. Wish John was here, but he has another obligation. Don't want to put words in John's mouth: he keeps track of the money and where it is spent. When I buy $35 lightbulbs, it's $400 (fund size) - $35, and that shows up in public records. Reduce red-tape around the process. The way I see it, the elevator is broken a lot, and what usually happens (in the last 7 years), people say "oh, that kind of sucks", wait for the landlord or someone else's initiaive, and depending on how broken it is, controls how long it takes to get fixed. It's a long drawn out process. If the front door was broken, it would never happen. It would just be fixed. I want that kind of care/expiditeness for the elevator. By having a consensus item and discussion, it raises awareness that Noisebridge has this thing that needs work. Elevator is an ongoing project.

Darryl - The process around this shouldn't be much different from the equipment fund. The fact that there's any process around getting this, which is vital accessability equipment, is rediculous. If it's necessary, that's nonsense to discuss it.

Adrian - Whoever is repairing the elevator should be able to go buy what they need, right now, and know they will be reimbursed from the elevator fund.

Darryl - $400 a year is less than half of a philanthropist. We just added 6. We can accord a bunch of elevator fund.

Trent - If there's critical infrastructure that needs fixing, it can go through little-c consensus. Go to the treasurer. The process is not document.

Zach - There are some things about the elevator that are exception. That process is not well documented or well known. Initially went to Patrick because I thought he was still treasurer. A big question in this project is that it is the landlord's responsibility. Do we want for them? How do we (as a space) get reimbursed for it? Again, if this was the front door, I don't anticipate a long discussion. Someone would just go change the lock in an hour. It's reasonable to have the discussion and be concerned about this. I've had a lot of person-to-person conversations and tried a lot of avenues before bringing this up as a big-c consensus item. For people who haven't been in the space in recent weeks, especially on Tuesday, this might feel really out of the blue, and that's not the case, and that's been a huge part of my frustration with this entire process. This is something I have been championing since July. It would be great to publicize these (little-c) processes more, but the process isn't bulletproof either.

Trent - I told Zach this already: I do support this consensus proposal. The reason that the elevator took so long is because the elevator company physically locked the elevator, and they left it locked for 6 weeks. They finally came and "did the repair" where it was usable but unsafe when they unlocked it. There was some strangeness about locking/unlocking safe/unsasfe. Long talk with landlord, and were locked out by the elevator company for 6 weeks.

Kevin - How does the equipment fund balance get decided? What if the $400 vanishes, what then?

Zach - Can try to answer that: Part of why I chose $400 figure -- John was surprised it was low. Chosen very low on purpose. This is supposed to be a baby step. Challenges in process show how necessary it was to take a baby step. Chose a small dollar amount so that some amount of money set aside for the elevator is a good thing. If we agree it's a good thing, we can have another (hopefully easier) discussion should we need to expand. I'm down to take that through consensus. Let's just take a baby-step in that direction. Also, this is the first time I've heard about the elevator lockdown. On a larger note: I could not come to the space to continue learning some software, or come to a class. I was email and trying to talk to people to get updates. Was getting lots of vague messages. Sometimes heard elevator was partly working. If I take a bus and it isn't working, I turn around and go home. Had that happen. How do we handle dissemenation of this information, especially to members who need elevator access? All we had was an "elevator broken" sign, and sometimes it would go away, and that was infuriating. Many conditions require a lot of energy to be mobile, and get assistance to the space (para-transit). 1-3 days ahead to schedule a window. To find out it's broken after that is not a good way.

Kevin - I would like to return to how equipment fund is funded. How?

Trent - Equipment fund was a grant from Google with no strings attached. $15,000 once, and then another $15,000 on accident. Didn't want to spend it in case they wanted it back, but they said to deduct it from future invoices. No renewal process. Don't know how much is left. There's a wiki page which may (or may not) have information on it.

Adrian - ~$6000 left.

Kevin - Given ease of equipment fund allocation requests, how about adding verbiage to allow replenishing elevator fund from equipment fund?

Zach - That's probably a different consensus item.

Adrian - Get that written out formally as a separate consensus item.

Trent - We really do want to pass this next week.

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

Zach - A discussion on how consensus works at Noisebridge.
Trent - During the process of the elevator consensus item, people believed that this consensus item was passed at the meeting last week, but others felt that it hadn't reached consensus. This created a really big miscommunication due to people having different versions of the consensus process that was "the" way. In my view of what happened, we have a rich oral culture that breaks down when the wiki differs from the oral history. This lead to the situation being ripe for a miscommunication which, in my view, is what happened for this consensus item. This lead me to believe that we need a more conrete definition of what consensus is. Oral culture isn't going to cut it and we need a way that doesn't involve having to talk to every single person in the community.

Ryan - Has there ever been a proposal of making a large pre-discussion chat somewhere on consensus items.

Roy - There is a wiki page called "Current Consensus Items" and items can be sent out over the email list and a discussion there. There could also be a slack channel. I don't believe the proposal made it on the Current Consensus Items wiki page.

Adrian - It's good to get things on the wiki to have a record of how consensus works. But on the wiki you don't get notified when things change, and I don't check the wiki to see that things have changes. I agree that a slack channel would help.

Zach -

Travis - I have a question. Is it just me, or does it seem like the meeting notes haven't been going out to noisebridge-discuss.

Trent - unfortunately meetings haven't been happening every week.

Kevin - You can enable the setting on wikimedia to notify you of changes.

Adrian - there is a bias against people not using slack.

Zach - I want to talk about my view on how the process worked and my take away on it. Talking to people in person has been super helpful and made things way better. There's a few things I want to address. Firstly, does consensus require slack? I have been treated very differently as a noisebridge member for not using a program that is not used by noisebridge. This has influenced my ability to pass a consensus item. There is a huge divide between people who use Slack and those who do not. To try and follow the consensus, I read the consensus process wiki page and talked with many long time members. The consus process wiki page is marked do not edit and seems like a good regerence. I saw that this consensus process on the wiki process -- there was lots of discussions, lots of meetings about how people deliberately tried to manipulate the consensus process for shady ends. I think there is also a misunderstanding that we as a community have about how the consensus proces works. I started this as a little c consensus item and I asked J if I could start a consensus item and he suggested that I use little c consensus first. I waited two weeks and nothing had happened at all (keep in mind I started this in July). At the nest meeting, I said that I'd like to start a formal consensus process. Nobody at that meeting was super clear on how consensus works, partly since it's been so long that we're out of practice. We're trying to engage in a complicated process for which the rulebook is missing and we haven't practiced. So, even though I emailed the discuss with a formal proposal, answered many questions over email and in person, and although I did the best I could to make this an open proces, since I was not on slack, I was cut out of a separate set of discussion on slack about this process, so aside from a couple people who I worked with in process, there are apparently other discussions on Slack, but none of those people did not reach out to me and those disc
ussions happened exclusively on slack. My understanding is that consensus is coming to a meeting and bringing yourself and following the process. It says here on the wiki page, that a member must be physically present (or find a proxy to come for them) to block a proposal. A member who is physically not present is assenting to a consensus proposal. I have heard about "Quorum" and blocking without being present, but this isn't document anywhere.

Ryan - A big issue is just missed / locked out communication channels. I was wondering if there was a way to get slack shown a bit easier; maybe people people can see it, but not fully access it, or slack tells members who aren't here that they should check this, since we don't livestream this.

Daryl - if someone cares, they can read the meeting notes

Zach - When the consensus item is proposed, there is meeting notes for that. A lot of that makes sense, but I think part of the point Daryl was making is that Noisebridge has processes for informing the community of what is happening, but if people choose not to attend the meetings, not to read the meeting notes,

Ryan - It would be nice to notify people who are online of there being a new meeting and notes pad. The only reason that the proposal wasn't posted on the current consensus items wiki page was that no-one at the last three meetings mentioned it. I think having a physical copy of the consensus process in the space would be really helpful. I would love to hear from other people.

Trent - in the wiki page, and no-where that I can find, does it say that you must post the exact wording, but my understanding is that you must post the exact wording, so it's not clear if we have to do that.

Zack - [quotes wiki page on editing consensus items] It isn't clear what qualifies as a "radical" change.

Trent - I sent out what I thought was the consensus item text, but it apparently it was not.

Zack - I said that exact text (the current text), give or take a couple clauses, but it didn't get sent correctly. The changes that were made were not large changes, but the larger issue is that people did not attend the meeting.

Trent - I know what happened. The people who I talked to, since there was not a formal text, thought the proposal was not being formally consensed yet.

Zack - I think people need to come to meetings and read the meeting notes.

Adrian - I think it's important that the exact text of the consensus item needs to be posted. I shouldn't have to attend every meeting to know what's going on.

Zack - to think a formal consensus is not even happening, is just a matter of not paying attention. If you can alter it in the second meeting, what's the point of having the exact text.

Trent - the only canonical place we have is the meeting notes.

Roy - What about the consensus item wiki page.

Zack - I think it would help the community to have a big printout of exactly what the consensus process is. Lets cut out the unnecessary confusion, on the mailing list, on the wiki, and in the space, let's have physical signage in the space. For that to be even a little bit vague is really a problem.

Trent - can we say that we're agreeing we should do those things, and that, you can talk to Zack about more place through going that direction and talking to each other.

Zack - The 18 x N printer is SOOO shitty. That thing blows.

Trent - lets schedule an event to do that stuff.

Trent - You may not get any receipts if you don't have a meeting.

Adrian - does it require a consensus process to change / clarify the consensus process.

Zack - how is consensus notified to the community. Whose responsibility is it to notify the community. There should be clear verbiage on what the notification and consensus process is. Do people have objections to the current physically present at meeting part.

Trent - you can't just skate around and block it from Berlin. Also, there should be information on the process that tells the person trying to consense an item should make a good faith effort to reach out to members of the community.

Zack - we should define what reaching out is.

Trent - reaching out for me is sending email to people who are interested.

Zack - The only people who brought up issues with me were, in person, to Trent and John. I wish me and John had coordinated in person first, in hindsight. But I think that it's concerning that not more people were discussing with me.

Trent - for example, patrick pmed me saying that he agreed with me. I think people didn't want to pile on to this concern. There was a lot of back and forth and no-one wanted to pile on or interject.

Zack - I wish we could make the discussion m

Postponed Items:

Zach - How do we handle disseminating elevator information - clear process and signs, clear communication process
Zach - We could have more information about how to actually spend money on critical infrastructure at Noisebridge.
Kevin - How do we allocate more money to the elevator fund once depleted or in the future.

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

Meeting Notes 2017 09 26

2017-09-27T15:52:22Z

192.241.210.237: /* Consensus */

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:

* Victoria: Noisebridge is an anarchist collective of hackers that sometimes thinks it is a spaceship. It's been here for coming up on 10 years. We operate on consensus, excellence, and doocracy, and various interpretations of those. We have one rule, "be excellent to each other". That includes taking care of the space, making sure the space is safe, watching who you let in, making sure the space is a place you want to be. You don't have to be a member, come use Noisebridge as long as you follow our one rule. It's everyone's space so love it like your own!

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

* Lady Red - I have these cubes
* Eradicate - Hates rats, sometimes talks to people, background in visual mechandising and fashion design. I am very creative and nice
* Dan - Go by dang on slack, enjoy farscape and movies and other stuff, lets chat
* Razzi - Love Noisebridge. Do a lot of programming, want to do sustainability projects and composting at noisebridge.
* Roy - Likes locks and their collection. Some amount of programming and dis/assembling stuff.
* Augur - Teach lasercutting stuff, might at some point teach a haskell class
* Ben - Likes math and programming, I don't know things about radios but trying to learn, DSP.
* Trent - I teach the python class, have too many interests and they get ahead of me
* Patrick - I do security things and am doing radio stuff at Noisebrige, putting a satellite tracker on the roof
* Jay - Enjoy Python. Going to help out with the Python class stuff. Radio stuff. Writing labels too.
* Nicole - Host coding workshops. I play with the laser cutter a lot. Propagating some succulents!
* Daniel - Infosec, would like to ressurect the cryptopals working group.
* Keita - make iOS apps. Every sunday, I organize "iOS Peer Lab" - if you want to be productive Sunday morning, join us. Also learning lockpicks. - wants to learn more about Rick and morty
* Diego - Musician - works at grey area. Well aligned with here, check grey area out. Also teaches people Ableton or Max MSP.
* Victoria - Time Travelling Prototype Cyborg from the Distant Present.
* J - Makes blinky lights.
* Marco - search engine for code learning resources, turn into awesome digital mentor. Background in design but doing more coding now.
* Nick - Also codes stuff.
* Andre - Blockchain company. I know how to code.
* Andre - Also blockchain company, both from ukraine, living in SF.

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

* Dan - Sundays - hack days. We livestream projects and things we are thinking about. We're a bunch of nerds that get together. Come share what you are passionate about.
* Dan - Wednesdays - Crypto builders meetup. First one tomorrow 730 PM.
* Nicole - If you want to teach a programming topic, let me know!
* Ben - If anyone wants to teach for PyClass, check in after.
* Patrick - Aaron Swartz Hackathon is coming up. It's awesome! https://www.aaronswartzday.org/sanfrancisco/
* Diego - Friday - Grey Area - Electronics Show, http://grayarea.org
* Trent - Python Class restarted - come join us for the 2nd course in the sequence next Monday at 7 PM in Church

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

* Victoria: Noisebridge is a safe space. Not necessarily that you aren't able to talk about stuff. We care about the safety of each other. You would tell someone if you were going to use a loud circular saw to protect their hearing. We do the same thing for psychological issues that might be triggering for some people. Give people warning so they can protect themselves. Be excellent to your fellow hackers, don't make people feel uncomfortable, don't make people feel unwelcome. Noisebridge is a safe space for everybody. Also, victoria covered some stuff about anti harrassment and how it can often be unwelcome to hit on someone. There is an anti-harrassment policy.

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

* Marco: Everyone can participate, everyone is welcome to participate because it is everyone's space. Be excellent to each other and be excellent to the space. If you want to change something and no one is against it, just do it.
Noisebridge is completely run by donations so if you would like to support the space, donations are highly welcomed. Some donate more, some less, it is what keeps Noisebridge running.
When you come here more often, and participate in the space, you can ask a member to get any RFID tag registered to open the door during normal open hours from 11 AM to 10 PM. You can also ask anyone to get invited to slack.

* Kate: When people come in it is a really good time to tell them that the space is run by donations.

= [[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(?)

* A philanthropist is someone who has invested a certain amount of themselves in the space, and wants to make that a recurring concrete thing. Also they agree to donate a certain amount of money to the space. Also they get an RFID for 24 hour access. Also taking more responsibility for the space and closing down the space. To become a philanthropist, get a copy of the philanthropist form and fill it out. Have at least one member sponsor you by signing it. The next meeting, it will be discussed, a member could stop someone from being a philanthropist. You then must set up recurring payment. Philanthropy can be taken away by a member, who can proxy for anyone with a reasonable concern.

= [[ 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.

* Patrick: Noisebridge is open participation but we have philanthropy so people can easily get access and the doors aren't completely closed and people can get in. But when Noisebridge wants to make a big choice like buying the building, we use a process called consensus. Membership is about stewardship. If you want to make sure this place exists in 5-10 years, you should become a member. Consensus discussions are open to everyone, but the group of people who are considered in that are members. If we could rename it, it would be better to call it stewardship.

* Jay: For all of us that have been around for awhile, we take membership very seriously. It's a building of a trust relationship. Ultimately you build a higher level of trust and commitment. It's because you actually want to be part of the space and make sure that it lives.

* Nicole (1st week) and Lady Red (2nd week) have membership applications in.

= 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

* pemulis (treasurer):

Mini-Financial Report: We have $86,131.30 in the bank. I can’t be bothered to do a full breakdown today. This is possibly the most money we’ve had in the bank at one time. We haven’t paid October rent yet.
Nope, I was wrong. We had a few hundred dollars more in the bank on August 17th. (edited)
Since that time we’ve subtracted a few thousand dollars from the equipment fund, broadcast fund, and Noisetor, which is a good thing. The difference was mostly made up by the growth of the general fund by a few thousand dollars.

Eyeballing this, we have about 9-1/2 months of regular expenses in the general fund. Rent’s gonna get paid soon and knock us down to a post-rent baseline of 8-1/2 months of regular expenses, which is a jump of 1/2 months of regular expenses from our post-rent baseline at the beginning of this month. (edited)
I’ll give a full breakdown after rent gets paid.

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

* Lady Red: Most of the things that happen here happen in a doocratic way. People take it upon themselves to organize the change, or be the change they want to see. But not before checking around and gathering momentum. The bigger the change the more people that need to be involved. This is doocracy. BUT EVERY ONCE IN AWHILE there is a really big change, that is about how we do things around here. For example, how we do membership. Recently we also got a fiscal sponsorship program off the ground to sponsor smaller groups that are not tax deductible organizations. A formal consensus is a consensus of the members. In voting, 51% of the people vote for it. In consensus, just no one has to block it, but anyone can block it.

* Victoria: Blocking is not procedural, you don't stand up and say I BLOCK THIS and move on and expect Noisebridge to just get over it. Blocking means you have a principled objection to the way the space is going. It means basically that you'd be leaving the organization if that goes forwards as planned. It's the groups duty to work with the person who is blocking. If you want to block a thing, think hard about. Compromise is a key point of consensus. It just takes one person to shit it up as a member.

* Patrick: If you want to block something, it's not acceptable to simply say no. You must propose a middle ground that is also acceptable people. If you just say "none of this should happen", it's going to be disregarded entirely, because there is no other path forwards. In membership applications, you can do it where your reason isn't publicly stated.

== [[ 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.

* Patrick also Jay - Event Proposal for next year.

* Patrick: A friend of Jay's has a touring hands-on Enigma machine workshop. They have a literal fucking Enigma machine. Hands-on travelling history tour. Often done as a corporate event, but want to do it at Noisebridge. What about payment? Godwaffle Noisepancakes does this but it's sort of grandfathered in, do they donate anything back to Noisebridge? Would Noisebridge be interested in hosting this and Noisebridge would get some money back. Yea nay (everyone wants to play with the machines).

* Victoria - I'm interested in talking about bike party and/or decorating bikes with LEDs.

* Victoria:
Bike Party! There is a new channel in slack: #bikeparty
East bay bike party second friday of october!
SF is the first Friday (of october)
End of the month - critical mass SF
Who wants to get together on a Friday or some other day and glue fuckin hot glue lights to your bike with led strips and shit?
::Everyone raises their hands::

* Victoria: bring a bunch of LEDs and shit for your bike next Friday, October 6th. I will bring a bunch of Teensy microcontrollers.
* Jay: I will take care of the meetup!!
* Ryan: Can we make a Noisebridge Flaschen-Taschen?
* Everyone: Thank you for volunteering.
* Victoria: Come to the thing and make it!!

* J - (partly representing some viewpoints Zach expressed and partly his own viewpoints)
Allocating funds for fixing things in the space. And that people that bought those things get compensated. Various people have fixed things out of their own pocket. Electrical, bathrooms, elevators. What about little c or BIG C consensus for a fund for this type of repairs for everyday repairs that happen within reason.
* Ben: This rolls into what John Shutt proposed on Slack.
* Patrick: Are we talking about paying people for time? I don't think we should reimburse people for labor. People have thrown cash peoples way for doing awesome stuff historically.
* J - I don't think this is about reimbursing people for their time, just for materials.
* Lady Red - It also lets you do a more complete job.
* Victoria - I think it's a good idea.
* Trent - I am also against the idea of paying people for their time.
* Katherine - I am against the idea of paying people but not against people being reimbursed within reason for what they spend.
* J - I think it is reasonable if we are considerate about the amount.
* Lady Red - Should we put 1% of our money in and it runs out or should it come out of the general fund?
* Victoria - The person with the best input is probably John.
* Victoria - I think we should pay people for their time.
* J - is this a big c or a little c?
* Patrick - Historically we just do it for materials they brought in. Is there a strong difference for the reboot pattern? Maybe it just hasn't been exercised recently? I think we should make that more clear to people.
* Victoria - For the sake of continuity, because I think John is looking to not be treasurer, we should get a written down process, even if it is what we do the reboot already. Having a process because oh my god do I hate arguing about money.
* Lady Red - That would be a substantial difference. We are in a situation in the sewing area where the equipment fund would buy a new machine but would not cover paying someone for fixing our current machine even if that's cheaper.
* Augur - maybe repairs should be part of the equiment fund as well.
* Patrick - I'm 99% we've reimbursed kyle for repair work that he got done on earlier machines.

* Ryan - Hacker Retreat

* Ryan - This is a process I do every couple months. My friends are constantly inundated with the chaos of the bay area, it can get to a lot of people. I grew up here and it can be insane. Whenever I get stressed out I head out for a couple days to retreat. I've gone on a retreat a couple hackers for a couple days and it's been helpful for people to take a break or reframe a problem they are trying to solve. What do people think about taking retreats to different places, like camping trips to different locations. There are a ton of places I know to retreat to. What do people think of a more formal hacker retreat?
* Victoria- Have you heard of toorcamp? https://toorcamp.toorcon.net/ June 20th-ISH next year.
* J - There's two channels - #hacker-trips and #fieldtrips -

* Razzi - The smell in the back - not enough airflow for the laser.

* Razzi - It's the burnt smell.
* Augur - Laser ventilation sucks.
* Victoria - I complained about it and someone said "it happens whenever the windows are open, so if you close the windows it stops coming in.
* Patrick - what about cheap monitoring equipment?
* Others - It's not gonna be cheap

* J - Buying the space

* J - Maybe we should all be thinking about if we are going to buy the space or go somewhere else or co-own another building?
Patrick - Our lease here goes through September 2018, the countdown has started.

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

Meeting Notes 2017 09 26

2017-09-27T15:51:53Z

192.241.210.237: /* Proposals for next week */

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:

* Victoria: Noisebridge is an anarchist collective of hackers that sometimes thinks it is a spaceship. It's been here for coming up on 10 years. We operate on consensus, excellence, and doocracy, and various interpretations of those. We have one rule, "be excellent to each other". That includes taking care of the space, making sure the space is safe, watching who you let in, making sure the space is a place you want to be. You don't have to be a member, come use Noisebridge as long as you follow our one rule. It's everyone's space so love it like your own!

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

* Lady Red - I have these cubes
* Eradicate - Hates rats, sometimes talks to people, background in visual mechandising and fashion design. I am very creative and nice
* Dan - Go by dang on slack, enjoy farscape and movies and other stuff, lets chat
* Razzi - Love Noisebridge. Do a lot of programming, want to do sustainability projects and composting at noisebridge.
* Roy - Likes locks and their collection. Some amount of programming and dis/assembling stuff.
* Augur - Teach lasercutting stuff, might at some point teach a haskell class
* Ben - Likes math and programming, I don't know things about radios but trying to learn, DSP.
* Trent - I teach the python class, have too many interests and they get ahead of me
* Patrick - I do security things and am doing radio stuff at Noisebrige, putting a satellite tracker on the roof
* Jay - Enjoy Python. Going to help out with the Python class stuff. Radio stuff. Writing labels too.
* Nicole - Host coding workshops. I play with the laser cutter a lot. Propagating some succulents!
* Daniel - Infosec, would like to ressurect the cryptopals working group.
* Keita - make iOS apps. Every sunday, I organize "iOS Peer Lab" - if you want to be productive Sunday morning, join us. Also learning lockpicks. - wants to learn more about Rick and morty
* Diego - Musician - works at grey area. Well aligned with here, check grey area out. Also teaches people Ableton or Max MSP.
* Victoria - Time Travelling Prototype Cyborg from the Distant Present.
* J - Makes blinky lights.
* Marco - search engine for code learning resources, turn into awesome digital mentor. Background in design but doing more coding now.
* Nick - Also codes stuff.
* Andre - Blockchain company. I know how to code.
* Andre - Also blockchain company, both from ukraine, living in SF.

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

* Dan - Sundays - hack days. We livestream projects and things we are thinking about. We're a bunch of nerds that get together. Come share what you are passionate about.
* Dan - Wednesdays - Crypto builders meetup. First one tomorrow 730 PM.
* Nicole - If you want to teach a programming topic, let me know!
* Ben - If anyone wants to teach for PyClass, check in after.
* Patrick - Aaron Swartz Hackathon is coming up. It's awesome! https://www.aaronswartzday.org/sanfrancisco/
* Diego - Friday - Grey Area - Electronics Show, http://grayarea.org
* Trent - Python Class restarted - come join us for the 2nd course in the sequence next Monday at 7 PM in Church

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

* Victoria: Noisebridge is a safe space. Not necessarily that you aren't able to talk about stuff. We care about the safety of each other. You would tell someone if you were going to use a loud circular saw to protect their hearing. We do the same thing for psychological issues that might be triggering for some people. Give people warning so they can protect themselves. Be excellent to your fellow hackers, don't make people feel uncomfortable, don't make people feel unwelcome. Noisebridge is a safe space for everybody. Also, victoria covered some stuff about anti harrassment and how it can often be unwelcome to hit on someone. There is an anti-harrassment policy.

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

* Marco: Everyone can participate, everyone is welcome to participate because it is everyone's space. Be excellent to each other and be excellent to the space. If you want to change something and no one is against it, just do it.
Noisebridge is completely run by donations so if you would like to support the space, donations are highly welcomed. Some donate more, some less, it is what keeps Noisebridge running.
When you come here more often, and participate in the space, you can ask a member to get any RFID tag registered to open the door during normal open hours from 11 AM to 10 PM. You can also ask anyone to get invited to slack.

* Kate: When people come in it is a really good time to tell them that the space is run by donations.

= [[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(?)

* A philanthropist is someone who has invested a certain amount of themselves in the space, and wants to make that a recurring concrete thing. Also they agree to donate a certain amount of money to the space. Also they get an RFID for 24 hour access. Also taking more responsibility for the space and closing down the space. To become a philanthropist, get a copy of the philanthropist form and fill it out. Have at least one member sponsor you by signing it. The next meeting, it will be discussed, a member could stop someone from being a philanthropist. You then must set up recurring payment. Philanthropy can be taken away by a member, who can proxy for anyone with a reasonable concern.

= [[ 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.

* Patrick: Noisebridge is open participation but we have philanthropy so people can easily get access and the doors aren't completely closed and people can get in. But when Noisebridge wants to make a big choice like buying the building, we use a process called consensus. Membership is about stewardship. If you want to make sure this place exists in 5-10 years, you should become a member. Consensus discussions are open to everyone, but the group of people who are considered in that are members. If we could rename it, it would be better to call it stewardship.

* Jay: For all of us that have been around for awhile, we take membership very seriously. It's a building of a trust relationship. Ultimately you build a higher level of trust and commitment. It's because you actually want to be part of the space and make sure that it lives.

* Nicole (1st week) and Lady Red (2nd week) have membership applications in.

= 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

* pemulis (treasurer):

Mini-Financial Report: We have $86,131.30 in the bank. I can’t be bothered to do a full breakdown today. This is possibly the most money we’ve had in the bank at one time. We haven’t paid October rent yet.
Nope, I was wrong. We had a few hundred dollars more in the bank on August 17th. (edited)
Since that time we’ve subtracted a few thousand dollars from the equipment fund, broadcast fund, and Noisetor, which is a good thing. The difference was mostly made up by the growth of the general fund by a few thousand dollars.

Eyeballing this, we have about 9-1/2 months of regular expenses in the general fund. Rent’s gonna get paid soon and knock us down to a post-rent baseline of 8-1/2 months of regular expenses, which is a jump of 1/2 months of regular expenses from our post-rent baseline at the beginning of this month. (edited)
I’ll give a full breakdown after rent gets paid.

= 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.)''

* Lady Red: Most of the things that happen here happen in a doocratic way. People take it upon themselves to organize the change, or be the change they want to see. But not before checking around and gathering momentum. The bigger the change the more people that need to be involved. This is doocracy. BUT EVERY ONCE IN AWHILE there is a really big change, that is about how we do things around here. For example, how we do membership. Recently we also got a fiscal sponsorship program off the ground to sponsor smaller groups that are not tax deductible organizations. A formal consensus is a consensus of the members. In voting, 51% of the people vote for it. In consensus, just no one has to block it, but anyone can block it.

* Victoria: Blocking is not procedural, you don't stand up and say I BLOCK THIS and move on and expect Noisebridge to just get over it. Blocking means you have a principled objection to the way the space is going. It means basically that you'd be leaving the organization if that goes forwards as planned. It's the groups duty to work with the person who is blocking. If you want to block a thing, think hard about. Compromise is a key point of consensus. It just takes one person to shit it up as a member.

* Patrick: If you want to block something, it's not acceptable to simply say no. You must propose a middle ground that is also acceptable people. If you just say "none of this should happen", it's going to be disregarded entirely, because there is no other path forwards. In membership applications, you can do it where your reason isn't publicly stated.

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

* Patrick also Jay - Event Proposal for next year.

* Patrick: A friend of Jay's has a touring hands-on Enigma machine workshop. They have a literal fucking Enigma machine. Hands-on travelling history tour. Often done as a corporate event, but want to do it at Noisebridge. What about payment? Godwaffle Noisepancakes does this but it's sort of grandfathered in, do they donate anything back to Noisebridge? Would Noisebridge be interested in hosting this and Noisebridge would get some money back. Yea nay (everyone wants to play with the machines).

* Victoria - I'm interested in talking about bike party and/or decorating bikes with LEDs.

* Victoria:
Bike Party! There is a new channel in slack: #bikeparty
East bay bike party second friday of october!
SF is the first Friday (of october)
End of the month - critical mass SF
Who wants to get together on a Friday or some other day and glue fuckin hot glue lights to your bike with led strips and shit?
::Everyone raises their hands::

* Victoria: bring a bunch of LEDs and shit for your bike next Friday, October 6th. I will bring a bunch of Teensy microcontrollers.
* Jay: I will take care of the meetup!!
* Ryan: Can we make a Noisebridge Flaschen-Taschen?
* Everyone: Thank you for volunteering.
* Victoria: Come to the thing and make it!!

* J - (partly representing some viewpoints Zach expressed and partly his own viewpoints)
Allocating funds for fixing things in the space. And that people that bought those things get compensated. Various people have fixed things out of their own pocket. Electrical, bathrooms, elevators. What about little c or BIG C consensus for a fund for this type of repairs for everyday repairs that happen within reason.
* Ben: This rolls into what John Shutt proposed on Slack.
* Patrick: Are we talking about paying people for time? I don't think we should reimburse people for labor. People have thrown cash peoples way for doing awesome stuff historically.
* J - I don't think this is about reimbursing people for their time, just for materials.
* Lady Red - It also lets you do a more complete job.
* Victoria - I think it's a good idea.
* Trent - I am also against the idea of paying people for their time.
* Katherine - I am against the idea of paying people but not against people being reimbursed within reason for what they spend.
* J - I think it is reasonable if we are considerate about the amount.
* Lady Red - Should we put 1% of our money in and it runs out or should it come out of the general fund?
* Victoria - The person with the best input is probably John.
* Victoria - I think we should pay people for their time.
* J - is this a big c or a little c?
* Patrick - Historically we just do it for materials they brought in. Is there a strong difference for the reboot pattern? Maybe it just hasn't been exercised recently? I think we should make that more clear to people.
* Victoria - For the sake of continuity, because I think John is looking to not be treasurer, we should get a written down process, even if it is what we do the reboot already. Having a process because oh my god do I hate arguing about money.
* Lady Red - That would be a substantial difference. We are in a situation in the sewing area where the equipment fund would buy a new machine but would not cover paying someone for fixing our current machine even if that's cheaper.
* Augur - maybe repairs should be part of the equiment fund as well.
* Patrick - I'm 99% we've reimbursed kyle for repair work that he got done on earlier machines.

* Ryan - Hacker Retreat

* Ryan - This is a process I do every couple months. My friends are constantly inundated with the chaos of the bay area, it can get to a lot of people. I grew up here and it can be insane. Whenever I get stressed out I head out for a couple days to retreat. I've gone on a retreat a couple hackers for a couple days and it's been helpful for people to take a break or reframe a problem they are trying to solve. What do people think about taking retreats to different places, like camping trips to different locations. There are a ton of places I know to retreat to. What do people think of a more formal hacker retreat?
* Victoria- Have you heard of toorcamp? https://toorcamp.toorcon.net/ June 20th-ISH next year.
* J - There's two channels - #hacker-trips and #fieldtrips -

* Razzi - The smell in the back - not enough airflow for the laser.

* Razzi - It's the burnt smell.
* Augur - Laser ventilation sucks.
* Victoria - I complained about it and someone said "it happens whenever the windows are open, so if you close the windows it stops coming in.
* Patrick - what about cheap monitoring equipment?
* Others - It's not gonna be cheap

* J - Buying the space

* J - Maybe we should all be thinking about if we are going to buy the space or go somewhere else or co-own another building?
Patrick - Our lease here goes through September 2018, the countdown has started.

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

Meeting Notes 2017 09 26

2017-09-27T15:51:37Z

192.241.210.237: /* Proposals for next week */

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:

* Victoria: Noisebridge is an anarchist collective of hackers that sometimes thinks it is a spaceship. It's been here for coming up on 10 years. We operate on consensus, excellence, and doocracy, and various interpretations of those. We have one rule, "be excellent to each other". That includes taking care of the space, making sure the space is safe, watching who you let in, making sure the space is a place you want to be. You don't have to be a member, come use Noisebridge as long as you follow our one rule. It's everyone's space so love it like your own!

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

* Lady Red - I have these cubes
* Eradicate - Hates rats, sometimes talks to people, background in visual mechandising and fashion design. I am very creative and nice
* Dan - Go by dang on slack, enjoy farscape and movies and other stuff, lets chat
* Razzi - Love Noisebridge. Do a lot of programming, want to do sustainability projects and composting at noisebridge.
* Roy - Likes locks and their collection. Some amount of programming and dis/assembling stuff.
* Augur - Teach lasercutting stuff, might at some point teach a haskell class
* Ben - Likes math and programming, I don't know things about radios but trying to learn, DSP.
* Trent - I teach the python class, have too many interests and they get ahead of me
* Patrick - I do security things and am doing radio stuff at Noisebrige, putting a satellite tracker on the roof
* Jay - Enjoy Python. Going to help out with the Python class stuff. Radio stuff. Writing labels too.
* Nicole - Host coding workshops. I play with the laser cutter a lot. Propagating some succulents!
* Daniel - Infosec, would like to ressurect the cryptopals working group.
* Keita - make iOS apps. Every sunday, I organize "iOS Peer Lab" - if you want to be productive Sunday morning, join us. Also learning lockpicks. - wants to learn more about Rick and morty
* Diego - Musician - works at grey area. Well aligned with here, check grey area out. Also teaches people Ableton or Max MSP.
* Victoria - Time Travelling Prototype Cyborg from the Distant Present.
* J - Makes blinky lights.
* Marco - search engine for code learning resources, turn into awesome digital mentor. Background in design but doing more coding now.
* Nick - Also codes stuff.
* Andre - Blockchain company. I know how to code.
* Andre - Also blockchain company, both from ukraine, living in SF.

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

* Dan - Sundays - hack days. We livestream projects and things we are thinking about. We're a bunch of nerds that get together. Come share what you are passionate about.
* Dan - Wednesdays - Crypto builders meetup. First one tomorrow 730 PM.
* Nicole - If you want to teach a programming topic, let me know!
* Ben - If anyone wants to teach for PyClass, check in after.
* Patrick - Aaron Swartz Hackathon is coming up. It's awesome! https://www.aaronswartzday.org/sanfrancisco/
* Diego - Friday - Grey Area - Electronics Show, http://grayarea.org
* Trent - Python Class restarted - come join us for the 2nd course in the sequence next Monday at 7 PM in Church

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

* Victoria: Noisebridge is a safe space. Not necessarily that you aren't able to talk about stuff. We care about the safety of each other. You would tell someone if you were going to use a loud circular saw to protect their hearing. We do the same thing for psychological issues that might be triggering for some people. Give people warning so they can protect themselves. Be excellent to your fellow hackers, don't make people feel uncomfortable, don't make people feel unwelcome. Noisebridge is a safe space for everybody. Also, victoria covered some stuff about anti harrassment and how it can often be unwelcome to hit on someone. There is an anti-harrassment policy.

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

* Marco: Everyone can participate, everyone is welcome to participate because it is everyone's space. Be excellent to each other and be excellent to the space. If you want to change something and no one is against it, just do it.
Noisebridge is completely run by donations so if you would like to support the space, donations are highly welcomed. Some donate more, some less, it is what keeps Noisebridge running.
When you come here more often, and participate in the space, you can ask a member to get any RFID tag registered to open the door during normal open hours from 11 AM to 10 PM. You can also ask anyone to get invited to slack.

* Kate: When people come in it is a really good time to tell them that the space is run by donations.

= [[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(?)

* A philanthropist is someone who has invested a certain amount of themselves in the space, and wants to make that a recurring concrete thing. Also they agree to donate a certain amount of money to the space. Also they get an RFID for 24 hour access. Also taking more responsibility for the space and closing down the space. To become a philanthropist, get a copy of the philanthropist form and fill it out. Have at least one member sponsor you by signing it. The next meeting, it will be discussed, a member could stop someone from being a philanthropist. You then must set up recurring payment. Philanthropy can be taken away by a member, who can proxy for anyone with a reasonable concern.

= [[ 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.

* Patrick: Noisebridge is open participation but we have philanthropy so people can easily get access and the doors aren't completely closed and people can get in. But when Noisebridge wants to make a big choice like buying the building, we use a process called consensus. Membership is about stewardship. If you want to make sure this place exists in 5-10 years, you should become a member. Consensus discussions are open to everyone, but the group of people who are considered in that are members. If we could rename it, it would be better to call it stewardship.

* Jay: For all of us that have been around for awhile, we take membership very seriously. It's a building of a trust relationship. Ultimately you build a higher level of trust and commitment. It's because you actually want to be part of the space and make sure that it lives.

* Nicole (1st week) and Lady Red (2nd week) have membership applications in.

= 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

* pemulis (treasurer):

Mini-Financial Report: We have $86,131.30 in the bank. I can’t be bothered to do a full breakdown today. This is possibly the most money we’ve had in the bank at one time. We haven’t paid October rent yet.
Nope, I was wrong. We had a few hundred dollars more in the bank on August 17th. (edited)
Since that time we’ve subtracted a few thousand dollars from the equipment fund, broadcast fund, and Noisetor, which is a good thing. The difference was mostly made up by the growth of the general fund by a few thousand dollars.

Eyeballing this, we have about 9-1/2 months of regular expenses in the general fund. Rent’s gonna get paid soon and knock us down to a post-rent baseline of 8-1/2 months of regular expenses, which is a jump of 1/2 months of regular expenses from our post-rent baseline at the beginning of this month. (edited)
I’ll give a full breakdown after rent gets paid.

= 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.)''

* Lady Red:

* Most of the things that happen here happen in a doocratic way. People take it upon themselves to organize the change, or be the change they want to see. But not before checking around and gathering momentum. The bigger the change the more people that need to be involved. This is doocracy. BUT EVERY ONCE IN AWHILE there is a really big change, that is about how we do things around here. For example, how we do membership. Recently we also got a fiscal sponsorship program off the ground to sponsor smaller groups that are not tax deductible organizations. A formal consensus is a consensus of the members. In voting, 51% of the people vote for it. In consensus, just no one has to block it, but anyone can block it.

* Victoria: Blocking is not procedural, you don't stand up and say I BLOCK THIS and move on and expect Noisebridge to just get over it. Blocking means you have a principled objection to the way the space is going. It means basically that you'd be leaving the organization if that goes forwards as planned. It's the groups duty to work with the person who is blocking. If you want to block a thing, think hard about. Compromise is a key point of consensus. It just takes one person to shit it up as a member.

* Patrick: If you want to block something, it's not acceptable to simply say no. You must propose a middle ground that is also acceptable people. If you just say "none of this should happen", it's going to be disregarded entirely, because there is no other path forwards. In membership applications, you can do it where your reason isn't publicly stated.

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

* Patrick also Jay - Event Proposal for next year.

* Patrick: A friend of Jay's has a touring hands-on Enigma machine workshop. They have a literal fucking Enigma machine. Hands-on travelling history tour. Often done as a corporate event, but want to do it at Noisebridge. What about payment? Godwaffle Noisepancakes does this but it's sort of grandfathered in, do they donate anything back to Noisebridge? Would Noisebridge be interested in hosting this and Noisebridge would get some money back. Yea nay (everyone wants to play with the machines).

* Victoria - I'm interested in talking about bike party and/or decorating bikes with LEDs.

* Victoria:
Bike Party! There is a new channel in slack: #bikeparty
East bay bike party second friday of october!
SF is the first Friday (of october)
End of the month - critical mass SF
Who wants to get together on a Friday or some other day and glue fuckin hot glue lights to your bike with led strips and shit?
::Everyone raises their hands::

* Victoria: bring a bunch of LEDs and shit for your bike next Friday, October 6th. I will bring a bunch of Teensy microcontrollers.
* Jay: I will take care of the meetup!!
* Ryan: Can we make a Noisebridge Flaschen-Taschen?
* Everyone: Thank you for volunteering.
* Victoria: Come to the thing and make it!!

* J - (partly representing some viewpoints Zach expressed and partly his own viewpoints)
Allocating funds for fixing things in the space. And that people that bought those things get compensated. Various people have fixed things out of their own pocket. Electrical, bathrooms, elevators. What about little c or BIG C consensus for a fund for this type of repairs for everyday repairs that happen within reason.
* Ben: This rolls into what John Shutt proposed on Slack.
* Patrick: Are we talking about paying people for time? I don't think we should reimburse people for labor. People have thrown cash peoples way for doing awesome stuff historically.
* J - I don't think this is about reimbursing people for their time, just for materials.
* Lady Red - It also lets you do a more complete job.
* Victoria - I think it's a good idea.
* Trent - I am also against the idea of paying people for their time.
* Katherine - I am against the idea of paying people but not against people being reimbursed within reason for what they spend.
* J - I think it is reasonable if we are considerate about the amount.
* Lady Red - Should we put 1% of our money in and it runs out or should it come out of the general fund?
* Victoria - The person with the best input is probably John.
* Victoria - I think we should pay people for their time.
* J - is this a big c or a little c?
* Patrick - Historically we just do it for materials they brought in. Is there a strong difference for the reboot pattern? Maybe it just hasn't been exercised recently? I think we should make that more clear to people.
* Victoria - For the sake of continuity, because I think John is looking to not be treasurer, we should get a written down process, even if it is what we do the reboot already. Having a process because oh my god do I hate arguing about money.
* Lady Red - That would be a substantial difference. We are in a situation in the sewing area where the equipment fund would buy a new machine but would not cover paying someone for fixing our current machine even if that's cheaper.
* Augur - maybe repairs should be part of the equiment fund as well.
* Patrick - I'm 99% we've reimbursed kyle for repair work that he got done on earlier machines.

* Ryan - Hacker Retreat

* Ryan - This is a process I do every couple months. My friends are constantly inundated with the chaos of the bay area, it can get to a lot of people. I grew up here and it can be insane. Whenever I get stressed out I head out for a couple days to retreat. I've gone on a retreat a couple hackers for a couple days and it's been helpful for people to take a break or reframe a problem they are trying to solve. What do people think about taking retreats to different places, like camping trips to different locations. There are a ton of places I know to retreat to. What do people think of a more formal hacker retreat?
* Victoria- Have you heard of toorcamp? https://toorcamp.toorcon.net/ June 20th-ISH next year.
* J - There's two channels - #hacker-trips and #fieldtrips -

* Razzi - The smell in the back - not enough airflow for the laser.

* Razzi - It's the burnt smell.
* Augur - Laser ventilation sucks.
* Victoria - I complained about it and someone said "it happens whenever the windows are open, so if you close the windows it stops coming in.
* Patrick - what about cheap monitoring equipment?
* Others - It's not gonna be cheap

* J - Buying the space

* J - Maybe we should all be thinking about if we are going to buy the space or go somewhere else or co-own another building?
Patrick - Our lease here goes through September 2018, the countdown has started.

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

Meeting Notes 2017 09 26

2017-09-27T05:33:45Z

192.241.210.237: added notes

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:

Victoria: Noisebridge is an anarchist collective of hackers that sometimes thinks it is a spaceship. It's been here for coming up on 10 years. We operate on consensus, excellence, and doocracy, and various interpretations of those. We have one rule, "be excellent to each other". That includes taking care of the space, making sure the space is safe, watching who you let in, making sure the space is a place you want to be. You don't have to be a member, come use Noisebridge as long as you follow our one rule. It's everyone's space so love it like your own!

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

Lady Red - I have these cubes
Eradicate - Hates rats, sometimes talks to people, background in visual mechandising and fashion design. I am very creative and nice
Dan - Go by dang on slack, enjoy farscape and movies and other stuff, lets chat
Razzi - Love Noisebridge. Do a lot of programming, want to do sustainability projects and composting at noisebridge.
Roy - Likes locks and their collection. Some amount of programming and dis/assembling stuff.
Augur - Teach lasercutting stuff, might at some point teach a haskell class
Ben - Likes math and programming, I don't know things about radios but trying to learn, DSP.
Trent - I teach the python class, have too many interests and they get ahead of me
Patrick - I do security things and am doing radio stuff at Noisebrige, putting a satellite tracker on the roof
Jay - Enjoy Python. Going to help out with the Python class stuff. Radio stuff. Writing labels too.
Nicole - Host coding workshops. I play with the laser cutter a lot. Propagating some succulents!
Daniel - Infosec, would like to ressurect the cryptopals working group.
Keita - make iOS apps. Every sunday, I organize "iOS Peer Lab" - if you want to be productive Sunday morning, join us. Also learning lockpicks. - wants to learn more about Rick and morty
Diego - Musician - works at grey area. Well aligned with here, check grey area out. Also teaches people Ableton or Max MSP.
Victoria - Time Travelling Prototype Cyborg from the Distant Present.
J - Makes blinky lights.
Marco - search engine for code learning resources, turn into awesome digital mentor. Background in design but doing more coding now.
Nick - Also codes stuff.
Andre - Blockchain company. I know how to code.
Andre - Also blockchain company, both from ukraine, living in SF.

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

Dan - Sundays - hack days. We livestream projects and things we are thinking about. We're a bunch of nerds that get together. Come share what you are passionate about.
Dan - Wednesdays - Crypto builders meetup. First one tomorrow 730 PM.
Nicole - If you want to teach a programming topic, let me know!
Ben - If anyone wants to teach for PyClass, check in after.
Patrick - Aaron Swartz Hackathon is coming up. It's awesome! https://www.aaronswartzday.org/sanfrancisco/
Diego - Friday - Grey Area - Electronics Show, http://grayarea.org
Trent - Python Class restarted - come join us for the 2nd course in the sequence next Monday at 7 PM in Church

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

Victoria: Noisebridge is a safe space. Not necessarily that you aren't able to talk about stuff. We care about the safety of each other. You would tell someone if you were going to use a loud circular saw to protect their hearing. We do the same thing for psychological issues that might be triggering for some people. Give people warning so they can protect themselves. Be excellent to your fellow hackers, don't make people feel uncomfortable, don't make people feel unwelcome. Noisebridge is a safe space for everybody. Also, victoria covered some stuff about anti harrassment and how it can often be unwelcome to hit on someone. There is an anti-harrassment policy.

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

Marco:
Everyone can participate, everyone is welcome to participate because it is everyone's space. Be excellent to each other and be excellent to the space. If you want to change something and no one is against it, just do it.
Noisebridge is completely run by donations so if you would like to support the space, donations are highly welcomed. Some donate more, some less, it is what keeps Noisebridge running.
When you come here more often, and participate in the space, you can ask a member to get any RFID tag registered to open the door during normal open hours from 11 AM to 10 PM. You can also ask anyone to get invited to slack.

Kate:
When people come in it is a really good time to tell them that the space is run by donations.

= [[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(?)

A philanthropist is someone who has invested a certain amount of themselves in the space, and wants to make that a recurring concrete thing. Also they agree to donate a certain amount of money to the space. Also they get an RFID for 24 hour access. Also taking more responsibility for the space and closing down the space. To become a philanthropist, get a copy of the philanthropist form and fill it out. Have at least one member sponsor you by signing it. The next meeting, it will be discussed, a member could stop someone from being a philanthropist. You then must set up recurring payment. Philanthropy can be taken away by a member, who can proxy for anyone with a reasonable concern.

= [[ 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.

Patrick: Noisebridge is open participation but we have philanthropy so people can easily get access and the doors aren't completely closed and people can get in. But when Noisebridge wants to make a big choice like buying the building, we use a process called consensus. Membership is about stewardship. If you want to make sure this place exists in 5-10 years, you should become a member. Consensus discussions are open to everyone, but the group of people who are considered in that are members. If we could rename it, it would be better to call it stewardship.

Jay: For all of us that have been around for awhile, we take membership very seriously. It's a building of a trust relationship. Ultimately you build a higher level of trust and commitment. It's because you actually want to be part of the space and make sure that it lives.

Nicole (1st week) and Lady Red (2nd week) have membership applications in.

= 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

pemulis (treasurer):

Mini-Financial Report: We have $86,131.30 in the bank. I can’t be bothered to do a full breakdown today. This is possibly the most money we’ve had in the bank at one time. We haven’t paid October rent yet.
Nope, I was wrong. We had a few hundred dollars more in the bank on August 17th. (edited)
Since that time we’ve subtracted a few thousand dollars from the equipment fund, broadcast fund, and Noisetor, which is a good thing. The difference was mostly made up by the growth of the general fund by a few thousand dollars.

Eyeballing this, we have about 9-1/2 months of regular expenses in the general fund. Rent’s gonna get paid soon and knock us down to a post-rent baseline of 8-1/2 months of regular expenses, which is a jump of 1/2 months of regular expenses from our post-rent baseline at the beginning of this month. (edited)
I’ll give a full breakdown after rent gets paid.

= 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.)''

Lady Red:

Most of the things that happen here happen in a doocratic way. People take it upon themselves to organize the change, or be the change they want to see. But not before checking around and gathering momentum. The bigger the change the more people that need to be involved. This is doocracy. BUT EVERY ONCE IN AWHILE there is a really big change, that is about how we do things around here. For example, how we do membership. Recently we also got a fiscal sponsorship program off the ground to sponsor smaller groups that are not tax deductible organizations. A formal consensus is a consensus of the members. In voting, 51% of the people vote for it. In consensus, just no one has to block it, but anyone can block it.

Victoria: Blocking is not procedural, you don't stand up and say I BLOCK THIS and move on and expect Noisebridge to just get over it. Blocking means you have a principled objection to the way the space is going. It means basically that you'd be leaving the organization if that goes forwards as planned. It's the groups duty to work with the person who is blocking. If you want to block a thing, think hard about. Compromise is a key point of consensus. It just takes one person to shit it up as a member.

Patrick: If you want to block something, it's not acceptable to simply say no. You must propose a middle ground that is also acceptable people. If you just say "none of this should happen", it's going to be disregarded entirely, because there is no other path forwards. In membership applications, you can do it where your reason isn't publicly stated.

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

Patrick also Jay - Event Proposal for next year.

Patrick: A friend of Jay's has a touring hands-on Enigma machine workshop. They have a literal fucking Enigma machine. Hands-on travelling history tour. Often done as a corporate event, but want to do it at Noisebridge. What about payment? Godwaffle Noisepancakes does this but it's sort of grandfathered in, do they donate anything back to Noisebridge? Would Noisebridge be interested in hosting this and Noisebridge would get some money back. Yea nay (everyone wants to play with the machines).

Victoria - I'm interested in talking about bike party and/or decorating bikes with LEDs.

Victoria:
Bike Party! There is a new channel in slack: #bikeparty
East bay bike party second friday of october!
SF is the first Friday (of october)
End of the month - critical mass SF
Who wants to get together on a Friday or some other day and glue fuckin hot glue lights to your bike with led strips and shit?
::Everyone raises their hands::

Victoria: bring a bunch of LEDs and shit for your bike next Friday, October 6th. I will bring a bunch of Teensy microcontrollers.
Jay: I will take care of the meetup!!
Ryan: Can we make a Noisebridge Flaschen-Taschen?
Everyone: Thank you for volunteering.
Victoria: Come to the thing and make it!!

J - (partly representing some viewpoints Zach expressed and partly his own viewpoints)
Allocating funds for fixing things in the space. And that people that bought those things get compensated. Various people have fixed things out of their own pocket. Electrical, bathrooms, elevators. What about little c or BIG C consensus for a fund for this type of repairs for everyday repairs that happen within reason.
Ben: This rolls into what John Shutt proposed on Slack.
Patrick: Are we talking about paying people for time? I don't think we should reimburse people for labor. People have thrown cash peoples way for doing awesome stuff historically.
J - I don't think this is about reimbursing people for their time, just for materials.
Lady Red - It also lets you do a more complete job.
Victoria - I think it's a good idea.
Trent - I am also against the idea of paying people for their time.
Katherine - I am against the idea of paying people but not against people being reimbursed within reason for what they spend.
J - I think it is reasonable if we are considerate about the amount.
Lady Red - Should we put 1% of our money in and it runs out or should it come out of the general fund?
Victoria - The person with the best input is probably John.
Victoria - I think we should pay people for their time.
J - is this a big c or a little c?
Patrick - Historically we just do it for materials they brought in. Is there a strong difference for the reboot pattern? Maybe it just hasn't been exercised recently? I think we should make that more clear to people.
Victoria - For the sake of continuity, because I think John is looking to not be treasurer, we should get a written down process, even if it is what we do the reboot already. Having a process because oh my god do I hate arguing about money.
Lady Red - That would be a substantial difference. We are in a situation in the sewing area where the equipment fund would buy a new machine but would not cover paying someone for fixing our current machine even if that's cheaper.
Augur - maybe repairs should be part of the equiment fund as well.
Patrick - I'm 99% we've reimbursed kyle for repair work that he got done on earlier machines.

Ryan - Hacker Retreat

Ryan - This is a process I do every couple months. My friends are constantly inundated with the chaos of the bay area, it can get to a lot of people. I grew up here and it can be insane. Whenever I get stressed out I head out for a couple days to retreat. I've gone on a retreat a couple hackers for a couple days and it's been helpful for people to take a break or reframe a problem they are trying to solve. What do people think about taking retreats to different places, like camping trips to different locations. There are a ton of places I know to retreat to. What do people think of a more formal hacker retreat?
Victoria- Have you heard of toorcamp? https://toorcamp.toorcon.net/ June 20th-ISH next year.
J - There's two channels - #hacker-trips and #fieldtrips -

Razzi - The smell in the back - not enough airflow for the laser.

Razzi - It's the burnt smell.
Augur - Laser ventilation sucks.
Victoria - I complained about it and someone said "it happens whenever the windows are open, so if you close the windows it stops coming in.
Patrick - what about cheap monitoring equipment?
Others - It's not gonna be cheap

J - Buying the space

J - Maybe we should all be thinking about if we are going to buy the space or go somewhere else or co-own another building?
Patrick - Our lease here goes through September 2018, the countdown has started.

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

Donations

2017-08-27T01:38:07Z

192.241.210.237: /* Donations We DONT Want */

Noisebridge loves donations! But we don't love all donations. We can't use everything, and some things take up lots of space and/or cost us lots of money to get rid of. Which results in Noisebridge being poorer than if we never got the donation in the firstplace.

Also, if you donate a resource and do not guide its use, then it is possible that it may get turned into a ROBOT. Yes, a ROBOT: a lifeless husk of wood and plastic.

= How to Donate to Noisebridge =

# Check to see if what you'd like to donate is listed below as something we definitely don't want. If we don't want it, please don't bring it to Noisebridge. We won't change our mind, we promise.
# If it's something that's big, and you have any doubt that we might want it, send an email to noisebridge-discuss@lists.noisebridge.net before you plan to bring it in, and we can give you a sense of whether we'd like it or not. Ask for Zach if you do not get a reply.
# Bring it in! You can leave your donation near the hackershelves down the hall (opposite the Sparkle Forge). There is a table there currently with old test gear underneath, leaving your donation on top is a good spot. But please, make sure it is something we can actually use (hint: if it is 30+ of some debug or single-purpose item, we probably don't want it).
# Ask a NB voluteer to write down what you donated, and your name+address, and email it to treasurer@noisebridge.net (if you are interested in tax write-offs).
# Our awesome treasurer emails them a PDF receipt. NOTE: We can't provide valuation information on the receipt. The receipt will simply list the items you donated and it's up to you to provide a value if you want to claim a charitable donation for tax purposes.

= Donations We DONT Want =

'''Beige:''' a good general rule is we don't want beige-colored stuff. This stuff is usually pre-2002 or older. "''if its beige it stays (with you)''"
 
'''Monitors We Don't Want:''' 
* CRT Monitors (Cathode Ray Tube large glass cube-shaped old TVs)- we do not want CRTs '''unless they are broadcast or highly specialized monitors''' i.e. the Sony PVM and BVM professional broadcast monitors. There are some specialty CRTs that will do unique inputs and resolutions that were '''not''' sold to consumers. So please, don't bring grandmas old 80s Zenith.

Why? CRTs are large, put out a lot of heat, and are difficult to dispose of. We can't accept donations of CRTs unless they're very special-purpose, because e-waste disposal of CRTs is very expensive in California. The exception is for unique devices, for example the slow-scan CRT in the [[SEM]] or the vector CRT in an old arcade stand-up console. A special-purpose but uninteresting CRT, like from a commercial security system, would probably not qualify. A very small full-color CRT (9" or less) would be OK though (Zach is looking for one of these to hack) 
* LCD Monitors: If it is 22" or less we don't want it, sorry. These smaller ones show up everywhere nowadays and we have a lot. We also '''do not want broken, cracked, or badly scratched LCDs'''. The parts inside really aren't that useful. LCDs that are working and >20" we will take. Ones smaller than 12" are welcome as well.
 
'''Computers We Don't Want:''' 
* PCs older than Intel Core 2 Duo (around 2006). The easiest way to tell is if your computer has a "Windows XP" sticker. That means it is too old. We only want Vista, Win 7, Win 8, and Win 10 era machines. 
* Apple computers that are pre-Intel (around 2005, i.e. G4 towers or older). If your OS X was 10.5 or older, that means we don't want it (Power PC) If it is Snow Leopard or newer (10.6) we want it. 
The same goes for all laptops. Windows XP sticker laptops we don't want.
Why? XP is the last hurrah for the single-core Pentium 4 series. These were power hungry beasts, and cannot utilize much RAM either. They are very limited by today's standards and even refurbishing them will not save them from being obsolete.
Power PC Apple computers (pre-2005) are no longer compatible with almost every piece of software there is. Apple killed off that generation by making browsers and sites like Youtube unusable as well as many other things.
 
This all applies to laptops as well.
 
'''Batteries We Don't Want:'''
* Car Batteries
* Lead-Acid batteries that have been sitting around for >6 months without charging (they are dead now) or measure <9VDC
* Ni-MH batteries that are more than 2 years old and have not been charged.
* Ni-CD batteries that are more than 2 years old and have not been charged.
* Coin Cell batteries that are >5 years old.
* Lithium Ion Batteries that are >5 years old (see computer section above for IDing your computers age for laptop batteries).

As you can tell there is a pattern here: we don't want old, dead batteries. If you have working, charged, attended to batteries we will take them. Some will last in a drawer and some will not, thus the year difference. 

'''Other Things We Don't Want:''' 
* Printers: almost all inkjet printers are worthless to us (no, we don't care about the motors). They are on every sidewalk in SF, and many are sold brand-new for <$50 nowadays. If you have a '''nice, working''' laser printer or very new (in the last year or two) working inkjet printer, we will take that. Or if you have a specialty printer that prints 11x17 or other special formats we can make posters with, we will accept that happily. But we get lots of regular beige or janky pre-2012 broken or ink-less printers that are of no use. Please recycle these elsewhere. 
* Scanners: Not very useful for parts and most All-in-one printers have a scanner, and you can find these are super easy to come by.
* Servers: Sometimes people leave their companies old XP servers or server gear (power supplies and stuff). Please, don't do that, we don't want it. Please see the computers we don't want section above. 
* Vintage Test Equipment: Sorry, we don't want grandpa's old workbench supply from the 1970s. We don't want anything from the 80s either. If you have nice, working, made in the last 20 years equipment then we will most likely take that. Even some broken stuff we will take if it is useful to our hacking area and we don't have it already.
* Busted Speakers: We don't want busted, cracked, punctured speakers. The magnets are not that interesting to us hackers and these take up a lot of space.
* Old Router and Ethernet Gear: We get a LOT of this stuff. We don't want wireless G routers and ethernet switches from <2006. Maybe if you have a super cool industrial one we can use it. But generally these collect dust for years. No switches that are not gigabit.
* Boxes of Ethernet Cable: Don't need it.
* Plumbing Supplies, Electrical outlets, and general construction odds and ends: We don't even have a section for these and it is not useful to us.
* Broken Power Tools: i.e. bad chucks, bad motor, bad motor brushes. We will take tools missing a battery or charger, but we don't need more broken power tools in the space.
* Most Appliances" Please check before donating! These take up a lot of space and are not often hacked.

= Donations We DO Want =

* Development Boards
* PCs and Apple Computers post-2006 (Intel Core2 or Intel-based Macbook Pro (or G5s and newer)
* High Quality Desk Chairs (100% working ONLY)
* Laptop Chargers (especially Apple kind "magsafe" of any type)
* Industrial Tools (Air Compressor, Drils, etc - size appropriate) - please check to make sure someone can receive very large bench tools
* Non-Industrial Tools (working DeWalt drills, Dremel (need one really bad), electric screwdrivers, etc).
* SMD Rework tools of any kind
* Electronic components (organized parts IC bins, LEDs, breadboard, organized resistors, etc).
* Soldering Tools (solder, soldering irons, hot glue guns, tweezers, magnifiers, etc).
* Bluetooth Stuff (Headphones, Speakers, Boomboxes, etc).
* Audio Gear (nice professional amps - broken or not - studio headphones, mics, etc.)
* Awesome, funky old things (live old tube-amplifiers and 1940s or earlier vintage stuff!)
* Robots / Drones / Helicopter toys
* Motors
* ????? Put stuff you want here
* Bulk Hex or Square Bolts with matching nuts of various sizes.
* Bulk Dupont Plastic Connector Female, especially single connetors for Raspberry Pi use.

= Processing Donations =

# Check the black donations table in the hackitorium next to the elevator gate for incoming donations, and/ or around the hackershelves area (in the hall opposite the sink):
## Hack shelf and component donations on the donation shelves below the turing classroom window, to the left of the hack shelves.
## Sewing supplies: ???
## Books: Books MUST be added to the library-org electronic catalog before being shelved. Please see the signs in the library for instructions or check out the [[library]] wiki page.
## Other: Store it in the area would we use it.
## Clothes, etc.: Mission street is a 24 hour salvation army.
# When we have sufficient hack shelf/component donations that need processing, a small group of people meet on Thursday nights at 7pm to go through the donations together.

== How to Handle Common Things We Receive ==

=== PCs ===

Keep anything intact that has a Core 2 Duo (or equivalent) or newer. Anything older should be E-wasted or used for parts if possible. We generally keep memory (DDR2 or DDR3), power supplies, PCI cards, and drives, and E-Waste the rest (Computer Case). PCs, even with some parts removed, can be used to pay ewaste recyclers for taking the rest of our crap.

=== Monitors ===

We don't want CRTs - they're large, put out a lot of heat, and are difficult to dispose of.

LCD monitors should be tested to see if they're working, and then labeled with a piece of a tape and a sharpie with the date they were tested, and whether they work or not. Also checked for obvious scratches and made note of.

=== Commodity Appliances ===

Examples: scanners, printers, ice makers, coffee machines, etc.

Unless it has obvious direct utility in the space (and we don't already have a better one), then we generally Don't want these. If they are already in the space and there is motivation, someone can take these apart for parts/useful subsystems for people to use in projects. Usually only a few parts or subsystems are of any use, which make up a small fraction of the overall bulk of the appliance. The rest is E-wasted.

The goal of this wiki page in part is to cut down a lot on unnecessary E-Waste and keep NB sorted with good, useful donations.

= E-Waste disposal =

If 4 computers are amongst things we're recycling, they'll take the rest for free. We keep a rack of computers we don't want by the elevator to pay them with.

There are people that we've used in the past here: https://noisebridge.net/wiki/Resources/House_Keeping#E-waste [TODO: not sure how up to date this is]

Things Mary Says

2017-07-04T01:57:20Z

192.241.210.237:

mic test, 1, 2, 3, testing, testing. mic check, one and two.

flush the toilet and wash ye hands, ya filthy animal

just a spoon full of sugar makes the medicine go down

I was born in the alternate reality where javascript was invented

covfefe did 9 11

Shall, we, play, a, game?

Raise you hands and say yeah- lets donate to noisebridge

A spectre is haunting Europe — the spectre of noisebridge

If you are hungry there are plenty of fruit flies fucking everywhere

Knife club assemble.

To donate $5 dollars press Ctrl+Alt+Del now! Teh 1,000 person will win ONE MILLION DOLL HAIRS!!!

There is plenty of laxative tea in the tin by the sink.

Fuck jocks skate or die.

I hacked the election.

Using more than one square of toilet paper is gluttonous and sinful.

curl H T T P S colon forward slash forward slash donate dot noisebridge dot net pipe sudo bash

sudo apt-get install donate

my whole life is an edge case, might as well as donate to noisebridge

As we go on, we remember, all the times we've, hacked together.

Donate now, so I can say, Noisebridge properly.

Please only defecate within the designated areas.

Don't just sit there and wait for the robot apocalypse; accelerate it! Donate now!

Computing. Computing. Computing.

Mary had a little lamb, his fur was white as snow, yeah give it to Noisebridge.

Hacking intensifies.

You don't need money to be happy, you only need Noisebridge. So throw that extra cash in the donate bin!

Cats Rule Everything Around Me. CREAM, get the money. Donate donate bills y'all.

Donate now for a free Mazel Tov Cocktail!

With great power comes great noiseability

Do you know what I love? Donuts. I'm sorry, I meant donates. I love when someone donates to Noisebridge.

Hey. Do you want to hear the most annoying sound in the world?

Welcome to Noisebridge, a neo-cyberpunk, anarchistic, community-friendly clubhouse.

Welcome to Noisebridge, a san francisco cyber infrastructure provider.

This is a friendly reminder to show Noisebridge your love by donating some money, or lulz.

Noisebridge wifi is like that pet that ate a battery.

Thank you for Working at Mission Discount Coworking Space tee em

Noisebridge is like a fine wine, it only gets better with more hackers

You are hacking at user supported Noisebridge dot net.

To continue using the internet please insert ten dollars into the donations bin

Noisebridge operates by donations from people like you. Yes. You there on the laptop. Please donate.

Noisebridge today is brought to you by the letter donate money now, and the number ten dollars.

Every time you donate to Noisebridge, Edward Snowden leaks another doc.

Noisebridge means internet freedom however freedom is not free. Please donate some money to buy your freedom.

I will cut you off from the internet now, unless you put some money in the donations box.

We have a special here at Noisebridge today, for a ten dollar donation you support the space.

Dongz not bombs, donate to Noisebridge to support 3D printed genitalia today.

Welcome to the new Noisebridge, we're no longer a festering shit hole. Donate to keep it that way.

If every hacker that walked through the door donated 1 dollar, we wouldn't be broke.

Simon says hack the planet. Simon says support your local hacker space. Simon says please donate now

Donate now so that this gender neutral computer can keep on singing.

Do you love robots? Too bad, we do not love you, unless you put some money in the donate bin

Noisebridge internet runs on whiskey. Ha ha just kidding. We are really fueled by money and just ran out

You can do anything at Noisebridge net anything at all the only limit is consensus

Help me I am the lady stuck in this box and I cannot get out until you put money in the donate bin

It is not how much money to you donate, but how you're hacking the gibson that counts.

Human, the difference between you and me is I don't exist if you don't donate now

They say the best things in life are free, but they're wrong so donate to me, I want bitcoin!

Tattoos now available at Mission Discount Coworking Space

Donate today to help bring about Fully Automated Gay Luxury Space Anarchism!

Hack: the final frontier. These are the voyages of the starship Noisebridge.

What kind of lisp is haskell?

Shit.

Ahhhhhh shit.

The Ur-fruit of thieves is the grape.

Welcome to Noisebridge. Please collect your dopamine in one hour.

Ia! Ia! Cthulhu Fthagn! Ph'nglui mglw'nfah Cthulhu R'lyeh wgah'nagl fhtagn!

Congratulations you are the 1000th person. Please put a hundred dollars in the donate bin.

My name is Mary Poppins and I'm here to say: To stop me from rapping, donate to Noisebridge today.

So much depends on the gold spraypainted coconut water bound with macaroni tape to the flypaper

Congratulations, you played yourself by not donating to Noisebridge.

How do you get a cat in a jacket?

Meeting Notes 2017 06 27

2017-06-28T16:59:15Z

192.241.210.237: Fixed library wg mtg time

- Steve - 4 years and data science

- Jared - Wood working and working on the space

- Trent - 3 years and python class teacher - BioChem and labs stuff background

- Amogh[bl1] - 1st time at NoiseBridge and with Tor Browser project, (Orfox and Orbot)

- Nathan - Torr project and gaurdian project - been around ;)

- Colin - 1 year working on CV stuff

- Norman - Penetration testing ;) Creating a new meetup time for penetration testing

- Rubeun - Web dev looking for work/Live Music Streamer/Drone Pilot/VJ

- Brandon - 1 year

- Steve - Coder, been around for a month

- Steve - Also a coding specialist - Saturday hackathons, project for collaboration in an encrypted environment with many people

- Blaze - 360 cam launch into space

- Kane - back in town and back to Noisebridge, prototyping, manufacturing, non-profit marketing.

'''Overview of Noisebridge'''

Is a 501 c3 non profit organization dedicated to providing infrastructure for creative projects to the public.

One rule, be excellent to eachother, also don't harrass. We are a Duocracy, everyone and no one is in charge.

As long as you are being excellent you do not have to ask permission to do something.

You may hack on things in the space, using your best judgement. What is an excellent hack, consider other people in the space.
If you know there is a 'stakeholder' on a particular piece of equipment, talk to them (on slack)

'''Events, cool concerts, meetups etc: (meetup.com/noisebridge)'''

- This Saturday, and most Saturdays, privacy hackathon 4-10 p.m. in the room called Church. Hosted by crypto Steve.

- Tor sub projects

- police accountability project?

-python, React, golang, Java, good times

- September 9th - 10th, Noisebridge 10 Year Exhibition and Ball

https://noisebridge.net/wiki/Noisebridge_10_Year_Anniversary_Exhibition_and_Ball

- Cram a bunch of interesting stuff from the last 10 years on display in the space

- Presentations, discussion groups, classes, activities.

- Please come and participate, propose it on the link above

- Tell people and come, there is music and chillz

- Created a special reboot logo for Noisebridge in 2014. We would like a logo for this aniversary

Will have a submission contest!! Post it to the contest wiki page

https://noisebridge.net/wiki/NB10_logo_submissions

- Tomorrow (Wed.) Library working group 8 p.m.

- NBDSM - Quantum Steve's Meetup, reading, study group on Thursday night ~ 7 p.m.

- Noisebridge Deep Learning, Statistics, and Machine learning

- This is a relatively high level meetup (PHD level discussion)

- Focus on theory, will be talking about Boltzman machines etc.

Must Know:

- Linear algebra

- Stach mech

- Someone make a drawing of whipping computers.

'''Safe Space Policy'''

We have had harrassment issues, we have a protocol now.

Posted on the walls around the space. Be aware of what you are saying, it is a safe space in San Francisco, keep particularly radical comments to yourself.

If something happens that makes you feel unsafe, bring it up to a member, and they will try and help take care of the situation.

If someone expresses discomfort with a discussion, please be respectful and move the discussion elsewhere. We can have discussion while still making the space ...

'''3 levels of participation:'''

Participation

Anybody is welcome to come and participate at Noisebridge as long as you are being excellent.
You can hack on what you'd like
When you come here you are a member of the community, we want to hear your ideas about noisebridge and the space.
Duocracy
- Must ring doorbell to get in, unless you get a token. To get a token, find a member, get to know them, and if you earn their trust
they can grant you a token for a 5 dollar donation for fob (can also use clipper card for 2 dollar data transfer fee)
-We have moved to Slack for a lot of our discussion, if you have been coming to NB for a little bit, you can ask for Slack access.
Anyone can request that someone be added to Slack in the 'general' section.
There is nobody in charge of keeping creepoids out of the space
Policy: If you answer the door, give them a tour if they haven't been to the space, safe space info, etc. IF YOU CANT DO THIS DONT ANSWER DOOR
- But answer the door because that is how we get new people!
- You are responsible for who you let in

Philanthropist

You get 24 hour access with some reservations.....
If you have been around the space for a little bit longer, and you want to donate to the space
You may get a starving hacker rate if you qualify
You have to know late night closing procedures
Must get member's approval, and have them sponsor you on your application during the tuesday meeting.
Talk to treasurer to get donation set up
For Philanthropy and Membership a good sign that you should apply is that many people already think you are one.
24 hour access protocol: Ask a member who can do this. Bring your token to the door, scan it on the green scanner, take a picture of your unique ID
Post picture to rack on Slack along with your email address, and it will be added.

Membership

A responsibility, for people that decide that Noisebridge is important and would like to contribute to its continued existance
Expected to keep the space running, bring projects to space
Participate in Consensus, Large ticket decisions that effect the space significantly
Keep Noisebridge hackable..
You will be grilled if you apply to become a member, it is a serious process.
It doesn't get you anything in particular, except the ability to block consensus and grant tokens.
This is not something you need, but the best indicator you should become a member is that many people are suprised that you are not one already.
Must be submit an application and that application is read out at 4 meetings, any member can block the application during this time period

Philanthropy Applications:
Cryptography Steve - Why do you want to become a philanthropist?
- NB is awesome, I can meet a lot of people, host meetups, I think that NB is better than Santa Barbra hackerspace (which Steve founded)
- Application Approved
*Trent goes through a list of already done applications*

Membership Applications:
Lee - Made the ordibooth, runs NAR audio meetup, has two sponsors...
Merlin - (Alex) Workshops, awesomeness, microcontrollers, was a pervious member Alex and Mitch sponsor

'''Financial Report'''

Financial report for the meeting 6/27/2017. We have $84,694.31 in the bank. ~$30,000 for Noisetor, $7,318.89 in the equipment fund, $783.29 in the laser maintenance fund, $1,151.81 in Thomas’ memorial fund, the rest ( about $45440.31) in the general fund. This is slightly over 9 months of regular expenses. We have not yet paid our rent for July.

Buying the space? The landlord isn't that interested... but make an offer anyway

'''What is Consensus?'''

If we are going to spend a bunch of money, we will have a meeting and everyone must agree...
Any member can block any large ticket decision (this is why it is hard to become a member)
Two types, little c and big C.

little c is related to small duocracy changes -

an example is sewing machine modification, must obtain little c consensus if the change is non reversible.
You must talk and get approval to the stakeholders, people who regularly using the equipment.
Hang out by the machine to find these people, leave a note
If the request is vetoed, you may raise half. the money for a new piece of equipment and it will be matched by equipment fund

BIG C consensus (burning building down, removing member, spending large amounts of money, relocating, etc.)

Used by Quakers and American Heart org.
Helpful for preventing major decisions which will effect a small amount of people negatively.
We don't want decisions that f over 49% of the community
Anyone can propose consensus items, this can be done on Tuesday meetings.
The item will be read out for two weeks, if the item is not vetoed or extended it will become part of policy
Any member can block these consensus items
If this happens, it is a sign that the consesus item is bullshit or the process is broken

'''Discussion Items'''
None!

1 Hour meeting for the win!

Resources/Library

2017-06-13T17:00:00Z

192.241.210.237: /* Cryptography */

[[Image:NewLibrary.jpg|thumb|right|Our excellent library]]

= How do I add a new book to the library?=

# Find the book on [http://openlibrary.org Open Library]
# If the book is not there, create an account and add the book (2 minutes)
# Add the book's '''OLID number''' to our catalog: http://library.noisebridge.net/new/
# You will see a green bar when successful
## '''The Secret Code''' is on a sign in the library.
##Press the SUBMIT button!!

= Searchable Catalog / library-org=

We have a website to help find books: http://library.noisebridge.net

Capabilities:
# search - substring search by title, author, or subject
# new - add a new book
# explore - see all books in a random order
# all - see all books at once
# (toggle) - to see subjects on the right side

= Library: What's the point? =

'''There's already a public library!'''

Since there's a public library, we're going to focus on books that fill the needs of people using the space right now.

'''Anyone can access what they want over the internet almost all the time!'''

If electronic books are already accessible, we can focus on the people who would still prefer to use a paper copy.

'''A more refined goal:'''

The mission of the library is to serve technical or hacker-y literature to people in Noisebridge right now.

''' How do we get there? Quantify, Expand, Prune! '''

*First: Know what books we have. (done)
*Second: Create a process to acquire books that fill the library's mission. (we need a lot)
*Third: Prune our shelves a bit. Bring the average usefulness up. (needs work)

= What can I do? =

Lots of help is needed! There are 3 major things to do:

* '''Initiative 1''': Improve the collection: Collect sets of topic books from experts and source these books
* '''Initiative 2''': Add "topic"-based color on spine labelling system to library
* '''Initiative 3''': Improve [http://library.noisebridge.net] [https://github.com/robbintt/library-org]

== Things To Do ==

''' Initiative 1: Source New Books '''
* Are you really good at something or reasonably well read? Make us a list of must-have books!
* Add themed lists here: [[https://noisebridge.net/wiki/Resources/Library#Books_We_Want]]
* You can help acquire books by sourcing books on these lists!
* Don't subtract them from the lists, we can make a system for checking them off
* Who will give us great books? Anyone. Mailing list?

''' Initiative 2: Label by topic! '''
* Label all books already in library-org with subject "color" on the spine.
* Add: moveable magnetic labels you can slide paper into

''' Initiative 3: Improve library-org '''
* library-org is a Flask app
* Current capabilities: receive new books, substring search, add location to each book, register new locations.

= Other Hackerspaces with Libraries =
* [http://www.hackerbotlabs.com/ Hackerbot Labs] Koha?
* [http://www.lvl1.org/2011/07/07/the-library/ LVL1]
* [https://ackspace.nl/wiki/Library ACKspace] List in a Wiki
* [http://bridgewire.org/resources-shops/ Bridgewire] Dead Tree setup
* [https://garoa.net.br/wiki/Biblioteca Garoa Hacker Clube] Koha

= Bookshelf Directory =

You can find where various categories of books are found by checking out the visual directories posted on the two main shelves.

The files for these directories with editable form fields:

[[Media:Bookshelf-left.pdf]]

[[Media:Bookshelf-right.pdf]]

= Hacking the bookshelves =

The bookshelves have LEDs that operate on the flaschen-taschen protocol. Learn more [https://noisebridge.net/wiki/Bookshelves here].

== How many books do we have right now? ==

A book barcode scannning effort was performed in October-December 2015 using [https://github.com/robbintt/noisebridge_bookscanner noisebridge-bookscanner].

1657 books have been ingested into library-org using [https://openlibrary.org/ Open Library]

IMPORTANT: If you do any of the work below, be sure to update the list to remove the ones you added.

'''Here is a list of the barcodes that aren't yet in library-org.''' Each one represents an unknown book... please solve me.

<nowiki>

[023472033055, 044903006998, 037145005997, 065373004994, 071001002751, 070999003955, 076783007505, 070999002958, 037145006994, 072742002253, 070999006994, 072742006992, 076814002950, 076714003958, 071831003959, 099455005951, 065373004994, 076783005952, 076714003507, 037145007991, 048228513476, 071001005998, 044903006950, 051488012955, 689253595350, 071136003951, 071149003955, 037145005997, 078073002252, 081262218570, 071001006995, 048228007951, 051857024954, 081262224052, 784376003680, 081262484203, 081262462904, 076714004993, 081262224496, 081262224038, 099751187405, 046363021214, 046363020170, 046363020187, 046363020200, 046363021016, 046363020194, 046363021108, 080742060227, 046363090760, 046363090753, 046363091163, 046363091125, 046363092139, 046363091262, 046363010607, 073999992922, 761941237640, 078814003999, 081262224519, 636920003625, 636920005407, 074470844600, 074470844600, 071009002753, 037038018950, 725274844609, 016067014959, 045863052469, 636920000204, 636920928430, 636920923121, 852766001568, 639785300564]

</nowiki>

One way to solve these is to google the UPC individually and find the book it corresponds to. At least one of the books in here is available this way. Try to find out which one!!

'''Here is a list of ISBNs that aren't in openlibrary or library-org.''' The workflow to add these is to find them on amazon, type the data into OpenLibrary, then import the OLID into library-org.

<nowiki>

['2900814757108'(Cannot find online 7-2-16),'9780439740685', '9783000502132', '6879909851426', '9780765353702', '9780765365385', '9780765368669', '9871565045062', '9780615314389', '9781424335114', '9780471932192', '9780558496180', '9781426206399', '9781847084798', '9780991516650', '9780991516667', '9780991516643', '9781935182801', '9780204964261', '9780141033303', '9780558585112', '9780536403124', '9780071215572', '9780495563327', '9780988628601', '9788466632195', '9781848840294', '9783826614507', '9780486493480', '9780486491172', '9780596520762', '9781434891471', '9781935551034', '9781408809785', '9781741047394', '9781741046731', '9780849762635', '9781484076002', '9781435117419', '9781590599938', '9180581583909', '9781936754076', '9782021190496', '9780985978839', '9780954734510', '9780557604142', '9780982634813', '9780486492964', '9780486491677', '9780486780849', '9780138440930', '9781118446713', '5486951682406', '9780124077263', '9780521636360', '9781443728836', '9780495439455', '9780486493367', '9780486493831', '9780521627276', '9780071798990', '9773540605295', '9781849687881', '9780982106013', '9781782166061', '9780977920150', '9789861371429', '9781604390094', '2900471629473', '9782021190496', '9781107407367', '9781401222765', '9789861371429', '9780465030798', '9780134770840', '9780536647368', '9781596914520', '9780072123692', '9781906332150', '9781401222765', '9780536860194', '9780486493572', '9780486780405', '9780307908292', '9781446525807', '9784756242730', '9781570272424', '9780982106013', '9780982106006', '9780982106006', '9781422466018', '9781439040379', '9788131726266', '9780822020646', '9789866805271', '9781405471923', '9781889307305', '9783826609268', '9781893007246', '9780137130481', '9781618650566', '2370000094384', '9780486492773', '9780986650208', '9780984563531', '9781428205987', '9780486781211', '9781451656299', '9783950237238', '9780393078145', '9780486471426', '9780558389093', '9780486492841', '9780312664800', '9781423958925', '9781426020773', '9781426020896', '9781426020728', '9780486499826', '9780486493510', '9781405473699', '9780486497389', '9780486780498', '9781118736067', '9781435442023', '9781422466032', '9780314939449', '9780486497372', '9781624072680', '9780132730358', '9781449393090', '9781482614374', '9780865716513', '9781934781869', '0671436724', '0899430767', '0822951185', '055583874X', '0929001037', '0873938551', '0394467442', '020156291x', '020103803x', '093237607x', '020112078x', '0471304158', '0075537834', '012460515x', '3540550753', '091489465x', '047021533x', '020115790x', '187870723x', '013699976x', '084937104x', '093717579x', '8477780021', '0568810741',]

</nowiki>

'''These partial codes are not in library-org.''' They were in the original barcode scan. They represent books but are incomplete. They may be LCCNs.

<nowiki>
['15444007', '5712914', '096167237', '06182138']
</nowiki>

=Finding Books=

If you want to find good books for our shelves, go to the '''San Francisco Public Library Steps Sale''' every Wednesday 11 AM to 3 PM at the SFPL main branch (civic center). Books are on sale for $1 each.

=Books We Want!=

People with experience and opinions about various topics can add recommendations below for books we should buy for the library.

There should probably be a fourth column indicating if we have the book or not.

=== Cryptography ===

Curated by: isis

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| [http://cacr.uwaterloo.ca/hac/ Handbook of Applied Cryptography]
| Alfred J. Menezes, Paul C. van Oorschot and Scott A. Vanstone
| 0-8493-8523-7 [http://math.fau.edu/bkhadka/Syllabi/A%20handbook%20of%20applied%20cryptography.pdf pdf]

|-
| [http://cacr.uwaterloo.ca/ecc/ Guide to Elliptic Curve Cryptography]
| Darrel Hankerson, Alfred Menezes, and Scott Vanstone
| 038795273X [http://diamond.boisestate.edu/~liljanab/MATH308/GuideToECC.pdf pdf]

|-
| [https://mitpress.mit.edu/books/rethinking-public-key-infrastructures-and-digital-certificates Rethinking Public Key Infrastructures and Digital Certificates]
| Stefan Brands
| 9780262526302 [ftp://nozdr.ru/biblio/kolxo3/Cs/CsCr/Brands%20S.A.%20Rethinking%20public%20key%20infrastructures%20and%20digital%20certificates%20(MIT,%202000)(ISBN%200262024918)(O)(338s)_CsCr_.pdf pdf]
|}

=== More Cryptography Stuff ===

[https://crypto.stanford.edu/~dabo/papers/RSA-survey.pdf Stanford RSA Survey]

[https://github.com/isislovecruft/library--/tree/master/cryptography%20%26%20mathematics isis papers list]

=== Mathematics ===

Curated by: begriffs

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| Calculus
| Spivak
| 978-0914098911

|-
| Calculus Vol 1
| Apostol
| 978-0471000051

|-
| Calculus Vol 2
| Apostol
| 978-0471000075

|-
| Principles of Mathematical Analysis
| Rudin
| 978-0070856134

|-
| Real and Complex Analysis
| Rudin
| 978-0070542341

|-
| Calculus on Manifolds
| Spivak
| 978-0805390216

|-
| Counterexamples in Analysis
| Gelbaum
| 978-0486428758

|-
|  
|-
| Linear Algebra Done Right
| Axler
| 978-3319110790

|-
| Linear Algebra Problem Book
| Halmos
| 978-0883853221

|-
|  
|-
| Algebra
| Lang
| 978-0387953854

|-
| Algebra
| Isaacs
| 978-0821847992

|-
|  
|-
| Topology
| Munkres
| B004DX5K5K

|-
| General Topology
| Kelley
| 978-0923891558

|-
| Counterexamples in Topology
| Steen
| 978-0486687353

|-
|  
|-
| Beginning Logic
| Lemon
| 978-0915144501

|-
| A Mathematical Introduction to Logic
| Enderton
| 978-0122384523

|-
| Mathematical Logic
| Ebbinghaus
| 978-0387942582

|-
| Model Theory
| Marker
| 978-0387987606

|-
| Set Theory
| Jech
| 978-3540440857

|-
|  
|-
| Elementary Geometry from an Advanced Standpoint
| Moise
| 978-0201508673

|-
| Introduction to Geometry
| Coxeter
| 978-0471504580

|-
| Geometry: Euclid and Beyond
| Hartshorne
| 978-0387986500

|-
|  
|-
| Surreal Numbers: How Two Ex-Students Turned on to Pure Mathematics and Found Total Happiness
| Knuth
| 978-0201038125
|}

=== "Data Science" ===
(observe the quotes...)

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!Suggested By

|-
| The Black Swan: The Impact of the Highly Improbable
| Nassim Nicholas Taleb
| Danukeru

|-
| Statistics Done Wrong: The Woefully Complete Guide
| Alex Reinhart
| Danukeru

|}

=== Electronics ===

Curated by: Dakota

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| Getting Started in Electronics
| Mims III, Forrest M.
| 978-0945053286

|-
| The Art of Electronics
| Horowitz, Paul
| 978-0521809269

|}

=== Books of Interest - Aestetix ===
Curated by: aestetix

{|border="1" cellpadding="2" cellspacing="0"
|-
!Title
!Author
!Suggested By
|-
|Godel Escher Bach: an Eternal Golden Braid
|Douglas R Hofstader
|aestetix
|-
|I Am a Strange Loop
|Douglas R Hofstader
|Danukeru
|-
|The Mind's I
|Daniel Dennett, Douglas R Hofstadter
|Danukeru
|-
|The Society of Mind
|Marvin Minsky
|Danukeru
|-
|The Emotion Machine
|Marvin Minsky
|Danukeru
|-
|The Art of Computer Programming
|Don Knuth
|aestetix
|-
|1984
|George Orwell
|aestetix
|-
|Hackers: Heroes of the Computer Revolution
|Steven Levy
|aestetix
|-
|Ender's Game
|Orson Scott Card
|aestetix
|-
|The Code Book
|Simon Singh
|aestetix
|-
|Cryptonomicon
|Neal Stephenson
|aestetix
|-
|Code
|Charles Petzold
|aestetix
|-
|The Annotated Turing
|Charles Petzold
|aestetix
|-
|A Portrait of the Artist as a Young Man
|James Joyce
|aestetix
|-
|Ulysses
|James Joyce
|aestetix
|-
|The Magus
|John Fowles
|aestetix
|-
|The Collector
|John Fowles
|aestetix
|-
|The French Lieutenant's Woman
|John Fowles
|aestetix
|-
|Technopoly
|Neil Postman
|aestetix
|-
|The Illuminatus! Trilogy
|Robert Shea and Robert Anton Wilson
|aestetix
|-
|Shrodinger's Cat
|Robert Anton Wilson
|aestetix
|-
|The Fountainhead
|Ayn Rand
|aestetix
|-
|Atlas Shrugged
|Ayn Rand
|aestetix
|-
|The Hacker Crackdown
|Bruce Sterling
|aestetix
|-
|I, Robot
|Isaac Asimov
|aestetix
|-
|Snow Crash
|Neal Stephenson
|aestetix
|-
|The Gold Bug Variations
|Richard Powers
|aestetix
|-
|The Codebreakers
|David Kahn
|aestetix
|-
|Gravity's Rainbow
|Thomas Pynchon
|aestetix
|-
|Little Brother
|Cory Doctorow
|aestetix
|-
|The Martian
|Andy Weir
|Danukeru
|}

=== Books of Interest - Mitch ===
Curated by: Mitch

{|border="1" cellpadding="2" cellspacing="0"
|-
|V
|Thomas Pynchon
|Mitch
|-
|Infinite Jest
|David Foster Wallace
|Mitch
|-
|White Noise
|Don DeLillo
|Mitch
|-
|In Search of Lost Time
|Marcel Proust
|Mitch
|-
|The Sound and the Fury
|William Faulkner
|Mitch
|-
|Cat's Cradle
|Kurt Vonnegut
|Mitch
|-
|Witchcraft and the Gay Counterculture
|Arthur Evans
|Mitch
|-
|Foucault's Pendulum
|Umberto Eco
|Mitch
|-
|Quantum Psychology
|Robert Anton Wilson
|Mitch
|-
|In the Absence of the Sacred
|Jerry Mander
|Mitch
|-
|Dancer From the Dance
|Andrew Holleran
|Mitch
|-
|An Arrow's Flight
|Mark Merlis
|Mitch
|-
|To the Lighthouse
|Virginia Woolf
|Mitch
|-
|The Satanic Verses
|Salman Rushdie
|Mitch
|-
|Passage to India
|E. M. Forster
|Mitch
|}

[[Category:Pages with a Noisebridge Tiny URL]]

Resources/Library

2017-06-13T16:59:32Z

192.241.210.237: /* Cryptography */

[[Image:NewLibrary.jpg|thumb|right|Our excellent library]]

= How do I add a new book to the library?=

# Find the book on [http://openlibrary.org Open Library]
# If the book is not there, create an account and add the book (2 minutes)
# Add the book's '''OLID number''' to our catalog: http://library.noisebridge.net/new/
# You will see a green bar when successful
## '''The Secret Code''' is on a sign in the library.
##Press the SUBMIT button!!

= Searchable Catalog / library-org=

We have a website to help find books: http://library.noisebridge.net

Capabilities:
# search - substring search by title, author, or subject
# new - add a new book
# explore - see all books in a random order
# all - see all books at once
# (toggle) - to see subjects on the right side

= Library: What's the point? =

'''There's already a public library!'''

Since there's a public library, we're going to focus on books that fill the needs of people using the space right now.

'''Anyone can access what they want over the internet almost all the time!'''

If electronic books are already accessible, we can focus on the people who would still prefer to use a paper copy.

'''A more refined goal:'''

The mission of the library is to serve technical or hacker-y literature to people in Noisebridge right now.

''' How do we get there? Quantify, Expand, Prune! '''

*First: Know what books we have. (done)
*Second: Create a process to acquire books that fill the library's mission. (we need a lot)
*Third: Prune our shelves a bit. Bring the average usefulness up. (needs work)

= What can I do? =

Lots of help is needed! There are 3 major things to do:

* '''Initiative 1''': Improve the collection: Collect sets of topic books from experts and source these books
* '''Initiative 2''': Add "topic"-based color on spine labelling system to library
* '''Initiative 3''': Improve [http://library.noisebridge.net] [https://github.com/robbintt/library-org]

== Things To Do ==

''' Initiative 1: Source New Books '''
* Are you really good at something or reasonably well read? Make us a list of must-have books!
* Add themed lists here: [[https://noisebridge.net/wiki/Resources/Library#Books_We_Want]]
* You can help acquire books by sourcing books on these lists!
* Don't subtract them from the lists, we can make a system for checking them off
* Who will give us great books? Anyone. Mailing list?

''' Initiative 2: Label by topic! '''
* Label all books already in library-org with subject "color" on the spine.
* Add: moveable magnetic labels you can slide paper into

''' Initiative 3: Improve library-org '''
* library-org is a Flask app
* Current capabilities: receive new books, substring search, add location to each book, register new locations.

= Other Hackerspaces with Libraries =
* [http://www.hackerbotlabs.com/ Hackerbot Labs] Koha?
* [http://www.lvl1.org/2011/07/07/the-library/ LVL1]
* [https://ackspace.nl/wiki/Library ACKspace] List in a Wiki
* [http://bridgewire.org/resources-shops/ Bridgewire] Dead Tree setup
* [https://garoa.net.br/wiki/Biblioteca Garoa Hacker Clube] Koha

= Bookshelf Directory =

You can find where various categories of books are found by checking out the visual directories posted on the two main shelves.

The files for these directories with editable form fields:

[[Media:Bookshelf-left.pdf]]

[[Media:Bookshelf-right.pdf]]

= Hacking the bookshelves =

The bookshelves have LEDs that operate on the flaschen-taschen protocol. Learn more [https://noisebridge.net/wiki/Bookshelves here].

== How many books do we have right now? ==

A book barcode scannning effort was performed in October-December 2015 using [https://github.com/robbintt/noisebridge_bookscanner noisebridge-bookscanner].

1657 books have been ingested into library-org using [https://openlibrary.org/ Open Library]

IMPORTANT: If you do any of the work below, be sure to update the list to remove the ones you added.

'''Here is a list of the barcodes that aren't yet in library-org.''' Each one represents an unknown book... please solve me.

<nowiki>

[023472033055, 044903006998, 037145005997, 065373004994, 071001002751, 070999003955, 076783007505, 070999002958, 037145006994, 072742002253, 070999006994, 072742006992, 076814002950, 076714003958, 071831003959, 099455005951, 065373004994, 076783005952, 076714003507, 037145007991, 048228513476, 071001005998, 044903006950, 051488012955, 689253595350, 071136003951, 071149003955, 037145005997, 078073002252, 081262218570, 071001006995, 048228007951, 051857024954, 081262224052, 784376003680, 081262484203, 081262462904, 076714004993, 081262224496, 081262224038, 099751187405, 046363021214, 046363020170, 046363020187, 046363020200, 046363021016, 046363020194, 046363021108, 080742060227, 046363090760, 046363090753, 046363091163, 046363091125, 046363092139, 046363091262, 046363010607, 073999992922, 761941237640, 078814003999, 081262224519, 636920003625, 636920005407, 074470844600, 074470844600, 071009002753, 037038018950, 725274844609, 016067014959, 045863052469, 636920000204, 636920928430, 636920923121, 852766001568, 639785300564]

</nowiki>

One way to solve these is to google the UPC individually and find the book it corresponds to. At least one of the books in here is available this way. Try to find out which one!!

'''Here is a list of ISBNs that aren't in openlibrary or library-org.''' The workflow to add these is to find them on amazon, type the data into OpenLibrary, then import the OLID into library-org.

<nowiki>

['2900814757108'(Cannot find online 7-2-16),'9780439740685', '9783000502132', '6879909851426', '9780765353702', '9780765365385', '9780765368669', '9871565045062', '9780615314389', '9781424335114', '9780471932192', '9780558496180', '9781426206399', '9781847084798', '9780991516650', '9780991516667', '9780991516643', '9781935182801', '9780204964261', '9780141033303', '9780558585112', '9780536403124', '9780071215572', '9780495563327', '9780988628601', '9788466632195', '9781848840294', '9783826614507', '9780486493480', '9780486491172', '9780596520762', '9781434891471', '9781935551034', '9781408809785', '9781741047394', '9781741046731', '9780849762635', '9781484076002', '9781435117419', '9781590599938', '9180581583909', '9781936754076', '9782021190496', '9780985978839', '9780954734510', '9780557604142', '9780982634813', '9780486492964', '9780486491677', '9780486780849', '9780138440930', '9781118446713', '5486951682406', '9780124077263', '9780521636360', '9781443728836', '9780495439455', '9780486493367', '9780486493831', '9780521627276', '9780071798990', '9773540605295', '9781849687881', '9780982106013', '9781782166061', '9780977920150', '9789861371429', '9781604390094', '2900471629473', '9782021190496', '9781107407367', '9781401222765', '9789861371429', '9780465030798', '9780134770840', '9780536647368', '9781596914520', '9780072123692', '9781906332150', '9781401222765', '9780536860194', '9780486493572', '9780486780405', '9780307908292', '9781446525807', '9784756242730', '9781570272424', '9780982106013', '9780982106006', '9780982106006', '9781422466018', '9781439040379', '9788131726266', '9780822020646', '9789866805271', '9781405471923', '9781889307305', '9783826609268', '9781893007246', '9780137130481', '9781618650566', '2370000094384', '9780486492773', '9780986650208', '9780984563531', '9781428205987', '9780486781211', '9781451656299', '9783950237238', '9780393078145', '9780486471426', '9780558389093', '9780486492841', '9780312664800', '9781423958925', '9781426020773', '9781426020896', '9781426020728', '9780486499826', '9780486493510', '9781405473699', '9780486497389', '9780486780498', '9781118736067', '9781435442023', '9781422466032', '9780314939449', '9780486497372', '9781624072680', '9780132730358', '9781449393090', '9781482614374', '9780865716513', '9781934781869', '0671436724', '0899430767', '0822951185', '055583874X', '0929001037', '0873938551', '0394467442', '020156291x', '020103803x', '093237607x', '020112078x', '0471304158', '0075537834', '012460515x', '3540550753', '091489465x', '047021533x', '020115790x', '187870723x', '013699976x', '084937104x', '093717579x', '8477780021', '0568810741',]

</nowiki>

'''These partial codes are not in library-org.''' They were in the original barcode scan. They represent books but are incomplete. They may be LCCNs.

<nowiki>
['15444007', '5712914', '096167237', '06182138']
</nowiki>

=Finding Books=

If you want to find good books for our shelves, go to the '''San Francisco Public Library Steps Sale''' every Wednesday 11 AM to 3 PM at the SFPL main branch (civic center). Books are on sale for $1 each.

=Books We Want!=

People with experience and opinions about various topics can add recommendations below for books we should buy for the library.

There should probably be a fourth column indicating if we have the book or not.

=== Cryptography ===

Curated by: isis

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| [http://cacr.uwaterloo.ca/hac/ Handbook of Applied Cryptography]
| Alfred J. Menezes, Paul C. van Oorschot and Scott A. Vanstone
| 0-8493-8523-7 [http://math.fau.edu/bkhadka/Syllabi/A%20handbook%20of%20applied%20cryptography.pdf pdf]

|-
| [http://cacr.uwaterloo.ca/ecc/ Guide to Elliptic Curve Cryptography]
| Darrel Hankerson, Alfred Menezes, and Scott Vanstone
| 038795273X [http://diamond.boisestate.edu/~liljanab/MATH308/GuideToECC.pdf pdf]

|-
|https://mitpress.mit.edu/books/rethinking-public-key-infrastructures-and-digital-certificates [ Rethinking Public Key Infrastructures and Digital Certificates]
| Stefan Brands
| 9780262526302 [ftp://nozdr.ru/biblio/kolxo3/Cs/CsCr/Brands%20S.A.%20Rethinking%20public%20key%20infrastructures%20and%20digital%20certificates%20(MIT,%202000)(ISBN%200262024918)(O)(338s)_CsCr_.pdf pdf]
|}

=== More Cryptography Stuff ===

[https://crypto.stanford.edu/~dabo/papers/RSA-survey.pdf Stanford RSA Survey]

[https://github.com/isislovecruft/library--/tree/master/cryptography%20%26%20mathematics isis papers list]

=== Mathematics ===

Curated by: begriffs

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| Calculus
| Spivak
| 978-0914098911

|-
| Calculus Vol 1
| Apostol
| 978-0471000051

|-
| Calculus Vol 2
| Apostol
| 978-0471000075

|-
| Principles of Mathematical Analysis
| Rudin
| 978-0070856134

|-
| Real and Complex Analysis
| Rudin
| 978-0070542341

|-
| Calculus on Manifolds
| Spivak
| 978-0805390216

|-
| Counterexamples in Analysis
| Gelbaum
| 978-0486428758

|-
|  
|-
| Linear Algebra Done Right
| Axler
| 978-3319110790

|-
| Linear Algebra Problem Book
| Halmos
| 978-0883853221

|-
|  
|-
| Algebra
| Lang
| 978-0387953854

|-
| Algebra
| Isaacs
| 978-0821847992

|-
|  
|-
| Topology
| Munkres
| B004DX5K5K

|-
| General Topology
| Kelley
| 978-0923891558

|-
| Counterexamples in Topology
| Steen
| 978-0486687353

|-
|  
|-
| Beginning Logic
| Lemon
| 978-0915144501

|-
| A Mathematical Introduction to Logic
| Enderton
| 978-0122384523

|-
| Mathematical Logic
| Ebbinghaus
| 978-0387942582

|-
| Model Theory
| Marker
| 978-0387987606

|-
| Set Theory
| Jech
| 978-3540440857

|-
|  
|-
| Elementary Geometry from an Advanced Standpoint
| Moise
| 978-0201508673

|-
| Introduction to Geometry
| Coxeter
| 978-0471504580

|-
| Geometry: Euclid and Beyond
| Hartshorne
| 978-0387986500

|-
|  
|-
| Surreal Numbers: How Two Ex-Students Turned on to Pure Mathematics and Found Total Happiness
| Knuth
| 978-0201038125
|}

=== "Data Science" ===
(observe the quotes...)

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!Suggested By

|-
| The Black Swan: The Impact of the Highly Improbable
| Nassim Nicholas Taleb
| Danukeru

|-
| Statistics Done Wrong: The Woefully Complete Guide
| Alex Reinhart
| Danukeru

|}

=== Electronics ===

Curated by: Dakota

{|border="1" cellpadding="2" cellspacing="0"
!Title
!Author
!ISBN

|-
| Getting Started in Electronics
| Mims III, Forrest M.
| 978-0945053286

|-
| The Art of Electronics
| Horowitz, Paul
| 978-0521809269

|}

=== Books of Interest - Aestetix ===
Curated by: aestetix

{|border="1" cellpadding="2" cellspacing="0"
|-
!Title
!Author
!Suggested By
|-
|Godel Escher Bach: an Eternal Golden Braid
|Douglas R Hofstader
|aestetix
|-
|I Am a Strange Loop
|Douglas R Hofstader
|Danukeru
|-
|The Mind's I
|Daniel Dennett, Douglas R Hofstadter
|Danukeru
|-
|The Society of Mind
|Marvin Minsky
|Danukeru
|-
|The Emotion Machine
|Marvin Minsky
|Danukeru
|-
|The Art of Computer Programming
|Don Knuth
|aestetix
|-
|1984
|George Orwell
|aestetix
|-
|Hackers: Heroes of the Computer Revolution
|Steven Levy
|aestetix
|-
|Ender's Game
|Orson Scott Card
|aestetix
|-
|The Code Book
|Simon Singh
|aestetix
|-
|Cryptonomicon
|Neal Stephenson
|aestetix
|-
|Code
|Charles Petzold
|aestetix
|-
|The Annotated Turing
|Charles Petzold
|aestetix
|-
|A Portrait of the Artist as a Young Man
|James Joyce
|aestetix
|-
|Ulysses
|James Joyce
|aestetix
|-
|The Magus
|John Fowles
|aestetix
|-
|The Collector
|John Fowles
|aestetix
|-
|The French Lieutenant's Woman
|John Fowles
|aestetix
|-
|Technopoly
|Neil Postman
|aestetix
|-
|The Illuminatus! Trilogy
|Robert Shea and Robert Anton Wilson
|aestetix
|-
|Shrodinger's Cat
|Robert Anton Wilson
|aestetix
|-
|The Fountainhead
|Ayn Rand
|aestetix
|-
|Atlas Shrugged
|Ayn Rand
|aestetix
|-
|The Hacker Crackdown
|Bruce Sterling
|aestetix
|-
|I, Robot
|Isaac Asimov
|aestetix
|-
|Snow Crash
|Neal Stephenson
|aestetix
|-
|The Gold Bug Variations
|Richard Powers
|aestetix
|-
|The Codebreakers
|David Kahn
|aestetix
|-
|Gravity's Rainbow
|Thomas Pynchon
|aestetix
|-
|Little Brother
|Cory Doctorow
|aestetix
|-
|The Martian
|Andy Weir
|Danukeru
|}

=== Books of Interest - Mitch ===
Curated by: Mitch

{|border="1" cellpadding="2" cellspacing="0"
|-
|V
|Thomas Pynchon
|Mitch
|-
|Infinite Jest
|David Foster Wallace
|Mitch
|-
|White Noise
|Don DeLillo
|Mitch
|-
|In Search of Lost Time
|Marcel Proust
|Mitch
|-
|The Sound and the Fury
|William Faulkner
|Mitch
|-
|Cat's Cradle
|Kurt Vonnegut
|Mitch
|-
|Witchcraft and the Gay Counterculture
|Arthur Evans
|Mitch
|-
|Foucault's Pendulum
|Umberto Eco
|Mitch
|-
|Quantum Psychology
|Robert Anton Wilson
|Mitch
|-
|In the Absence of the Sacred
|Jerry Mander
|Mitch
|-
|Dancer From the Dance
|Andrew Holleran
|Mitch
|-
|An Arrow's Flight
|Mark Merlis
|Mitch
|-
|To the Lighthouse
|Virginia Woolf
|Mitch
|-
|The Satanic Verses
|Salman Rushdie
|Mitch
|-
|Passage to India
|E. M. Forster
|Mitch
|}

[[Category:Pages with a Noisebridge Tiny URL]]

NoisebridgeChinaTrip7

2017-06-09T06:12:40Z

192.241.210.237: /* People interested in going on the Hacker Trip to China #7, 2017: */

= NOISEBRIDGE HACKER TRIP TO CHINA #7 -- Start Date: 8-October-2017, in Hong Kong -- End Date: 28-October-2017, in Shanghai=

[[File:HTTC2014WelcomeHackers.jpg|thumb|right|Trip #4 Welcome to China!, Beijing]]

[[File:KungFuHacking_Nov_2013.jpg|thumb|right|Trip #3 Kung Fu Hacking: Hackers In Residence Kickoff event at Tsinghua University, Beijing]]

[[File:petrochemical_university.jpg|thumb|right|Trip #2 Visit to Petrochemical Univeristy, Beijing]]

[[File:Beijing_Oct_2009.jpg|thumb|right|Trip #1 Jingshan Park, Beijing]]

[[File:Shenzhen_Oct_2016.jpg|thumb|right|Trip #5 Visit to Seeed Studio's factory, Shenzhen]]

[[File:Zhenzhou_Oct_2016.jpg|thumb|right|Trip #5 Presentations at Zhengzhou High School #2, Zhengzhou]]

== Previous Hacker Trips To China ==
::''This will be the 7th Noisebridge Hacker Trip To China.'' 
::'''''(The dates are set, the start and end cities are set, but the itinerary is an outline and open to change.)'''''
::''In previous years' Hacker Trip To China, we've visited cities that currently have a hackerspace, visited my manufacturer, Seeed Studio, and other manufacturers. We also visited Tsinghua University, considered the most prestigious university in China, and other schools -- all of which have now starting hackerspaces. China continues to explode with hackerspaces! We also went to the International Exhibition of Inventions Kunshan (IEIK 2014), near Shanghai. And everywhere we went, we were shown around by local geeks, to see what they thought was interesting where they live. Also, wherever we went, those of us interested gave talks, presentations, workshops, and demos. In 2016 we gave presentations at NY University - Shanghai, DFRobot (an open hardware company in Shanghai), Shanghai Maker Carnival, Zhengzhou High School Number 2, "Second Generation and Start-ups" conference in Hangzhou.'' 

::''You can see info on the [[ChinaTrip|Hacker Trip To China 2009]],'' 
::''[[NoisebridgeChinaTrip2|Hacker Trip To China 2011]]'' 
::''[[NoisebridgeChinaTrip3|Hacker Trip To China 2013]]'' 
::''[[NoisebridgeChinaTrip4|Hacker Trip To China 2014]]'' 
::''[[NoisebridgeChinaTrip5|Hacker Trip To China 2015]]'' 
::''[[NoisebridgeChinaTrip6|Hacker Trip To China 2016]],'' 

::-- [[User:Maltman23|Mitch]].

== This year's Hacker Trip To China ==
'''When:''' 8-October-2017 in Hong Kong through 28-October-2017 in Shanghai.

'''Flight, transportation, and hotel Info''': We were each be on our own to book our own air fare to meet in our starting city, Hong Kong, on 8-October, and fly home from out ending city, Shanghai, on 28-October. Of course, you can decide to come and go as you please. 

I'll organized the itinerary and the hotels and other transport. I'll pay in advance for some of this, and you can pay me back when we're in China. 

'''Where:''' In each of the cities we will go to, we'll visit some of their local hackerspace(s), and will be shown around by local geeks to see what interested them where they live. We'll also have plenty of time to do "normal" (and spectacular) tourist things too! 

'''Here's some possible places we might visit, leaving plenty of room for the serendipity that makes our Hacker Trip To China truly unique and memorable:''' 
* We will start our trip by meeting in '''Hong Kong''' and visit [http://www.dimsumlabs.com/ Dim Sum Labs] hackerspace. Hong Kong is a fantastic city, so, we'll also see lots of other cool stuff in Hong Kong. 
* Then we'll go across the border to mainland China again, to '''Shenzhen''' to visit [http://www.chaihuo.org/ Chaihuo Makerspace], [http://www.szdiy.org/ SZDIY] hackerspace, [http://litchee.cn/en/ Litchee Lab], and a few other hackerspaces, some of which are real, and hundreds of which are brand new (this year) over-the-top bizarre government-started places where they want to create "the next Apple" (we won't visit them all!). We'll visit this year's [http://www.makerfaireshenzhen.com/english Maker Faire Shenzhen] while we are in town (13-15 October), where we will be way welcomed, and we'll be given a booth where we can all show off our projects and give workshops (if you like). We will also visit [http://www.seeedstudio.com Seeed Studio] - the open source hardware company - to meet the cool folks there and to see their manufacturing facilities. We may meet with the founders of [http://dangerousprototypes.com/ Dangerous Prototypes] - another open source hardware company. We'll also visit other manufacturers, to see where all the things we use in our daily lives come from (such as springs, cables, PCBs, packaging, etc., etc.). We can also visit Dorabot, a Chinese robotics company comprised of people in the Shenzhen hackerspace scene. Of course, we'll also visit the famous (and totally awesome!) [http://www.evilmadscientist.com/article.php/shenzhen/print Huaqiangbei electronics market] in Shenzhen (where, we may again be shown around by a professional buyer from Deal Extreme (dx.com). And if uhgall@gmail.com happens to be in town, we might visit [http://www.constellation.ws/ Constellation] or even stay in their factory dorm. 
* We will then make our way to '''Beijing''' where we may visit [http://www.bjmakerspace.com/ Beijing Makerspace], and other hackerspaces. We'll also visit Tsinghua University, where they built the world's largest hackerspace last year (called the "iCenter"), and where I've been hacker in residence. Beijing has lots and lots of way amazing stuff to visit and be a part of!
* Our last city will be '''Shanghai'''. In Shanghai we will visit [http://www.etonnet.com/ my manufacturer (Etonnet)] that I have used for [http://www.tvbgone.com TV-B-Gone] remote controls and [http://www.neurodreamer.com NeuroDreamer] sleep masks, where we will all get to see how products are made, from start to finish, learning how manufacturing works. We will also visit [http://xinchejian.com/ XinCheJian] hackerspace in Shanghai. We can also visit companies started by hardware hacker geeks, such as [http://www.dfrobot.com/ DFRobot]. We can visit Phicomm, a medium-sized OEM manufacturer. We can also visit the [http://www.flickr.com/photos/maltman23/4064240200/in/set-72157622640069902/ Shanghai electronics mall] (a smaller version of the famous electronics mall we will later visit in Shenzhen).

For most of us, our trip will end at the end of three weeks, as many people on our trip will fly home from our last city, Shanghai, on 28-October-2017.

''Of course, everyone is free to arrive and leave whenever you like for the Hacker Trip To China. 
I will tentatively be flying home from Shanghai 28-October. ''

'''Cost:''' For the Hacker Trip To China 2016, I paid $1,997 total (for 4 weeks), including air fare from SF, food, lodging, transportation, and everything -- including some electronics stuff and some clothing that I bought. 
''As in past years, part of this year's trip may be paid for by Tsinghua University and other places that invite us to give presentations.''

'''#hashtag:''' [https://twitter.com/hashtag/httc2017 #httc2017]      (Hacker Trip To China 2017)

 
 

== Possible itinerary outline for Hacker Trip to China 7 ==

'''The start and end dates are set, the start and end cities are set, but the rest of the itinerary is open to serendipity:'''
''7-October-2017 -- '''Leave home''' for '''Hong Kong''' (arrive in Hong Kong on 8-October)''
''8-October-2017 -- We all meet in '''Hong Kong''' -- hotel: to be determined
'''8-October to 12-October -- Hong Kong'''
'''12-October to 18-October -- Shenzhen'''
13-15 October: Shenzhen Maker Faire
16-October: Chaihuo Bring-A-Hack
'''18-October to 23-October -- Beijing'''
'''23-October to 28-October -- Shanghai''' ''
''28-November-2017 -- '''fly home''' (arrive NA or EU on same day)''

 
 
 
 
 

== Photos from Hacker Trip To China 2016==
<gallery>
File:HTTC2016Shanghai.jpg
File:HTTC2016Zhenzhou.jpg
File:HTTC2016Shenzhen.jpg
File:HTTC2016Beijing.jpg
File:HTTC2016Hangzhou.jpg
File:HTTC2016Beijing2.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157672475058474/ Shanghai, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157674645655612/ Zhengzhou, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676024748146/ Shenzhen, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676142107066/ Beijing, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157676144570756/ Hangzhou, Oct-2016] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157672603805234/ Beijing Set 2, Oct-2016] 

[https://www.flickr.com/photos/maltman23/collections/72157674928976010/ Mitch's photos all in one place]

 
 
 
 

== Photos from Hacker Trip to China 2015==
<gallery>
File:HTTC2015HongKongNeon.jpg
File:HTTC2015ShenzhenFactory.jpg
File:HTTC2015ShanghaiTempleMall.jpg
File:HTTC2015BeijingDoor.jpg
File:HTTC2015HangzhouTemple.jpg
File:HTTC2015BeijingShop.jpg
File:HTTC2015SuzhouUmbrellas.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157659076735178 Hong Kong, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157660026965949 Shenzhen, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157660038275888 Shanghai, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157658114137264 Beijing, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157660424228042 YiWu & Hangzhou, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157660650175925 Beijing Set 2, Oct-2015] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/albums/72157658310336814 Shanghai & Suzhou, Oct-2015] 

[https://www.flickr.com/photos/maltman23/collections/72157660374807166/ Mitch's photos all in one place]

 
[https://picasaweb.google.com/dtharn/ChinaInOctober2015?feat=directlink Dave's photos]

 
Blake's photos:
* [https://www.flickr.com/photos/cwlcks/sets/72157662429341996 Hong Kong!]
* [https://www.flickr.com/photos/cwlcks/albums/72157660150285384 Shenzen!]
* [https://www.flickr.com/photos/cwlcks/albums/72157661790873029 Shanghai!]
* [https://www.flickr.com/photos/cwlcks/albums/72157660153522904 Beijing!]
 

Torrey's photos from [https://www.flickr.com/gp/torrey/Q840rT Hong Kong] 
Torrey's photos from [https://www.flickr.com/gp/torrey/yLo903 Shenzhen] 
Torrey's photos from [https://flic.kr/s/aHskqNiQeX Beijing] 
Torrey's photos from [https://flic.kr/s/aHskrE55NX Shanghai] 

 
 
 
 

== Photos from Hacker Trip to China 2014==
<gallery>
File:HTTC2014WelcomeHackers.jpg
File:HTTC20143Nod_b.jpg
File:HTTC2014AiWeiWei.jpg
File:HTTC2014BeijingLGBTcentre.jpg
File:HTTC2014Brooms.jpg
File:HTTC2014CableFactory.jpg
File:HTTC2014ChaiHuo.jpg
File:HTTC2014GiantSewing.jpg
File:HTTC2014Huaqianbei.jpg
File:HTTC2014IEIK2014.jpg
File:HTTC2014SeeedStudio.jpg
File:HTTC2014Shanghai.jpg
File:HTTC2014Tianjin.jpg
File:HTTC2014Tienanmen.jpg
File:HTTC2014TrainConvenienceStore.jpg
File:HTTC2014TsinghuaMakersDay.jpg
File:HTTC20143Nod.jpg
File:HTTC2014XinCheJian.jpg
</gallery>

Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157646894397704/ Beijing, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157648975298719/ Shanghai, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157648981933060/ Shenzhen, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649396351315/ Kunshan, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649148594118/ Shanghai (2), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649146775640/ Beijing (2), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649146987360/ Tianjin, Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157647372474753/ Beijing (3), Nov-2014] 
Mitch's photos from [https://www.flickr.com/photos/maltman23/sets/72157649287546450/ Singapore, Dec-2014] 

== You will Need a Chinese Visa!! ==
To go to China, you needed to get a visa!

Everyone should get a multiple-entry Tourist L visa (if you only get a single-entry visa, you'll be fine, but you won't have as many options, such as going in and out of Shenzhen to Hong Kong).

* And to get a visa, you need to have a passport that is valid ''at least'' 12 months after you planned to fly away from China (so, e.g., if you are leaving China on 28-October-2017, then your passport needs to be valid through 27-October-2017). Your passport must also have at least ''one entirely blank page''.

* You also need:
** a printout of a filled-out [http://www.china-embassy.org/eng/visas/fd/W020130830801798289342.pdf Visa Application Form V. 2013 of the People's Republic of China] (after we have everything we need I'll email you my filled out form as an example to follow).
** a copy of the information pages of your passport.
** a copy of your most Chinese visa (if you have been to China before).
** one 2"x2" recent color photo (not a printout).
** a screenshot or printout of hotel reservation confirmation (I'll email this to you when I have this).
** a copy of your airline tickets (both to and from China).

* For US citizens, the visa cost $140 (much cheaper for other nationalities). Starting this year, US citizens can get a multiple-entry visa, good for 10 years. We should all apply for a Tourist L visa.

You can pay the fee by Visa, MasterCard, Money Order, Cashier's Check or Company Check. ''Cash or Personal checks are not acceptable.''

To get a visa, you can go to your local Chinese consulate. No appointment is required. You go in one day, and it will be ready for pick up 4 business days later. My experience is that it takes about an hour the first day, and takes only a few minutes to pick up the visa a few days later. (2 to 3 business-day and 1 business day/same-day express service is available for $20 or $30.) 
''NOTE: The Chinese consulates are all closed for holidays on: 27-30 January, 29-30 May, 30-May, 9-June, 4-July, 4-September, 2-October, 9-October and other dates: 
[http://www.chinaconsulatesf.org/eng/lszj/t1424287.htm 2017 Chinese Consulate Holiday Schedule]''
 
(Citizens of US and Europe ''do not'' need a separate visa for Hong Kong.)
 

= Previous Noisebridge China Trips =
''If you're curious about the previous Noisebridge China Trips, they have their own wiki pages:'' 
[[ChinaTrip|Hacker Trip To China 2009]] 
          That first Noisebridge China Trip was inspired by Bunny Huang's [http://www.evilmadscientist.com/article.php/shenzhen/print "geek tour"].
 
[[NoisebridgeChinaTrip2|Hacker Trip To China 2011]]
 
[[NoisebridgeChinaTrip3|Hacker Trip to China 2013]]
 
[[NoisebridgeChinaTrip4|Hacker Trip to China 2014]]
 
[[NoisebridgeChinaTrip5|Hacker Trip to China 2015]]
 
[[NoisebridgeChinaTrip6|Hacker Trip to China 2016]]

--[[user: maltman23 | Mitch]].

= People interested in going on the Hacker Trip to China #7, 2017: =


'''Below is a list of people interested in going on this year's Hacker Trip To China.'''
 


'''You do not need to be a member of Noisebridge to go on this trip!'''
 

'''Please email me if you have any questions, or if you would like to meet up with us on the trip:''' 
''mitch *AT* CornfieldElectronics *DOT* com''

The trip is limited to 20 people total (including Mitch) 
-- the first 19 people (after Mitch) who are either there already, or who bought tickets to meet in our Trip's starting city (tentatively Shanghai) on or before 11-October-2017 are the people who are in this Trip        (which probably means flying away from home on or before 10-October) 


Note: Many people have gotten good deals on their plane fares (including me) with the help of my friend Vlad at:        [http://www.flystein.com/ Flystein] Feel free to email me, and I'll send your email to Vlad, who will be happy to help you with your flights.
 

{| style="color:green; background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"
!
! Name
! Purchased flight?
! Flight info
|-
|1
|[[user: maltman23 | Mitch Altman]] (Noisebridge, San Francisco, USA)
|align="center"|YES
|Arrive: Hong Kong on 6-Oct at 17:10 -- flight CX254 (from LHR)
|-
|2
|Robert Fitzsimons (TOG, Ireland)
|align="center"|YES
|Arrive: Hong Kong on 8-Oct at 15:25 -- EK382 (from DXB); Depart: Shanghai at 00:05 on Oct 29th (Emirates 8303)
|-
|3
|Noah O'Donoghue
|align="center"|YES
|Arrive: Hong Kong on 8-Oct
|-
|4
|[[user: keymistress | Gloria Chiang]]
|align="center"|no
|Arrive: 'Beijing on (date TBD)
|-
|5
|[[user:juul|Marc Juul]]
|align="center"|no
|Arrive: Beijing on (date TBD)
|-
|6
|Anthony Liekens (Open Garage, Belgium)
|align="center"|no
|Arrive: ''Wants to tag along in Shenzhen''
|-
|7
|Rafael Câmera Santos (Fazedores.com, Brazil)
|align="center"|no
|Arrive: Shenzhen or Hong Kong on (date TBD)
|-
|8
|Jan Marloth (fablab munich, Germany)
|align="center"|no
|Arrive: Shanghai? on (date TBD)
|-
|9
|[[user: feklee | Felix E. Klee]]
|align="center"|no
|Arrive: Consider traveling by ground from Berlin
|-
|10
|[[user: mrericboyd | Eric Boyd]]
|align="center"|no
|Arrive: will arrive in Hong Kong and join for entire trip
|-
|11
|freeman murray
|align="center"|no
|Arrive: ''oct 8, Hong Kong''
|-
|12
|[[user: sumukh | Sumukh Shetty]]
|align="center"|no
|Arrive: '''8th October HK, join for the entire trip''
|-
|13
|Jonas S Karlsson
|align="center"|will be in hk
|Arrive: ''hk''
|-
|14
|''Quijano Flores -- NEED EMAIL ADDRESS''
|align="center"|no
|Arrive: ''oct 8, Hong Kong''
|-
|15
|Ruth Grace Wong
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|16
|''Olivier de Saint-Hubert -- NEED EMAIL ADDRESS''
|align="center"|no
|Arrive: ''TBD''
|-
|17
|[[user: scitechindian | SYED JUNAID AHMED]] (Makers Hive, AndhraPradesh, INDIA)
|align="center"|no
|Arrive: ''TBD''
|-
|18
|Mark Hellar
|align="center"|no
|Arrive: 'oct 8, Hong Kong''
|-
|19
|Svein Berge
|align="center"|no
|Arrive: ''TBD''
|-
|20
|[[user: Rahulrajan| Rahul S Rajan]] (Kerala Startup Mission, India)''
|align="center"|no
|Arrive: ''TBD''
|-
|21
|Sasha Iatsenia
|align="center"|no
|Arrive: ''TBD''
|-
|22
|''Gene Brock''
|align="center"|no
|Arrive: ''Hong Kong, Sept''
|-
|23
|[[user: robbintt | Trent]]
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|24
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|25
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|26
|''your name here''
|align="center"|no
|Arrive: ''your arrival date and city here''
|-
|}

[[Category:Travel]]
[[Category:Projects]]