Meeting Notes 2010 01 12

From Noisebridge
Revision as of 15:15, 12 January 2010 by SpammerHellDontDelete (talk | contribs) (→‎Discussion items: adding summary of mailing list discussion)
Jump to navigation Jump to search

Crew

Moderator:

Note-Taker:

Attendee Count:

Officers:

Rollcall

Preflight Checklist

Please set your cell phones to vibrate.

Go get the membership binder.


Agenda Items

Announcements

Introduction and Names

What Noisebridge is about

Treasurer's Report

Very brief primer on Noisebridge consensus process

There is a consensus process...


Membership binder

What's Going On at Noisebridge

One short sentence about each of the following:

Weekly
  • Circuit Hacking Mondays (7PM, 2169)
  • Python Mondays (6:30 PM, 2169)
  • Project Euler now on Tuesdays at 7:00 p.m.
  • SCoW craft group - Wednesdays at 7PM
  • GameDevelopment - Wednesdays at 8PM, back from Berlin and 2010 class is in session
  • Shop Friday still plans to come back when the shop is done.
  • Sensebridge and the EEG group - Sundays at afternoonish (1-2ish) - come to try brain scanning
  • Spacebridge - Sundays at 5PM planning meeting this Sunday to decide on payload budget on
  • Where will we launch from? Lots of ideas. There's size limits for payloads but everyone interested should discuss afterwards.
  • Knots Go and Locks - Sundays 3PM

Project Updates

2169 Mission

  • Electrical:
  • Library:
  • Kitchen:
  • Network:
  • Heat:
  • EE lab:
  • Darkroom
  • Proposal:

Noisecloud

Noisebridge now has server power available. To find out more about the server access, ask Dr. Jesus.

26C3 debrief

Discussion items

How do we want to handle the NB logo on the wiki?

Notes from mailing list discussion

Randomizer function

  • Need better randomizer function

Possible wiki configurations:

  • Status quo (orig black and red circuit-like logo on all pages)
  • Randomizer from pool on all pages
  • Randomizer from pool on all internal pages, orig logo on index
  • Some other variant of mixed logos, may require someone committing to code up the implementation

Possible pool handling:

  • Public
  • Public upload somewhere, added to pool by ops
  • Public upload somewhere, some other approval method