Editing Meeting Notes 2008 06 17

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 2: Line 2:
== Results ==
== Results ==
[[Image:Bylaws!.jpg|thumb|right|180px|We agreed upon our bylaws!]]
=== Main results: ===
=== Main results: ===
(See discussion below for how we got here.)
(See discussion '''to be added''' below for how we got here.)
Option 2 - Board + Members.
Option 2 - Board + Members.
Line 30: Line 29:
# Incorporation meeting - sign Articles, Bylaws, file with state
# Incorporation meeting - sign Articles, Bylaws, file with state
# Obtain bank account
# Obtain bank account
# Find a space, sign lease
# Find a space
# Throw party
# Throw party
=== How We Got There ===
These are partial notes on our four-hour-plus discussion. Please add or modify for accuracy as needed.
* Points brought up in favor of Option 1 over Option 2 included:
** Difficulty of obtaining 50%+1 of all members for major decisions (bylaws amendment involving Member rights, kicking out Board members), given that we have trouble gathering that many people for meetings now.
** Increased overhead in record-keeping involving Members
*** "Interested persons" for IRS purposes (e.g., we have to be aware of how we pay board members and Members, since the IRS may be concerned that we are using our non-profit status improperly)
*** Membership meetings must be noticed 10 days in advance
*** Bringing up new business not included in meeting notice needs 1/3 of all membership
** Perceived benefits for Option 2 not specific to Option 2
*** Listening to will of membership could be achieved through strong mission statement
*** Oversight relies on interested parties and culture of transparency ; Option 2 by itself would '''not''' prevent problems such as seen in Hackers On A Plane. The fix for problems of that kind is better governance and transparency in day to day operations.
** External bylaws do not need to reflect all details of internal governance
*** and in the case of consensus process, cannot reflect such details due to CA law
* Points brought up in favor of Option 2 over Option 1 included:
** Principle of Members electing Board and other Members
** Members can recall non-performing Board member
** Avoids self-perpetuating clique of Board members
** Option 2 "light" - we envision Member meetings (i.e., formal meetings, as defined by law) only for elections, plus cases where Members believe Board is taking the wrong tack and want to discuss (we envision that Members, along with other participants of Noisebridge, will be continually engaged in open dialog about issues  of interest and concern)
*** Day to day operations are up to Board + Officers, and in particular they can do things like negotiate a lease without needing to always have lease approved by all Members
** Greater investment of Members will tend towards more transparent culture, more oversight, therefore tend to avoid problems such as seen in Hackers On A Plane.
** External bylaws should closely as possible reflect internal governance
*** if we have members playing a large role in decisions, they should also be Members
* We briefly discussed an Option 1 with a large Board of Directors (all "Members" are "Directors")
** Pro: avoid some of the overhead of Option 2, keep principle of everyone in control
** Con: large board unwieldy even w/committees, Board members have duty of care, duty of loyalty, no one has any idea if we could get directors&officers insurance for such a thing
* We also briefly discussed having officers replaced by very small shell scripts. The point would be to effectively "unbundle" some of the powers of each officer, by having a legal entity that delegated some powers as needed to different persons (e.g. an "education president" and a "sysadmin president" getting powers as needed from a small shell script serving as board of directors.) The idea owes a debt to Charles Stross _Accelerando_. Unfortunately, California law does not appear to allow shell scripts to serve as directors. David M. pointed out that in Accelerando this trend leads directly to all "normal" humans (i.e. non posthumans) being unable to function successfully in the resulting economy and so they must all emigrate to Saturn.
'''Final positions:'''
(Thanks to Matt for his notes; the "counted as" come from there. Edit if you disagree with characterization.)
After exploring our options and discussing the pros and cons, this is roughly where we ended up:
* Noah Balmer felt strongly that Option 1 was preferable due to decreased overhead and to the problems that could result from apathetic Members in Option 2. Would not block if we decided to implement Option 2, but he would not vote for it and thought it was the wrong direction.
* Jake Appelbaum felt strongly that Option 2 was preferable due to principle of member control plus past bad experiences with Hackers On A Plane. David Molnar preferred Option 2 with the understanding that it would be "light" and membership meetings happen rarely, but would not block Option 1.
* Rachel could go either way, slightly preferred option 1, but counted as neutral.
* Andy could go either way, slightly preferred option 2, but counted as neutral.
* Matt could go either way, pointing out that we all want to focus on real hacking and not on law hacking, and counted as neutral.
* Mitch would not block either way, but preferred option 2, counted as option 2.
* Eec and Audrey abstained.
The decision was Option 2, with the clarification that the day to day running is handled by the Board and Officers. The Members have formal meetings rarely, mainly to elect Board and new Members.
We then discussed initial board members and initial officers. The results emerged without objections and are recorded above. Finally we talked about next steps and called it a night.
== Agenda & Pre-Meeting Notes ==
'''Bigass Bylaws Meeting!!'''
'''Bigass Bylaws Meeting!!'''

Please note that all contributions to Noisebridge are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see Noisebridge:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)