User:MZarb
| (4 intermediate revisions by one user not shown) | |||
| Line 20: | Line 20: | ||
|- | |- | ||
| '''Level of Activity''' | | '''Level of Activity''' | ||
| − | |||
|1 | |1 | ||
|Many commits but not recently. | |Many commits but not recently. | ||
| + | |- | ||
| '''Number of Contributors''' | | '''Number of Contributors''' | ||
|2 | |2 | ||
| Line 51: | Line 51: | ||
|Very well laid out and all information is clearly available. Not sure if I would find use for this particular project in my classes, but structurally it is sound, and something I would look to emulate. | |Very well laid out and all information is clearly available. Not sure if I would find use for this particular project in my classes, but structurally it is sound, and something I would look to emulate. | ||
|} | |} | ||
| + | |||
| + | |||
| + | |||
| + | ''FOSS in Courses 2'' | ||
| + | |||
| + | Recalling your list of activities/topics from FOSS in Courses 1 (Instructors), identify the ways that these FOSS activities/topics can be structured. | ||
| + | |||
| + | Lectures: A wealth of material here - you can talk about professionalism (licensing etc.), or use code fragments from existing projects to show how easy/difficult it is to follow on from another programmer's code. These can be used either as demo pieces, or even handed out in a 'complete the code' exercise. | ||
| + | |||
| + | In-class activity: Concepts discussed above can be expanded on in lab sessions. | ||
| + | |||
| + | Project: Incorporate HFOSS in a client-facing project module. | ||
Latest revision as of 11:14, 27 June 2017
Mark Zarb
Dr Mark Zarb is the Foundation Year Coordinator and Course Leader at the School of Computing Science and Digital Media at Robert Gordon University. Prior to this, he received his PhD in Computing (with a focus on CS Education and Software Engineering) from the University of Dundee. Currently, Mark teaches on a variety of undergraduate modules, on topics ranging from introductory programming to software architecture and Arduino microcontrollers.
Rubric
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | Clearly signposted. MPL 2.0 w/ HD. |
| Language | 2 | |
| Level of Activity | 1 | Many commits but not recently. |
| Number of Contributors | 2 | |
| Product Size | 2 | |
| Issue Tracker | 1 | Separate system dashboard - very informative but leaving GitHub so how would students react? |
| New Contributor | 2 | |
| Community Norms | 2 | |
| User Base | 2 | |
| Total Score | 16 | Very well laid out and all information is clearly available. Not sure if I would find use for this particular project in my classes, but structurally it is sound, and something I would look to emulate. |
FOSS in Courses 2
Recalling your list of activities/topics from FOSS in Courses 1 (Instructors), identify the ways that these FOSS activities/topics can be structured.
Lectures: A wealth of material here - you can talk about professionalism (licensing etc.), or use code fragments from existing projects to show how easy/difficult it is to follow on from another programmer's code. These can be used either as demo pieces, or even handed out in a 'complete the code' exercise.
In-class activity: Concepts discussed above can be expanded on in lab sessions.
Project: Incorporate HFOSS in a client-facing project module.
