Jump to navigation Jump to search
Revision as of 17:32, 21 February 2015 by Mattsenate (removes google doc link, adds link to wiki page)
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 a Responsibilibuddy aka "Omni point person" for an event.
- Volunteer working group members need:
- User accounts to access two Wordpress instances for calendaring and booking (event request):
- Subscriptions to two mailing lists:
- 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 through our event request form at https://omnicommons.org/occupy are posted to the booking mailing list.
- Event Request Form
- Requests are submitted at https://omnicommons.org/occupy
- Requests can be found in the 'Pending' queue: https://omnicommons.org/occupy/wordpress/wp-admin/edit.php?post_status=pending&post_type=event
- Be aware that if you accidentally approve a 'pending' event, an email will be sent to the event requester! Please send an update email if you approve an event by mistake!!!
- When requests are approved, members of the working group approve and publish the event on https://omnicommons.org/occupy
- On the other hand, https://omnicommons.org/calendar is a global aggregator, pulling event feeds from /occupy/, http://sudoroom.org/calendar, http://bayareapublicschool.org/calendar, etc.
- 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.
- Attend Regular Meeting Sat @ 1pm
- Working group members go through all remaining pending events and self-assign to follow up with event requesters.Follow along with the list for a bit and you'll see how we proceed with people.
- Consider syncing the calendar feeds from /occupy/ to /calendar/ as described above.
- We have a general pattern of cc'ing the commons email list when corresponding with people seeking to book events, for sake of transparency and decentralizing responsibility.
- Read the Documentation, Share with Requesters
- 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.
- Approve, Publish, Sync to main Omni Calendar
- 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).