Open Source Comes to Campus/In a Box: Difference between revisions

no edit summary
imported>Shauna
(Created page with " 1. Logistics 2. Curriculum 3. Publicity 4. Staff 5. Sponsorship")
 
imported>Shauna
No edit summary
Line 1:
Open Source Comes to Campus '''In a Box''' is our attempt to make this event easy for other people to adapt and run.
 
If you're interested in working with us to run an event, please [http://openhatch.readthedocs.org/en/latest/community/contact.html contact us] and tell us so! Probably the best route for this particular query is email.
 
(If you'd like to take these materials and go do your own thing, that's fine too, but the rest of this page assumes you'd like our remote support.)
1. Logistics
 
2. Curriculum
We've done a lot of work to document our process. Here's what we have to offer you:
3. Publicity
 
4. Staff
2. ===== Curriculum=====
5. Sponsorship
 
You can find the full curriculum for Open Source Comes to Campus on the [[Open_Source_Comes_to_Campus/Curriculum | Curriculum]] page. All of the activities have the materials we use available, and many have instructor guides/walkthroughs as well. We're beginning the process of adding screencasts/videos for some of our materials as well.
 
We're happy to talk with you at length about the curriculum and do trainings for any activities or sections you don't feel comfortable with.
 
1. =====Logistics=====
 
There are a number of logistical hurdles when planning an event, from finding space and making sure you have the right equipment to ordering the right amount of food. We keep these logistics organized via a [https://drive.google.com/?tab=mo&authuser=0#folders/0B4HP1ey91UqPb1RrN25YOFA4V3c shared folder] which you can copy for your event. The [[https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Logistics | Logistics]] page has a bunch of advice as well (and is referenced several times from the overview documents in the shared folder.
 
If you find any of this documentation confusing or insufficient, we'll be happy to answer all your questions (and we'll use your feedback to improve our process!)
 
3. =====Publicity=====
 
We'll provide you with a customizable [[Open Source Comes to Campus/Logistics/Publicity Website | publicity website]] as well as template [https://github.com/openhatch/open-source-comes-to-campus/tree/master/flyers/publicity_flyer_templates flyers] and template [https://drive.google.com/?tab=mo&authuser=0#folders/0B4HP1ey91UqPdkhaWDF1U2dhYzQ emails]. We're happy to help if you have additional ideas for publicity.
 
=====Staff=====
 
One of the most important parts of a successful event is making sure you have friendly, knowledgeable, enthusiastic staff. We have a large network of OpenHatch fans and volunteers who we'll ask to staff your event, and we'll help you [[Open_Source_Comes_to_Campus/Logistics#How_do_you_find_staff.3F find new volunteers]] as well.
 
We'll also support you with a number of remote staff, including:
* Throughout the event, Asheesh and/or Shauna will be available remotely
* During the contributions workshop, we'll have maintainers of [[OpenHatch_affiliated_projects | selected projects]] available to help guide attendees through contributing to said projects via IRC.
* There are pros and cons to doing the career panel remotely. If you decide you want to do the career panel via videoconference, we can hook you up with some amazing people working in open source who will participate.
 
5. =====Sponsorship=====
 
Open Source Comes to Campus has relationships with sponsors who frequently cover the cost of food and/or travel. It is highly likely, though not guaranteed, that those sponsors will be willing to do the same for your event.
 
 
Please note that you don't have to follow our methods or curriculum exactly to run an Open Source Comes to Campus event! We're happy to see you customize and experiment.
Anonymous user