Yar: copy from pad

2014-10-26T02:09:50Z

copy from pad

New page

thursday's meeting
* they specifically decided to limit commons wg to just disco room & ballroom because of uncertainty over what "other common areas" mean

we are responsible for a large growing amount of space. how to divvy up responsibilities for all those spaces?
* event bottom-liners
** some confusion over what responsibilities that entails
** how to help people take on that labor?
* what is the workload so far?
** liaising
** collecting checks
** cleaning
** being aware of conflicts and stewarding them and solving communication issues
** to interact with the confusing behind-the-scenes aspects of omni so one-off event folks don't have to
** should we pay someone to do that? "no..."

policies about pricing so we can be explicit on our "proverbial website"
* danny's "fee structure" - how to make that workable?
* right now everything is a sliding scale. member groups can schedule spaces for free and sponsor third-party events if they want to
* need to write more down instead of edit live
* action item: revise danny's document
* questions for each room: capacity? sound porousness? people walking through? the shoe question?
* statement of principles. these are the values we share, and we're especially seeking communities that share those values.
* state who we'd LIKE to see rather than just saying no to venture capitalists. will help a lot with outreach.

also clarify who's entitled to how much time in each space
* backspace plans to rent to other people outside who aren't practicioners
* a way for omni's calendar to send people to backspace?
* "there should be a master calendar that includes non-commonswg spaces"
* the new calendar system can accomodate partially open spaces, i.e. spaces that are only schedulable by the commonswg part of the time. like potentially parts of backspace and sudoroom.
* clustered interest areas emerging in the building - does the commons wg represent those or are there better ways?
* sound is also an issue. do events that need quiet have a right to block a loud event at the same time?

things to consider when developing the new calendar
* app can make sure loud & quiet events don't coincide
* the idea for the calendar app is to have a single URL that everyone visits first - both stranger and member groups. the UX will ask them all the relevant questions.

we are meeting at 10am next week!

Event:2014/10/25 Commons WG Meeting - Revision history

Yar: copy from pad