Okay looking over the first chapter (http://teachingopensource.org/index.php/Practical_OSS_Exploration_-_Introduction_to_Free_and_Open_Source_Software) I think that the main objectives are. 1. Understand the differences, relative advantages, and disadvantages of Open Source and Closed Source software. 2. Compare open and closed source software from the perspective of a user, and as a developer. 3. Be familiar with some of the roles in open source projects - The stuff about contributor mountain seems to be going this way, but I feel like if falls short, or if this is even an objective for this chapter. 4. Choose an Open Source project to contribute to while working through this book. 5. Know where the textbook is going - this chapter introduces very briefly many concepts that later get a whole chapter.
It seems like the book is assuming that students are familiar enough with C to read, understand and edit a basic program. It is also assuming that students have access to a *nix system of some kind to do their development on. The contributor mountain example feels to be problematic, as though it reflects a hierarchy, rather than an open process. It is also a really great way to provide a road map towards participation, but I wonder if we couldn't find a better metaphor, and one that could be carried through the whole book. Review vs. Exercises For the reviews to be useful they need to be focused on ideas, and have clearly correct or incorrect answers. The exercises all seem to be fairly straightforward, and working towards the objectives, they seem to meet the goal of providing concrete action steps for students to complete. I'm writing review questions with the goal of ensuring the students understand the core ideas of a particular chapter, and know the meaning of key terms. For this chapter I think a set of 5 true/false questions(I've got a few scribbled down, but I'm going to set a 30 min timer and see if I can't improve them this evening.) about attributes of Open Source Software vs Closed Source software (i.e. "T/F - You can fix a bug that is bothering you if it is in Closed Source Software") Some Multiple choice scenario questions, (i.e. Software that is free of charge is open source only if? A. ... B. Anyone may download edit and build the software themselves C. ... D. ...). And maybe a set of define the term, or short scenario questions. I'm not sure which, if any of the terms are critical though. Open Source seems to be the only thing in this that is definitely critical. -- -Andrew Hamblin "That which does not kill me has made a grave tactical error" _______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
