Difference between revisions of "Booking System"

From Omni Commons
Jump to navigation Jump to search
m
Line 16: Line 16:
** [https://omnicommons.org/wiki/File:Omni_Events_Simple_Contract.pdf Simple Contract for small, quiet events]
** [https://omnicommons.org/wiki/File:Omni_Events_Simple_Contract.pdf Simple Contract for small, quiet events]
** [https://docs.google.com/document/d/1SEaPQbqwt6ezxqq1PQw4duMVlkqxQAdHhQI28vSWuuU/edit?usp=sharing Long Contract for large and/or loud events]
** [https://docs.google.com/document/d/1SEaPQbqwt6ezxqq1PQw4duMVlkqxQAdHhQI28vSWuuU/edit?usp=sharing Long Contract for large and/or loud events]
* See the [[Calendar_System]] page for instructions on adding events to the /calendar/ instance. Events can be directly added if they're sponsored by a member collective (eg; as a sudo member I can sponsor an event happening in the ballroom and add it directly if there are no conflicts).
* See the [[Calendar System]] page for instructions on adding events to the /calendar/ instance. Events can be directly added if they're sponsored by a member collective (eg; as a sudo member I can sponsor an event happening in the ballroom and add it directly if there are no conflicts).

Revision as of 01:18, 18 February 2015

This page outlines how our booking system works for those in the Commons working group.

Check out this guide which covers most of the basics of being an Omni point person for an event: https://docs.google.com/document/d/1fsm4dn4NHRl8D9mYYKDQAhF-IHMsOjRM-MVnnH_lXUk/edit

  • Booking 'agents' have accounts to two Wordpress instances, /calendar/ and /occupy/, and are on two mailing lists - commons and booking (@lists.omnicommons.org). Events submitted at omnicommons.org/occupy are posted to the booking mailing list. The commons mailing list is for discussion, inquiries, feedback from the rest of the group, and discussion of issues pertaining to the commons.
  • Events submitted at https://omnicommons.org/occupy sit in the 'Pending' queue until someone from the working group approves and publishes it. Omnicommons.org/calendar is a global aggregator, pulling event feeds from /occupy/, sudoroom.org, and bayareapublicschool.org.
  • Each Saturday at 1pm, we go through all remaining pending events and self-assign to follow up. Follow along with the list for a bit and you'll see how we proceed with people.
  • Events published in the /occupy/ calendar are pulled by /calendar/ every 24 hours, and so will not show up right away. You can manually sync the BAPS, Sudo, and Occupy calendars in /calendar/ under Events -> ESS Feeds -> Syndication and pressing the blue cloud associated with the calendar you want to sync.
  • We have a general pattern of cc'ing the commons list when corresponding with people seeking to book events, for sake of transparency and decentralizing responsibility.
  • Check out our rental policy and fee structure to learn about our sliding-scale model. Point people to this page and always ask what they can afford to pay, making our costs clear. At the least, for free events for the cause, ask folks to pass the hat.
  • We ask that folks having events in the space take their trash out with them, and prep and clean the ballroom if they're using that space. Make sure they read the Ballroom Prep and Cleaning Guide.
  • For Disco Room events/rehearsals, we ask that renters sweep and dry mop after use. Mops are available in the Disco Room.
  • For paid ballroom events, we ask people to sign a contract, a waiver and a 50% deposit three weeks prior to the event. There are two versions of the contract: one for large (~50+ people) events, the other for smaller, quiet events.
  • See the Calendar System page for instructions on adding events to the /calendar/ instance. Events can be directly added if they're sponsored by a member collective (eg; as a sudo member I can sponsor an event happening in the ballroom and add it directly if there are no conflicts).