how to engage students in real open source projects

Post on 18-Dec-2014

1.938 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

 

TRANSCRIPT

HOW TO ENGAGE STUDENTS

IN REALOPEN SOURCE PROJECTS

Scott WilsonApache Committer

Service Manager, OSS WatchGSoC Mentor

Researcher, University of Bolton@scottbw

scottbw@apache.orgscott.bradley.wilson@gmail.com

You want to know how to use open source projects in your classes

I’m going to suggest one way to do it from week one, with no coding required

HOW DID I GET HERE?

How an ASF committer and researcher got involved in undergraduate teaching…

CPU4000Core Skills Module

First year, first semesterTraditionally “boring” stuff like how to use

library, how to do referencing in an essay. Involved lots of lectures

Moved to inquiry based learning on open source projects

Results

• Run now for 3 home cohorts of 25-45 students plus 2 international cohorts

• Some students produced fantastic work! Some… needed to be unstuck :)

• Notable increase in motivation

5 TIPS

1.START WITH SOFT SKILLS, NOT CODE

open source is primarily

about communities and collaboration

You don’t need coding skills to: file a bug report ask for help on a list or forum correct the documentation improve graphics localization test browser compatibility

These are all things open source projects value highly

And the truth is, not all computing students will end up as developers.

And they probably won’t find that out until later…

2. LET STUDENTS PICK THEIR OWN PROJECTS*

*yes, non-apache ones! And especially not my-favourite-project

We need to build enthusiasm and develop a sense of ownership

Working on software is more fun if its for something you’re interested in already, like music, sport, games, art, sharing pics of cats …

Give up control now, while you still can :)

3. TEACH HOW TO “READ” A PROJECT

Know how to check for signs of life in a project

Get students familiar with finding source code, subscribing to mailing lists, navigating an issue tracker, and using tools like ohloh

these are fundamental skills to build on later

4. GET STUDENTS INTERACTING WITH THE PROJECT COMMUNITY - NOT THE LECTURER

You’ve got other things to do, and its not like you’re an expert on all the software ever written

Start simple: try to download and install the software, and if you get stuck, ask for help on the list or forum - NOT THE LECTURER

… but you can help students understand list etiquette

UR CODE SUX. HELP INSTALL PLZ

5. ASSESS PUBLIC INTERACTIONS

Authentic assessment!

By which I mean things like issue tracker reports, conversations on mailing lists and forums, and any patches (probably to doc)

You can use a learning (b)log, patchwork text, or whatever you’re comfortable with. Even roll it into a traditional essay.

1. START WITH SOFT SKILLS, NOT CODE2. LET STUDENTS PICK THEIR OWN

PROJECTS3. TEACH HOW TO “READ” A PROJECT4. GET STUDENTS INTERACTING WITH

THE PROJECT COMMUNITY - NOT THE LECTURER

5. ASSESS PUBLIC INTERACTIONS

This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit

http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041,

USA.

top related