Events: Difference between revisions

From All Hands Active Wiki
Jump to navigation Jump to search
JoshW (talk | contribs)
removed broken links, copy.com now redirects to cahoots.com
 
(45 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Next in person meetup on this: Sunday, Nov. 3rd from 3:00pm to 5:30pm==
{{Outdated}}


==Establishing an Event Process==
==Events!==
So you want to run an event at / with AHA?
*[https://wiki.allhandsactive.org/Calendar AHA Events Calendar]
This document tries to cover all the basics for a simple one day event happening at AHA. '''This document is not meant to cover the intricacies of Summer Camp, building curriculum, doing a dry run for your class''', etc. There are many small details that go into running a successful event, hopefully this document will help cover the basics.


This document will help!
'''People who want to run an event''' at AHA should be able to do so with ease, and there should be someone at AHA who can help facilitate this in an efficient way.


Well, it will, when we fill it with stuff.
'''People who want to participate in an event''' at AHA should be able to find out what we are doing via our shop, staff, web site and other local / online means. An event description should give them everything they need to know. Our [https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform submission form] is one example of the  information we should have collected to form a solid description.


Observation: We run events at AHA, but there is no clear path to submitting, promoting, running, etc. There is no established guideline for doing so. This document here seeks to fix that.
==Needs / In Progress==
 
# Feel free to '''attach your name''' if you can help out with this!
==Needs==
# Feel free to attach your name if you can help out with this!
# A documented process for events
# A documented process for events
## Josh is looking into this
## That is this document.
## That is this document.
## Eventually this should be split into two documents:
## Eventually this should be split into two documents:
### One for people who wish to run an event
### One for people who wish to run an event
### One for people who handle the processing of events
### One for people who handle the processing of events
# [https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform A submission form]
# [https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform A submission form] '''(Larry)'''
## This has been created, now we need to:
## This has been created, now we need to:
### Clarify who the event staff are that this will notify via email
### Clarify who the event staff are that this will notify via email
### Clarify the process that event staff follow once they have been notified.  
### Clarify the process that event staff follow once they have been notified.  
#### This partially depends on the following items being resolved. But we shouldn't wait until then.
#### This partially depends on the following items being resolved. But we shouldn't wait until then.
# A process for handling payments
# A process for handling payments '''(Zach, Larry, Nate, Ken)'''
## Currently Paypal, and currently a PITA to setup for each event
## Currently Paypal, and currently a PITA to setup for each event
## Nate, Tyler, and Ken are currently looking in to this
# A process for handling events/registration/recurrence. '''(Larry, Nate, Ken)'''
# A process for handling events/registration/recurrence.
# A process for automating submission to multiple outlets, ie: Wordpress, Facebook, Google Calendar '''(Nate, Ken)'''
## Nate, Tyler, and Ken are currently looking in to this
# A process for automating submission to multiple outlets, ie: Wordpress, Facebook, Google Calendar
## Nate, Tyler, and Ken are currently looking in to this


==The Process==
==The Process==
# Someone wants to submit an event, they should have:
=== '''An idea for an event is formed''' (Anyone can do this)===
## A Name for the Event
# A Name for the Event
## A Date and Time for the Event
# A Date and Time for the Event
### [https://www.google.com/calendar/embed?src=allhandsactive%40gmail.com&ctz=America/Detroit Check the AHA Google Calendar] to find open slots
## [https://www.google.com/calendar/embed?src=allhandsactive%40gmail.com&ctz=America/Detroit Check the AHA Google Calendar] to find open slots
## A Description
# A Description
## Your contact Information
# Your contact Information
## General Requirements of Attendees
# General Requirements of Attendees
## General Requirements of AHA
## Age is good to know! If no age specified, we should make sure to note "All Ages Welcome" in our event description.
## Min. and Max. # of people you can handle attending
# General Requirements of AHA
## How much money AHA should Charge
# Min. and Max. # of people you can handle attending
# Once that's all figured out?
# How much money AHA should Charge
## [https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform Submit the event to AHA!]
=== '''The idea is submitted''' (Anyone can do this)===
# This submits the form to '''AHA Event Staff'''
# [https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform Submit the event to AHA!]
=== '''The idea is reviewed''' (AHA Director of Education)===
# Event staff should review this posting for
# Event staff should review this posting for
## Possibilities of double scheduling
## Possibilities of double scheduling
Line 51: Line 47:
### Do materials need to be purchased?
### Do materials need to be purchased?
## Is AHA available to fulfill any requested requirements?
## Is AHA available to fulfill any requested requirements?
# A confirmation email from AHA Staff should be sent to the individual within 48 hours.
# At this point in time, this process is not here for us to decide whether an event is appropriate for AHA. This process is to facilitate someone running an event at AHA.
## This should include any questions that may need answering
 
# Once all major questions have been resolved, the event should get posted, this may involve a series of steps. '''This process is being examined for possibilities of automating'''
=== '''A confirmation email is delivered to the submitter''' (AHA Event Staff)===
## Setting up payment processing method
# This should include any questions that may need answering
## Posting to internal sources:
=== '''The Event is Posted''' (AHA Event Staff)===
### AHA Google Calendar
- Tyler/Nate/Ken have some input some automation.
### AHA Website
# Setting up payment processing method
### AHA Facebook Page
## Online: At the All Hands Active event page for that event
### AHA Facebook Group
## In store: Set up Square Item (Works for Cash/Check/Credit/Debit)
### AHA Mailing List
## ???
### AHA Monthly Mailing Notice
# Posting to internal sources:
## Posting to external sources, ie:
## AHA Google Calendar First (Doesn't require images, payment, registration, etc.
### Arborweb
## [http://www.allhandsactive.com/events AHA Website]
### Craigslist
## [https://www.facebook.com/pages/AHA-All-Hands-Active/300100514925 AHA Facebook Page]
### Meetup?
## [https://www.facebook.com/groups/132903191962/ AHA Facebook Group]
### Mlive
## [https://groups.google.com/forum/#!forum/ahashop_members AHA Members Discussion List]
### Observer
## [https://groups.google.com/forum/#!forum/ahashop AHA Public Discussion List]
### AA Family Website
## [http://www.mailchimp.com AHA Announce List] (Mailchimp, ask Josh for login details)
## The teacher / leader of this class or workshop should be involved in the promotion of it. Ideally to communities that are more specifically related to the event.
# Posting to external sources, ie:
## Posting to physical media
## [http://www.arborweb.com Arborweb]
### Monthly Event Listing print outs
## [http://annarbor.craigslist.org Craigslist]  - Not actively using, maybe a good idea?
### Fliers / posters if appropriate
## [http://www.meetup.com Meetup] - Not actively using, maybe a good idea?
## [http://www.Mlive.com]  - Not actively using, maybe a good idea?
## [http://annarborobserver.com/articles/front_page.html Ann Arbor Observer]
## [http://www.annarborfamily.com/ Ann Arbor Family]
# The teacher / leader of this class or workshop should be involved in the promotion of it. Ideally to communities that are more specifically related to the event.
# Posting to physical media
## Monthly Event Listing print outs
## Fliers / posters if appropriate
=== '''Day of, but prior to event''''===
# Staff should have some way of knowing that an event is happening that day (Assuming we are open)
# Space should be cleared / cleaned up
# Any people using the space where the class will be held should be notified that an AWESOME event is happening that is SO awesome they might have to move.
=== '''During the event'''===
# Someone should be able to take money and point people to where the workshop is.
# Someone else (teacher/leader) should be able to handle people once they have paid.
=== '''After the event'''===
# Can we get feedback from the people who attended it?
# Can we get feedback from the teacher/organizer?
# Can we provide feedback to the teacher/organizer if appropriate?
 
==Resources==
'''(NEEDS UPDATING)''' 
 
[https://drive.google.com/folderview?id=0B9x4RIcqwUojN0RkNlY1SWpkVlk&usp=sharing Directory of Major Events] - Includes Template for the Printed List of Events]
 
[https://docs.google.com/spreadsheet/ccc?key=0AjFv57sTWhFPdDUzRFlKaENNMVNXMHRhWGdoTXFlLUE&usp=drive_web#gid=1 Event Submission Form Responses]
 
[https://docs.google.com/forms/d/1a7nY7qSNBjAJCO40QVSJhevIINNzoNkkFAvtni9hxcw/viewform Event Submission Form]
 
[https://docs.google.com/spreadsheet/ccc?key=0Atx4RIcqwUojdHAzNUppdFR0VnFRMUVJRV9tOEJ4c1E&usp=drive_web#gid=1 Previous Document for keeping track of events] Has some useful information, may no longer be useful
 
==Automation==
* Google calendar to Twitter -> When an event starts on Google Calendar Ifttt.com automation will publish a tweet. (allhandsactive email account)
* Google calendar to facebook page -> When an event starts on Google Calendar ifttt.com automation will post to the facebook page.
* Google calendar to facebook events -> Facebook doens't allow creating events via their API anymore. This is manual.
 
GAE Event manager (AHEM) Aha Event Management:
https://bitbucket.org/tsworman/ahaevents - Code
http://blog.novaslp.net/post/107096389283/above-is-the-user-workflow-for-an-end-user-who - AHEM running.

Latest revision as of 16:33, 30 October 2021


Notice
Notice
OUTDATED!:
The content of this page is outdated.
If you have checked or updated this page and found the content to be suitable, please remove this notice.


Events!

This document tries to cover all the basics for a simple one day event happening at AHA. This document is not meant to cover the intricacies of Summer Camp, building curriculum, doing a dry run for your class, etc. There are many small details that go into running a successful event, hopefully this document will help cover the basics.

People who want to run an event at AHA should be able to do so with ease, and there should be someone at AHA who can help facilitate this in an efficient way.

People who want to participate in an event at AHA should be able to find out what we are doing via our shop, staff, web site and other local / online means. An event description should give them everything they need to know. Our submission form is one example of the information we should have collected to form a solid description.

Needs / In Progress

  1. Feel free to attach your name if you can help out with this!
  2. A documented process for events
    1. That is this document.
    2. Eventually this should be split into two documents:
      1. One for people who wish to run an event
      2. One for people who handle the processing of events
  3. A submission form (Larry)
    1. This has been created, now we need to:
      1. Clarify who the event staff are that this will notify via email
      2. Clarify the process that event staff follow once they have been notified.
        1. This partially depends on the following items being resolved. But we shouldn't wait until then.
  4. A process for handling payments (Zach, Larry, Nate, Ken)
    1. Currently Paypal, and currently a PITA to setup for each event
  5. A process for handling events/registration/recurrence. (Larry, Nate, Ken)
  6. A process for automating submission to multiple outlets, ie: Wordpress, Facebook, Google Calendar (Nate, Ken)

The Process

An idea for an event is formed (Anyone can do this)

  1. A Name for the Event
  2. A Date and Time for the Event
    1. Check the AHA Google Calendar to find open slots
  3. A Description
  4. Your contact Information
  5. General Requirements of Attendees
    1. Age is good to know! If no age specified, we should make sure to note "All Ages Welcome" in our event description.
  6. General Requirements of AHA
  7. Min. and Max. # of people you can handle attending
  8. How much money AHA should Charge

The idea is submitted (Anyone can do this)

  1. Submit the event to AHA!

The idea is reviewed (AHA Director of Education)

  1. Event staff should review this posting for
    1. Possibilities of double scheduling
    2. Working out any monetary issues, ie:
      1. Is the teacher being compensated?
      2. Do materials need to be purchased?
    3. Is AHA available to fulfill any requested requirements?
  2. At this point in time, this process is not here for us to decide whether an event is appropriate for AHA. This process is to facilitate someone running an event at AHA.

A confirmation email is delivered to the submitter (AHA Event Staff)

  1. This should include any questions that may need answering

The Event is Posted (AHA Event Staff)

- Tyler/Nate/Ken have some input some automation.
  1. Setting up payment processing method
    1. Online: At the All Hands Active event page for that event
    2. In store: Set up Square Item (Works for Cash/Check/Credit/Debit)
    3. ???
  2. Posting to internal sources:
    1. AHA Google Calendar First (Doesn't require images, payment, registration, etc.
    2. AHA Website
    3. AHA Facebook Page
    4. AHA Facebook Group
    5. AHA Members Discussion List
    6. AHA Public Discussion List
    7. AHA Announce List (Mailchimp, ask Josh for login details)
  3. Posting to external sources, ie:
    1. Arborweb
    2. Craigslist - Not actively using, maybe a good idea?
    3. Meetup - Not actively using, maybe a good idea?
    4. [1] - Not actively using, maybe a good idea?
    5. Ann Arbor Observer
    6. Ann Arbor Family
  4. The teacher / leader of this class or workshop should be involved in the promotion of it. Ideally to communities that are more specifically related to the event.
  5. Posting to physical media
    1. Monthly Event Listing print outs
    2. Fliers / posters if appropriate

Day of, but prior to event'

  1. Staff should have some way of knowing that an event is happening that day (Assuming we are open)
  2. Space should be cleared / cleaned up
  3. Any people using the space where the class will be held should be notified that an AWESOME event is happening that is SO awesome they might have to move.

During the event

  1. Someone should be able to take money and point people to where the workshop is.
  2. Someone else (teacher/leader) should be able to handle people once they have paid.

After the event

  1. Can we get feedback from the people who attended it?
  2. Can we get feedback from the teacher/organizer?
  3. Can we provide feedback to the teacher/organizer if appropriate?

Resources

(NEEDS UPDATING)

Directory of Major Events - Includes Template for the Printed List of Events]

Event Submission Form Responses

Event Submission Form

Previous Document for keeping track of events Has some useful information, may no longer be useful

Automation

  • Google calendar to Twitter -> When an event starts on Google Calendar Ifttt.com automation will publish a tweet. (allhandsactive email account)
  • Google calendar to facebook page -> When an event starts on Google Calendar ifttt.com automation will post to the facebook page.
  • Google calendar to facebook events -> Facebook doens't allow creating events via their API anymore. This is manual.

GAE Event manager (AHEM) Aha Event Management: https://bitbucket.org/tsworman/ahaevents - Code http://blog.novaslp.net/post/107096389283/above-is-the-user-workflow-for-an-end-user-who - AHEM running.