Open Source Comes to Campus/Curriculum: Difference between revisions

Content added Content deleted

Inline

Revision as of 15:05, 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 one or both of the "Finding a Project" activities.

Finding a Project Demo

Finding a Project Activity

Finding a Project activity.

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.

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.

@@ Line 29: / Line 29: @@
 ==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 one or both of the "Finding a Project" activities.
-The Contributions Workshop is constantly being improved upon.  Currently, it's pretty straightforward.
+==== Finding a Project Demo ====
-* One or more organizers presents the [[First Tasks]] page and explains how to use it.
-* Local project leads as well as remote maintainers (via hangout or something similar) explain their projects in 2-5 minutes.
-* Attendees start looking through and contributing to projects while local project leads get together in small groups with interested students.  The other project leads float.
-* After about 15-20 minutes, if any students are stuck (and some will be), they can do the [https://github.com/openhatch/open-source-comes-to-campus/blob/master/curriculum/handouts/FindingProjects_Student_Handout.odt Finding a Project] activity.
+==== Finding a Project Activity ====
-We're working on brainstorming additional activities for attendees who get stuck.  We're also planning to create a short guide for mentors to give them advice about how to approach students who need help but aren't asking for it (a common problem).
+[https://github.com/openhatch/open-source-comes-to-campus/blob/master/curriculum/handouts/FindingProjects_Student_Handout.odt Finding a Project] activity.
+=== 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.
+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
+** [https://openhatch.org/wiki/Opportunities General FOSS opportunities]
+** things that OpenHatch is doing
+* Organizers ask students to fill out the exit survey
 ==Wrap Up==