Event:2015/11/27 Commons WG Hackathon

From Omni Commons
Revision as of 05:51, 28 November 2015 by Tunabananas (talk | contribs) (added notes from commons hackathon)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Omni Commons Commons Hackathon - 28 November 2015 Starts at 12pm @ Laura's place :)

Attendees

yar, jeremy, laura, jenny, julio, robb

gossip

  • lasted until 1:17pm

Announcements

Meeting Structure

  • Second Sundays
    • Full review of pending events for the following month & assigning point people
    • Link to event criteria?
  • All other meetings
    • Prioritize answering questions from event holders and orienting new volunteers
    • Check in on the week's upcoming events (calendar listing, point person(s), A/V needs, optional promoting on omni social media, contract & deposit, payment & invoicing)
  • Maybe one meeting a month could be dedicated just to onboarding new volunteers?

Responsibilibuddy / Point Person Responsibilities

  • Update https://omnicommons.org/wiki/responsibilibuddy - draft happening at https://pad.riseup.net/p/responsibilibuddy
  • Give accounts on /calendar/ and /occupy/ and sign up for mailing lists
  • Comms Checklist: Meet w/ event holder, go over any concerns/questions, iron out day-of logistics, create/send/sign contract, invoice for payment & deposit (Quickbooks), be present for entire event, return deposit up to 1 week after event
    • Meet: Can be done during a Commons WG meeting 1st, 3rd & 4th Sundays or independently
    • Concerns/Questions: See the FAQ for common questions and answers (todo: write an FAQ)
    • Day-of: Clean space, work out A/V logistics, anticipate concurrent events, provide doorperson if necessary
    • Contract: revise to be simpler
    • Invoice: Is there a Commons account for our Quickbooks?
  • Create a temporary keycard for recurring events
  • If event requires quality sound, let them know they can message sound@omnicommons.org to hire an in-house sound technician

contract

Event Request Form Improvement

  • point person detail on event request form (not useful) (jeremy will talk to laura or jenny)
  • update the rules (neighborhood, noise, limitations of space use, street restrictions) and have them be apparent in general information about having an event a the Omni
  • make sure autoresponse for booking the event is happening
    • emails are only sent when pending events are approved. there is no template for when events are submitted. A success message appears for users upon submission: "SUCCESS!!! You have successfully submitted your event. We (the all-volunteer Commons working group) review all requests on the second Sunday of the month. You will receive a response shortly after that. Please be patient, as we receive many requests every month. Thank you - we look forward to hosting you in the Omni Commons!"
  • new requests can all appear in one spreadsheet to make them easier to review
    • jenny: is the extra work to implement this worth it when we can also just look at 'pending events' in /occupy/?

Booking Process Walkthrough

Jenny will facilitate (if she works out the bugs in this new plugin first):

Dream Calendar System Brainstorm

Yar will facilitate:

Done Today

Action Items

Gratuitous Link Dump

end

  • please leave this here along with some whitespace :)