Anonymous user
Open Source Comes to Campus/Logistics: Difference between revisions
Open Source Comes to Campus/Logistics (view source)
Revision as of 02:46, 7 December 2013
, 10 years agono edit summary
imported>Shauna No edit summary |
imported>Shauna No edit summary |
||
Line 63:
===== How do you communicate with attendees before the event? =====
** The low-effort communication strategy we sometimes follow includes:▼
All the emails asterisked (*'d) below have templates which can can be found in [https://drive.google.com/?tab=mo&authuser=0#folders/0B4HP1ey91UqPb1RrN25YOFA4V3c the Template google docs folder]. The [[Open Source Comes to Campus/Logistics/Email templates | wiki version of the templates]] is deprecated, but you might find you like them better.
*** A [[Email_templates#Quick_confirmation_email | quick confirmation email]] within 24 hours of sign up▼
▲
* A one week out reminder email* with event details
* A day-before reminder email*.
A higher energy strategy involves asking attendees about projects their interested in using info from the sign up form. (See here for [[Email_templates#Personalized_one_week_out_email | details and templates]].) This strategy usually involves an extra 5-15 minutes of work per attendee but attendees are much more likely to show up (our experience is that personalized emails double-triple the attendance rate.) (Note: this strategy may need to be adjusted as we focus more on including projects which we already have relationships with.)
We recommend using strong language ("You *must* confirm if you want to attend on Sunday.") to ensure higher attendance.
=== During the event ===
===== How should I document the event? =====
'''Taking attendance''': the classic method of the paper and pen sign up form works well for us. It may be useful to assign a mentor to keep track of late arrivals and make sure they sign it.
'''Nametags''': nametags can be very useful for identifying students to follow up with (ie students who seem engaged and excited). I will frequently make a note of such students, and later match their names to their sign up info.
*** Upload them! Right now they just go into a public folder on Asheesh's flickr account but we're hoping to get a bit fancier soon.▼
▲
** Figure out ahead of time your food budget, and pick a place and make an order at least 24 (we aim for 48-72) hours ahead of time.▼
** Because our events start early and run a full day, we like to provide breakfast, lunch, and an afternoon snack. This usually costs between $200-350, depending on the size of the event. Less, if we order pizza for lunch. Your needs may vary, but we like to get:▼
===== How do we order food? =====
*** Breakfast: 1-3 boxes of coffee + milk + sugar, donuts/bagels/pastries, fresh fruit▼
*** Lunch: If possible, order sandwiches and salads rather than pizza. Try to provide vegetarian/vegan/dairy/gluten free options even if no attendees have listed it. Make sure to order beverages!▼
▲
*** Snack: Something light (people generally aren't that hungry or are willing to eat lunch leftovers) but fruit and chocolate never hurt anyone.▼
** When ordering: ▼
▲
*** Ask for plates, napkins, cups, and utensils (if necessary.)▼
*** Place the tip on the credit card you order with. If you need to adjust it, you can (presumably) do that after the fact. ▼
▲
*** Tell the vendor to bring things at least 20 minutes before the actual lunch time, if you have reason to believe that they might slip.▼
▲
▲
▲
===After the Event===
There is a template follow up email in [https://drive.google.com/?tab=mo&authuser=0#folders/0B4HP1ey91UqPb1RrN25YOFA4V3c the google docs folder]. Before sending it out, email your staffers and see if there's any information about their projects or organizations (or just opportunities they know about) that they'd like to see included.
*** We have a low traffic OSCTC alumni list that we add all attendees to as well.▼
** We strongly encourage writing up the event and posting it on your organization's blog. We'd also love to feature posts about OpenHatch-affiliated events on the OpenHatch blog!▼
We strongly encourage you to make note of attendees who seemed especially engaged, and follow up with them personally.
** For OSCTC events, we usually make two posts:▼
*** A summary-type post (unofficially titled the "bug report") - see [https://openhatch.org/blog/2013/umass/ this post]▼
=====How do I follow up with OpenHatch?=====
*** Infrequently Asked Questions, where we answer in depth novel questions we received at each event - see [https://openhatch.org/blog/2013/infrequently-asked-questions-wellesley-college/ this post]▼
We're happy to talk with you about running future events!
▲
▲
▲
|