Difference between revisions of "Open Source Comes to Campus/Curriculum"

From OpenHatch wiki
Jump to navigation Jump to search
imported>Shauna
imported>Shauna
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  +
The following is a list of activities in roughly the order we run them at an event. (To see our typical schedule, see the [[Open Source Comes to Campus/Logistics/Schedule | Schedule]] page.)
If you're looking for help with the logistics of running an OSCTC-type event, see [[OSCTC_logistics | here]].
 
   
 
__toc__
 
__toc__
Line 5: Line 5:
 
==Computer Setup==
 
==Computer Setup==
   
  +
This starts off the day. Direct attendees to [[Open_Source_Comes_to_Campus/Curriculum/Laptop_setup |the computer setup page]] and have mentors walk around and see if they're getting stuck.
See [[Computer setup | the computer setup page.]]
 
   
 
==Open Source Communication Tools==
 
==Open Source Communication Tools==
   
  +
[[OSCTC/Tools | The tools lecture]], which also currently includes a "What is Open Source?" component, aims to familiarize students with tools like IRC, issue trackers, mailing lists, and version control through several activities.
You can see the current and past versions of this presentation [[OSCTC/Tools | here]].
 
   
 
==Learning Git==
 
==Learning Git==
   
You can see the current and past versions of this presentation [[Open_Source_Comes_to_Campus/Practicing_Git | here]].
+
This is a hands-on activity which teaches version control, generally, and git via github specifically. You can see the current and past versions of this presentation [[Open_Source_Comes_to_Campus/Practicing_Git | here]].
   
 
==Career Panel==
 
==Career Panel==
   
  +
There are several possible options for the [[Open Source Comes to Campus/Curriculum/Career Panel | career panel]].
See also: [[OSCTC career panel]].
 
   
 
==History and Ethics of Free Software==
We aim for four panelists representing a diversity of open-source jobs. For example, past panelists have included people who work for [http://www.redhat.com/ Red Hat] [http://loft.bocoup.com/ BoCoup Loft] [http://sunlightfoundation.com/ the Sunlight Foundation] and [http://www.personalgenomes.org/mission.html the Personal Genome Project], as well as freelancers.
 
   
  +
This activity has been mostly omitted from recent Open Source Comes to Campus events - mostly for time issues, but also because we think it needs a lot of work.
We start off by asking each person to introduce themselves, their current occupation, and their current employer and to talk very briefly about how that work relates to open source.
 
   
  +
If you'd like to take a look, it's [[Open Source Comes to Campus/Curriculum/History and Ethics of Free Software | here]].
Then - questions! Potential questions include:
 
* How did you get started in open source?
 
* What opportunities are out there for college students? And do you have any other advice specific to college students?
 
* Do you have advice on what to do when approaching a project for the first time?
 
* What obstacles have you faced in open source? How have you addressed them?
 
* What business models are there for open source?
 
* What are some non-programming contributions you've made?
 
* What's your favorite open source project?
 
* Who's the coolest person you've met doing open source stuff?
 
   
  +
(If you want to help improve it, that would be swell.)
We typically do the career panel just before lunch so that attendees can socialize with panelists immediately afterwards.
 
   
 
==Contributions Workshop==
Make sure Google Summer of Code, GNOME Outreach Project for Women, and any local opportunities are mentioned!
 
   
  +
The Contributions Workshop is the part of the day where students begin making contributions to FOSS projects. If there is time, it may make sense to include some version of the [[Open_Source_Comes_to_Campus/Curriculum/Finding_a_Project | Finding a Project]] demo/activity. Finding a Project can be run as a demo, a student activity, or both. If both, we recommend introducing the activity, having a mentor demo it by walking through it at the front of the room/on the projector, and then having the student do it. We recommend having the students do the activity in pairs or small groups.
==Ethics and History of Free Software==
 
   
  +
=== The workshop itself ===
The tried-and-mostly-true version of this section is a lecture: [[/Ethics_history_talk|Ethics history talk]].
 
   
  +
For the workshop itself, one of the organizers introduces and explains that some of the mentors at the event have open source projects they maintain or contribute to and that students can work in small groups to contribute to those projects. The mentors then take 2-5 minutes to give a brief overview of their project and the types of tasks students can work on. The organizer assigns different mentors to different spots in the room and writes down the layout on the board/displays it on the projector so that students can find a group. The organizer should also include a link to [https://openhatch.org/wiki/First_Tasks first tasks], [https://openhatch.org/wiki/Additional_tasks additional tasks] or whatever resource is being used for the event to keep track of projects.
The more interactive, more un-tested version of this section is an activity: [[history and ethics activities]]
 
   
  +
If students do not want to join a specific project, they should join the "self-guided" group. This group of students will have one or more mentors who will help them find their own projects, building on the work done in the Finding a Project activity (if that activity was done).
==Contributions Workshop==
 
   
 
=== Wrap up ===
[https://openhatch.org/wiki/First_Tasks Here is the link for the Princeton event.]
 
   
  +
After one hour of the workshop, the organizer will lead the wrap up. Often, the workshop will continue after the wrap up. If that's the case, make very, very clear that students are welcome to stay and keep working.
==Wrap Up==
 
   
  +
During the wrap up:
These can vary, based on your event. We often:
 
   
  +
* Students report on their progress so far
* ''Ask attendees to share their successes''. Find a few people (perhaps 5) to stand up and speak for a minute or two about what they accomplished during the day.
 
  +
* Organizers talk about opportunities to follow up:
  +
** Future open source events at the school
  +
** Future open source events at the general area
  +
** [https://openhatch.org/wiki/Opportunities General FOSS opportunities]
  +
** things that OpenHatch is doing
  +
* Organizers ask students to fill out the exit survey
   
  +
==Wrap Up==
* ''Get attendees to fill out your exit survey''. Typically, you should plan your exit survey in advance of the event. At the wrap-up, you can use a projector and project a URL of the exit survey (preferably shortened with a meaningful name, using a service like http://bit.ly/ or http://smarturl.it/ ).
 
 
* ''Thank people''. Sponsors! Staff! And don't forget the attendees - they are there! You are glad they are there.
 
 
* ''Hand out tokens of appreciation'', if you can. Attendees often love to receive T-shirts, books, stickers.
 
   
  +
Some notes on how we do our wrap ups can be found [[Open Source Comes to Campus/Curriculum/Wrap up | here]].
* Follow up:
 
** Tell attendees to expect a follow up email and an invitation to join the alumni list (if you have an alumni list) and/or the general OpenHatch mailing list.
 
** Let them know about follow up events. If this is obvious -- like inviting people to a "project night" after an introductory workshop -- great! Make sure to share that recommendation, and do so with high clarity. Perhaps put the URL on a projector, and give people 90 seconds to check their calendars and sign up for it. If the follow-up methods are less obvious, think harder: for an open source outreach event, are there conferences nearby that are coming up? Is there a programming user group that welcomes newcomers that might be a good fit? Mention them, because attendees new to the community are likely to have never heard about them.
 
** Encourage attendees to keep hanging out on IRC, keep doing training missions and to keep working on the bugs from our bug tracker.
 
** Remind them about programs like GSoC and GNOME outreach.
 
   
   

Latest revision as of 15:31, 21 April 2014

The following is a list of activities in roughly the order we run them at an event. (To see our typical schedule, see the Schedule page.)

Computer Setup

This starts off the day. Direct attendees to the computer setup page and have mentors walk around and see if they're getting stuck.

Open Source Communication Tools

The tools lecture, which also currently includes a "What is Open Source?" component, aims to familiarize students with tools like IRC, issue trackers, mailing lists, and version control through several activities.

Learning Git

This is a hands-on activity which teaches version control, generally, and git via github specifically. You can see the current and past versions of this presentation here.

Career Panel

There are several possible options for the career panel.

History and Ethics of Free Software

This activity has been mostly omitted from recent Open Source Comes to Campus events - mostly for time issues, but also because we think it needs a lot of work.

If you'd like to take a look, it's here.

(If you want to help improve it, that would be swell.)

Contributions Workshop

The Contributions Workshop is the part of the day where students begin making contributions to FOSS projects. If there is time, it may make sense to include some version of the Finding a Project demo/activity. Finding a Project can be run as a demo, a student activity, or both. If both, we recommend introducing the activity, having a mentor demo it by walking through it at the front of the room/on the projector, and then having the student do it. We recommend having the students do the activity in pairs or small groups.

The workshop itself

For the workshop itself, one of the organizers introduces and explains that some of the mentors at the event have open source projects they maintain or contribute to and that students can work in small groups to contribute to those projects. The mentors then take 2-5 minutes to give a brief overview of their project and the types of tasks students can work on. The organizer assigns different mentors to different spots in the room and writes down the layout on the board/displays it on the projector so that students can find a group. The organizer should also include a link to first tasks, additional tasks or whatever resource is being used for the event to keep track of projects.

If students do not want to join a specific project, they should join the "self-guided" group. This group of students will have one or more mentors who will help them find their own projects, building on the work done in the Finding a Project activity (if that activity was done).

Wrap up

After one hour of the workshop, the organizer will lead the wrap up. Often, the workshop will continue after the wrap up. If that's the case, make very, very clear that students are welcome to stay and keep working.

During the wrap up:

  • Students report on their progress so far
  • Organizers talk about opportunities to follow up:
    • Future open source events at the school
    • Future open source events at the general area
    • General FOSS opportunities
    • things that OpenHatch is doing
  • Organizers ask students to fill out the exit survey

Wrap Up

Some notes on how we do our wrap ups can be found here.