1. HOW TO ENGAGESTUDENTSIN REALOPEN SOURCEPROJECTS
2. Scott Wilson Apache Committer Service Manager, OSS Watch GSoC MentorResearcher, University of Bolton @scottbw firstname.lastname@example.org email@example.com
3. You want to know howto use open sourceprojects in your classesIm going to suggest oneway to do it from weekone, with no codingrequired
4. HOW DID I GET HERE?How an ASF committer and researcher got involved in undergraduate teaching
5. CPU4000 Core Skills ModuleFirst year, first semesterTraditionally boring stuff like how to use library, how to do referencing in an essay. Involved lots of lecturesMoved to inquiry based learning on open source projects
6. 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
7. 5 TIPS
8. 1.START WITH SOFTSKILLS, NOT CODE ly rc e is primari n open sou oll aboratio ities and c about commun
9. You dont need codingskills to: file a bug reportask for help on a list orforum correct thedocumentation improvegraphics localization testbrowser compatibility ighly en source projects value h These are all things op
10. And the truth is, not allcomputing students willend up as developers. r t out until late b ly wont find tha And they proba
11. 2.LET STUDENTS PICKTHEIR OWN PROJECTS**yes, non-apache ones! And especially not my-favourite-project We need to build enth and develop usiasm a sense of ownership
12. Working on software ismore fun if its forsomething youreinterested in already,like music, sport,games, art, sharing picsof cats Gi ve up control now, while you still can :)
13. 3.TEACH HOW TO READA PROJECT Know how to check fo r signs of lif e in a project
14. Get students familiarwith finding sourcecode, subscribing tomailing lists, navigatingan issue tracker, andusing tools like ohloh later these are fundamental skills to build on
15. 4.GET STUDENTSINTERACTING WITHTHE PROJECTCOMMUNITY -NOT THE LECTURER Youve got other things to do , and its not like youre an expert on all the software ever written
16. Start simple: try todownload and install thesoftware, and if you getstuck, ask for help onthe list or forum -NOT THE LECTURER
17. but you can helpstudents understand listetiquette Z PINSTALL PL UR COD E S UX. H E L
18. 5.ASSESS PUBLICINTERACTIONS Authentic a ssessment!
19. By which I mean thingslike issue trackerreports, conversationson mailing lists andforums, and any patches(probably to doc)
20. You can use a learning(b)log, patchwork text,or whatever yourecomfortable with. Evenroll it into a traditionalessay.
21. 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 LECTURER5. ASSESS PUBLIC INTERACTIONS
22. 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 letterto Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.