FOSS Course, UPenn, Murphy
(Difference between revisions)
(→0. Overview) |
(→2. Methods of Assessment) |
||
Line 38: | Line 38: | ||
== 2. Methods of Assessment == | == 2. Methods of Assessment == | ||
− | + | Each week, students are expected to post to their public blogs a 200-300 word response to the weekly reading assignment. In some cases, specific prompts may be given but in general the prompt is open-ended. Blog posts are assessed on the following scale: | |
− | ** | + | * Exceptional: a blog post that is particularly insightful, thorough, or thought-provoking |
− | * ' | + | * Satisfactory: a blog post that demonstrates that the student has read the articles, understands their main points, and can synthesize a response including personal insight |
+ | * Unsatisfactory: a blog post that demonstrates that the student has not read the articles, does not understand the main points, and/or is simply summarizing the readings but not relaying any personal insight | ||
+ | * Not submitted: when it's... ya know... "not submitted" | ||
+ | |||
+ | Students are also expected to attend and participate in all discussions of the reading assignments. Participation is assessed on the following scale: | ||
+ | * Exceptional: numerous contributions to the discussion that are particularly insightful, thorough, or thought-provoking | ||
+ | * Satisfactory: | ||
== 3. Course Outline == | == 3. Course Outline == |
Revision as of 14:04, 16 August 2016
HERE WE GO!
Contents |
0. Overview
Course Name | Open Source Software Development |
---|---|
Course Overview | This course exposes students to the cultural, technical, and legal aspects of FOSS development and provides students with an opportunity to work on a real-world open-source software project, and gain experience in software maintenance and enhancing software quality. |
Instructor Contact Info | Chris Murphy |
Student Characteristics | The course is targeted to upper-level undergraduate or graduate students. |
Prerequisites | Students should have completed a traditional software engineering course and have had experience working in groups. They should be familiar with GitHub and the target programming language for the FOSS project on which they will work. |
Infrastructure | The class meets twice a week for 75 minutes each. In general, one of the class meetings will consist of discussions of the reading assignments and/or guest speakers, and the other class meeting that week will be for learning activities, project status updates and presentations, or time to work on the project. |
Offerings | Univ of Pennsylvania: Fall 2016 (14 undergraduates) |
1. Learning Objectives
- objectives & prerequisites should be active, student-centered, specific, and measurable
- the student will be able to...
- for the entire course, and/or for FOSS-specific parts of the course
- might include content & process skills
- might consider all levels of Bloom's taxonomy
2. Methods of Assessment
Each week, students are expected to post to their public blogs a 200-300 word response to the weekly reading assignment. In some cases, specific prompts may be given but in general the prompt is open-ended. Blog posts are assessed on the following scale:
- Exceptional: a blog post that is particularly insightful, thorough, or thought-provoking
- Satisfactory: a blog post that demonstrates that the student has read the articles, understands their main points, and can synthesize a response including personal insight
- Unsatisfactory: a blog post that demonstrates that the student has not read the articles, does not understand the main points, and/or is simply summarizing the readings but not relaying any personal insight
- Not submitted: when it's... ya know... "not submitted"
Students are also expected to attend and participate in all discussions of the reading assignments. Participation is assessed on the following scale:
- Exceptional: numerous contributions to the discussion that are particularly insightful, thorough, or thought-provoking
- Satisfactory:
3. Course Outline
Week | Topics/Activities | Reading Assignments |
---|---|---|
1 | Course Introduction
Blogs, IRC, and GitHub
|
|
2 | FOSS Background
FOSS Field Trip and Project Evaluation
|
|
3 | Getting Started in FOSS
Start Getting Involved in Project
|
|
4 | Ways of Contributing to FOSS
|
|
5 | What Motivates People to Contribute to FOSS
|
|
6 | Licensing and Legal Issues
|
|
7 | FOSS Business Models and Opportunities
|
|
8 | HFOSS
|
|
9 | FOSS Success Stories
|
|
10 | Starting and Growing a FOSS Community
|
|
11 | Criticisms of FOSS
|
4. Notes to Instructor
- Tips, suggestions, lessons learned (warnings)...
5. Moving Forward
- what next steps are desirable or possible for this course
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
Materials linked to by this page may be governed by other licenses.