Open Source Comes to Campus/Training/Short Explanations

There are currently five training modules being developed. Here are brief descriptions for the purpose of reference.

Introduction to Open Source
The introduction to open source currently looks like this. You can see a self-guided version here. (It has been recommended that presenters actually read the self-guided version first -- the main version are the slides you would actually present.)

This intro generally takes about 15-30 minutes.

Communications Tools
The introduction to open source currently looks like this. You can see a self-guided version here. (It has been recommended that presenters actually read the self-guided version first -- the main version are the slides you would actually present.)

Some presenters may choose to include the Bug Comprehension Activity. You can also add this short piece on social norms.

With the bug comprehension activity + social norms, this presentation takes about 60 minutes. Without, it takes about 25-35 minutes.

Git/Github
There are a few different options for teaching students about git. These depend mostly on whether you're a single person teaching a large group, or whether you have enough volunteers that they can each lead small groups. For small groups, we recommend this activity. For one large group, we recommend this slightly different version.

Both versions take about an hour. Some students will finish much more quickly. We recommend finding a mentor who is comfortable with git to teach more advanced students additional topics.

The repository we use as a demo during the mentor trainings is here.

Contributions Workshop
The contributions workshop may look different from event to event. What remains the same is that mentors are key for giving attendees a good experience. It's important that mentors be enthusiastic about what they're teaching, so finding something they *want* to teach is a high priority for us! Individual mentors may:


 * Lead contributions to a specific project
 * Teach students about a specific area of open source (for instance, open GIS or open science)
 * Show students how to make a specific kind of contribution (for instance, improving install instructions, reproducing bugs, or increasing accessibility of websites)
 * Guiding students through the process of finding their own projects

OpenHatch Mentoring Philosophy
This training module will be more of a discussion of our mentoring philosophy and how best to carry it out at OpenHatch events. You can read about that philosophy in the Mentor Guide under "general guidelines" (that's the only section pre-selected, so just scroll down; you can ignore the rest, which is out of date).