Difference between revisions of "How to Run an Event"

From HacDC Wiki
Jump to: navigation, search
Line 1: Line 1:
Note: non-public events are strongly discouraged at HacDC.
+
Note: non-public events and charging participants more than the cost of materials are strongly discouraged at HacDC.
  
 
# Have an idea for an event. :)  If your event is a [[Running a Kit Build|kit build]] or [[LightningTalks Howto|lightning talks]], we have particular tips for you in addition to the ones on this page. If you're running a class, add the class description, including date and time and anything participants should bring, to [[:Category:Classes]].
 
# Have an idea for an event. :)  If your event is a [[Running a Kit Build|kit build]] or [[LightningTalks Howto|lightning talks]], we have particular tips for you in addition to the ones on this page. If you're running a class, add the class description, including date and time and anything participants should bring, to [[:Category:Classes]].
# Plan where and how to present your content. Options include the space, the [http://www.saintstephensdc.org/Meeting_Auditorium.html auditorium] (capacity: 200 people standing; 150 sitting in chairs in rows; 70 sitting at tables), the [http://www.saintstephensdc.org/Meeting_Church.html sanctuary] (capacity: 200 people sitting in pews; another 300 can stand or sit on floor), and the [http://www.saintstephensdc.org/Meeting_DiningRoom.html dining room] (capacity: 300 people standing; 220 sitting in chairs in rows; 175 sitting at tables).
+
# Plan where and how to present your content. Options include the space's meeting room or workshop, the [http://www.saintstephensdc.org/Meeting_Auditorium.html auditorium] (capacity: 200 people standing; 150 sitting in chairs in rows; 70 sitting at tables), the [http://www.saintstephensdc.org/Meeting_Church.html sanctuary] (capacity: 200 people sitting in pews; another 300 can stand or sit on floor), and the [http://www.saintstephensdc.org/Meeting_DiningRoom.html dining room] (capacity: 300 people standing; 220 sitting in chairs in rows; 175 sitting at tables).
 
# Assemble any necessary parts.
 
# Assemble any necessary parts.
 
# Schedule a time
 
# Schedule a time
Line 9: Line 9:
 
## If you're not sure when to have your event, consider posting a poll to help you decide. [http://doodle.com/ Doodle] is one free and easy service for doing so.
 
## If you're not sure when to have your event, consider posting a poll to help you decide. [http://doodle.com/ Doodle] is one free and easy service for doing so.
 
# Publicize!  
 
# Publicize!  
## '''Send an e-mail to HacDC's blabber@ (public) and members@ (members-only) mailing lists.''' 
+
## Send an e-mail to HacDC's blabber@ (public), members@ (members-only), and announcements@ mailing lists.
## '''Blog it (and add it to the event calendar) by [[Doing Things in Drupal|creating an event node in Drupal]].'''
+
## Blog it on our Wordpress site (if you don't have a login for [http://www.hacdc.org/wp-admin/ our Wordpress dashboard], contact info@hacdc.org).
 +
## Create a HacDC Meetup.com event, which automatically adds it to the [http://www.hacdc.org/calendar the HacDC event calendar]
 
## Consider notifying other groups whose members might be interested.  One place to check is [http://barcamp.pbwiki.com/DC-Area-Geeky-Groups this list of DC-area geeky groups].
 
## Consider notifying other groups whose members might be interested.  One place to check is [http://barcamp.pbwiki.com/DC-Area-Geeky-Groups this list of DC-area geeky groups].
 
## Get it listed on [http://dctechevents.com/ DC Tech Events] and, if possibly applicable to artists, send it to the [http://dorkbot.org/mailman/listinfo/dorkbotdc-blabber/ DorkbotDC Blabber] mailing list or let the overlord(s) know: dorkbotdc [at] dorkbot [dot] org.
 
## Get it listed on [http://dctechevents.com/ DC Tech Events] and, if possibly applicable to artists, send it to the [http://dorkbot.org/mailman/listinfo/dorkbotdc-blabber/ DorkbotDC Blabber] mailing list or let the overlord(s) know: dorkbotdc [at] dorkbot [dot] org.
 
# Post signs (e.g., on the red door) directing attendees who've never been to HacDC before.
 
# Post signs (e.g., on the red door) directing attendees who've never been to HacDC before.
 
# Run the event.  Share your knowledge.  Have fun.  [http://www.flickr.com/groups/hacdc/ Take some pictures.]
 
# Run the event.  Share your knowledge.  Have fun.  [http://www.flickr.com/groups/hacdc/ Take some pictures.]
## At the event, please tell the participants who aren't members about what HacDC is and ask them to consider joining or donating to us.
+
## At the event, please tell the participants who aren't members about what HacDC is and ask them to consider joining or donating to us. Not confident with your impromptu asking-for-money skills? Try our pre-scripted [[Spiel]].
 
# How did it go?  [http://hacdc.org/ Blog] it!  Have suggestions for next time?  Add them here!
 
# How did it go?  [http://hacdc.org/ Blog] it!  Have suggestions for next time?  Add them here!
  
 
[[Category:Event Planning]]
 
[[Category:Event Planning]]

Revision as of 12:36, 25 February 2013

Note: non-public events and charging participants more than the cost of materials are strongly discouraged at HacDC.

  1. Have an idea for an event. :) If your event is a kit build or lightning talks, we have particular tips for you in addition to the ones on this page. If you're running a class, add the class description, including date and time and anything participants should bring, to Category:Classes.
  2. Plan where and how to present your content. Options include the space's meeting room or workshop, the auditorium (capacity: 200 people standing; 150 sitting in chairs in rows; 70 sitting at tables), the sanctuary (capacity: 200 people sitting in pews; another 300 can stand or sit on floor), and the dining room (capacity: 300 people standing; 220 sitting in chairs in rows; 175 sitting at tables).
  3. Assemble any necessary parts.
  4. Schedule a time
    1. Use the church's calendar if you want to use the church's auditorium, dining room, or sanctuary.
    2. Use the the HacDC event calendar to choose a date and time. Please try not to overlap with other HacDC events. Also, please try to give potential participants at least a week's notice.
    3. If you're not sure when to have your event, consider posting a poll to help you decide. Doodle is one free and easy service for doing so.
  5. Publicize!
    1. Send an e-mail to HacDC's blabber@ (public), members@ (members-only), and announcements@ mailing lists.
    2. Blog it on our Wordpress site (if you don't have a login for our Wordpress dashboard, contact info@hacdc.org).
    3. Create a HacDC Meetup.com event, which automatically adds it to the the HacDC event calendar
    4. Consider notifying other groups whose members might be interested. One place to check is this list of DC-area geeky groups.
    5. Get it listed on DC Tech Events and, if possibly applicable to artists, send it to the DorkbotDC Blabber mailing list or let the overlord(s) know: dorkbotdc [at] dorkbot [dot] org.
  6. Post signs (e.g., on the red door) directing attendees who've never been to HacDC before.
  7. Run the event. Share your knowledge. Have fun. Take some pictures.
    1. At the event, please tell the participants who aren't members about what HacDC is and ask them to consider joining or donating to us. Not confident with your impromptu asking-for-money skills? Try our pre-scripted Spiel.
  8. How did it go? Blog it! Have suggestions for next time? Add them here!