[OSCTC-planning] framing our tutorials

[Heidi Ellis]

Hi Folks,

I like the idea of partnering the learning of the communication tools with an actual project. I would plan to introduce the activities rather than just “encounter” them as this would highlight their importance. I do have some thoughts:


1.       It might make sense when actually running the activity, to pick one or more projects to use as an example. I have found that folks can spend a lot of time looking through projects and so providing some direction there might be helpful. Another thought is to use projects provided by the mentors or have students suggest projects.

2.       I might structure the IRC activity to use #openhatch rather than the project’s IRC channel because 1) folks in the project channel might not appreciate having their channel used for student learning; and 2) students might feel more intimidated by participating in a “real” channel.  What I do when teaching this is to use two channels. One is the project’s channel to show what is happening there and the second is a channel for students to talk amongst themselves.

3.       I’d do the version control and issue tracker with the ”real” project.
Just my two cents. ☺
Heidi

From: osctc-planning-bounces at lists.openhatch.org [mailto:osctc-planning-bounces at lists.openhatch.org] On Behalf Of Shauna Gordon-McKeon
Sent: Thursday, July 24, 2014 6:40 PM
To: Planning for Open Source Comes to Campus
Subject: [OSCTC-planning] framing our tutorials

We've gotten a few comments that our morning tutorials, which cover IRC, issue trackers, reading issue reports, and using version control, are a bit abstract - they're not rooted in the process of contributing and therefore they're less interesting and harder to learn about for students.

A little while back we made the 'Finding a Project' activity:
https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Curriculum/Finding_a_Project

What do folks think about framing the morning tutorials with this activity?  Students would start the day by finding projects, and they'd cover the different activities - IRC, issue trackers, version control - as they came up.

Alternatively, we could keep this where it is at the beginning of the contributions workshop, or remove it entirely.

~ Shauna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/osctc-planning/attachments/20140725/328581d7/attachment.html>