Editing Open Source Comes to Campus/Logistics/Email templates

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
Here are current versions of our email templates.  I've tried to bold all sections you'll need to change but I may have missed some.
+
Here are current versions of our email templates.
  
 
__toc__
 
__toc__
Line 14: Line 14:
 
<p>We’re running an event on '''date''' at '''place''' and I was wondering if you would be interested in helping out!</p>
 
<p>We’re running an event on '''date''' at '''place''' and I was wondering if you would be interested in helping out!</p>
  
<p>The event runs from 10:00am to 5pm with coffee, bagels and socializing for a half hour beforehand.  (Staff won't need to show up at '''start of day''' sharp, but should be there by '''start of instruction''' if possible.)  You can find out more about the event '''at this url'''.</p>
+
<p>The event runs from 9:30am to 5pm with coffee, bagels and socializing for an hour beforehand.  (Staff won't need to show up at '''start of day''' sharp, but should be there by '''start of instruction''' if possible.)  You can find out more about the event '''at this url'''.</p>
  
 
<p>We're looking for people to help mentor attendees as they learn how to contribute to open source projects.  Instructors with a variety of backgrounds are welcome: while it's great if you have tons of experience using git and setting up development environments, we're also looking for people who've been involved with open source as non-programmers, who know a bit about picking bugs and submitting patches, or who just like to talk about their experiences with open source.</p>
 
<p>We're looking for people to help mentor attendees as they learn how to contribute to open source projects.  Instructors with a variety of backgrounds are welcome: while it's great if you have tons of experience using git and setting up development environments, we're also looking for people who've been involved with open source as non-programmers, who know a bit about picking bugs and submitting patches, or who just like to talk about their experiences with open source.</p>
Line 62: Line 62:
  
 
=== to CS departments/clubs ===
 
=== to CS departments/clubs ===
 
Alternate version: [[OSCTC Email Templates#CS Department Publicity Email]]
 
  
 
<blockquote>
 
<blockquote>
Line 79: Line 77:
  
 
=== to science departments/clubs ===
 
=== to science departments/clubs ===
 
Alternate version: [[OSCTC Email Templates#Non-CS Department Publicity Email]]
 
  
 
Using the template below, you can substitute in:
 
Using the template below, you can substitute in:
Line 125: Line 121:
 
</blockquote>
 
</blockquote>
  
=== Form day before reminder email ===
+
=== Form day before reminder email ====
 
 
<blockquote>
 
<p>Hi,</p>
 
 
 
<p>This is just a reminder about tomorrow’s Open Source Comes to Campus event.  The event starts at '''instruction start time''', but we’ll be at the space starting at '''event start time''' with fresh coffee and donuts for those who want to chat a bit beforehand.  </p>
 
 
 
<p>If you’d like to get an even earlier start, you can go ahead and make a GitHub account:</p>
 
https://github.com/</p>
 
GitHub is a popular tool for housing open software projects.  We’ll be talking a lot about how to use it tomorrow.</p>
 
 
 
<p>If you’d like more details about the event, you can check the website, or feel free to email me with any questions.  We’re looking forward to seeing you tomorrow!</p>  </blockquote>
 
  
 
=== Personalized one week out email ===
 
=== Personalized one week out email ===
 
<blockquote><p>Hi '''attendee name''',</p>
 
 
<p>You recently signed up for our Open Source Comes to Campus event, which will be running on '''date''' from '''time''' in '''place'''.  I’m emailing you to remind you about the event, and to confirm that you can come.  We provide breakfast and lunch to our attendees, so please RSVP -- we don’t want anyone to go hungry because we didn’t get enough food.  </p>
 
 
<p>'''Personalized section - see below.'''</p>
 
 
<p>If you don't know yet, that's okay!  We ask because, before the event, we collect bug reports and requests for our attendees to work on.  If we know what you’re interested in, we can find you some contributions to make to a project you’re particularly excited about.</p>
 
 
<p>We’re looking forward to seeing you on the '''date'''!  Again - it’s important that you let us know if your plans change and you can’t make it.  If you can only come for half the event, that’s useful for us to know as well.</p>
 
 
<p>Feel free to contact us ahead of time with any questions you may have.  And tell your friends about the event - we still have a few spots left!</p>
 
 
<p>best,</p>
 
<p>'''your name'''</p>
 
</blockquote>
 
 
Here are some examples for the personalized section:
 
 
For an attendee with no stated interests.
 
<blockquote>I’m also curious if there are any areas of open source that you’re particularly interested in.  There's pretty much every type of open source project you can imagine!  Music software, open source video games, educational software, tools for scientific research, browsers, operating systems, mobile apps, mobile platforms, online tools like wordpress or wikipedia.  </blockquote>
 
 
For an attendee who named areas of interest but not specific projects:
 
<blockquote>
 
I’m also curious if there are any areas of open source that you’re particularly interested in.  On the sign up form, you mentioned that you're interested in music software, games, and internet browsers.  Of these, do you have specific projects you use and would like to contribute to - for instance, Chrome or Firefox (browsers), LilyPond or RhythmBox or Audacity (music), Blender or Quake (games), etc?
 
</blockquote>
 
 
For an attendee who has named a project or projects(s) that is expansive and could use narrowing:
 
<blockquote>
 
You mentioned in your sign up survey that you're interested in contributing to Chrome, Firefox and Ubuntu.  These are all large projects with a huge list of reported bugs and requested features, so there's lots of ways for you to contribute.  Are there specific aspects of those projects you're interested in working on?  Mobile development, apps/plugins, the user interface, etc.?
 
</blockquote>
 
 
For an attendee who has named a single project and we don't actually need more detail:
 
<blockquote>
 
We asked about your interests because, before the event, we collect bug reports and requests for our attendees to work on.  If we know what you’re interested in, we can find you some contributions to make to a project you’re particularly excited about.  We'll take a look at Banshee for you, but if you come up with anything else you'd like to contribute to, let us know.  Either way, there will be a number of bugs/features/contributions for you to choose from at the event.
 
</blockquote>
 
 
For an attendee who mentioned a project with a difficult set up environment:
 
<blockquote>
 
You mentioned in your sign up survey that you're interested in contributing to Android and the Wikipedia backend.  Which of these would you say you're most interested in?  I ask because, before the event, we collect bug reports and requests for attendees to work on.  We're hoping we can find you some contributions to make that you're excited about!  Also - have you done any Android development?  Do you have a development environment already set up?  If not, it's probably best to focus on contributing to the other three projects, as in our experience Android setup can take up most of the afternoon.
 
</blockquote>
 
  
 
== Follow up email ==
 
== Follow up email ==
 
To attendees:
 
<blockquote><p>Thanks so much to everyone who came to the event on '''date'''!  '''Co-organizer (if applicable)''' and I and all of our staff had a great time meeting you and working with you throughout the day.</p>
 
 
<p>For those who couldn't make it - fear not!  The information presented at the workshop is also available online, [[OSCTC_Resources | on our wiki]].  We're not finished editing the materials, though, so if anything is confusing, please let us know.</p>
 
 
<p>We’ll be posting about the event soon on the OpenHatch blog.  If you attended but don't want your name or photo in a blog post, tell us and we'll make sure that your preferences are respected.</p>
 
 
<p>You've all been subscribed to our alumni mailing list.  This is a low traffic list that we'll use to keep you informed of opportunities such as internships and local open source meetups.  If for any reason you want to be taken off the list, just send me an email, or use the automated unsubscribe option at the bottom of list emails.</p>
 
 
<p>And as always, feel free to contact us with any questions you have.  You can reach us on IRC in #openhatch as well as at our personal email addresses or at hello@openhatch.org.</p>
 
 
<p>Again, thanks so much for working with us and taking the time to learn a little bit about open source.  We hope to keep working with you in the future.  :)</p>
 
</blockquote>
 
 
To attendees, with exit survey:
 
 
<pre>
 
Subject: Staying in touch, after Open Source Comes to Campus
 
 
Hi '''name''',
 
 
Thanks so much for coming to the Open Source Comes to Campus event last
 
Saturday! '''Co-organizer''' and I and all of our staff had a great time meeting
 
you and working with you throughout the day.
 
 
To help us know what went well at the event, and what we could improve,
 
we'd love if you could fill out this exit survey. We'll send you an
 
OpenHatch sticker in the mail if you do!
 
 
That's right, a FREE STICKER!
 
 
 
'''Exit survey URL'''
 
 
 
 
For those who couldn't make it - fear not! The information presented at
 
the workshop is also available online, on our wiki. We're not finished
 
editing the materials, though, so if anything is confusing, please let
 
us know. Find it here: https://openhatch.org/wiki/OSCTC_Resources
 
 
We'll be posting about the event soon on the OpenHatch blog. If you
 
attended but don't want your name or photo in a blog post, tell us and
 
we'll make sure that your preferences are respected.
 
 
You've all been subscribed to our alumni mailing list. This is a low
 
traffic list that we'll use to keep you informed of opportunities such
 
as internships and local open source meetups. If for any reason you want
 
to be taken off the list, just send me an email, or use the automated
 
unsubscribe option at the bottom of list emails.
 
 
And as always, feel free to contact us with any questions you have. You
 
can reach us on IRC in #openhatch on irc.freenode.net as well as at our
 
personal email addresses or at hello@openhatch.org.
 
 
Again, thanks so much for working with us and taking the time to learn a
 
little bit about open source. We hope to keep working with you in the
 
future.  :)
 
 
-- '''Your name'''.
 
</pre>
 

Please note that all contributions to OpenHatch wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see OpenHatch wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)