• 2014-09-07 — 2014-12-10
  • Tues & Thurs 6:30PM - 7:45PM
  • 4085.582.01
  • Orange Hall (ORN)-1380
  • remydcsi@rit.edu


The RIT Humanitarian Free/Open Source Software Development Course

The source for this syllabus can be found at http://github.com/decause/hflossk

Text Books

There are a number of textbooks we’ll be referencing throughout the quarter. You can find these books/texts/articles here on the resources page

What You’ll Do

This course will introduce students to the Free and Open Source Software (FOSS) and Open Content movements, to the open source development process, and to the open questions of the efficacy of technology in the classroom.

Students will learn FOSS process and Tools with class projects that support the One Laptop Per Child community by creating content and software for free distribution to students and teachers around the world. The OLPC project is driven by a world-wide community–one that students in HFOSS will become part of.

For this course students will be expected to attend and make final presentations to the RIT and Rochester FOSS communities via the regular Rochester Pythonistas meet-ups and FOSSBox hack-a-thons when possible. Students will also become members of the Sugar and OLPC international communities. Local FOSS community members may join us in class sessions as well. Treat them as you would another instructor, but they’re also your peers in moving this innovative project forward.

The spirit of the course

While still a course where you will receive a letter grade, the spirit of the course is intended to be both open and fun.

An open course – students will have access to the ‘document source’ for the syllabus. While you are reading the syllabus right now, as a student of the class you have a right to fork the upstream repository, make modifications, and submit patches for review. Barring a troll festival, this can create a fun, dynamic environment in which the course curriculum can develop by the very same mechanism being taught during the quarter (community-driven).


All code developed by students in the course must be licensed (by the student) under any one of the licenses approved by the Open Source Initiative.

Code that you write is your code, with which you can do what you will; true. However, if you’re unwilling to license code you write for an Free/Open Source course with a Free/Open Source license, you may be in the wrong course.


Week Day Topic Assigned Due
1 1 08/26

Welcome, intro, Syllabus, RTFM

LitReview1: What is Open Source? by Steve Weber

2 08/28

First Flight

Homework - First Flight

2 1 09/02

Formal Introduction to Git and Github

2 09/04

Writing for HFOSS - litreviews and blog posts

grok litreview.txt

Homework - First Flight

grok litreview.txt

3 1 09/09

Lit Review Discussion: What is Open Source?

LitReview1: What is Open Source? by Steve Weber

2 09/11

LIT: 5 Pillars of Opensource.com



4 1 09/16

Class CANCELLED. GO TO ROC.py Tuesday!

2 09/18

OLPC Distribution & Smoke testing

Smoke Test

Homework - Bugfix

*** 09/20 to

Software Freedom Day 2014

5 1 09/23

COMMARCH: Git-by-a-bus and CCF: Callaway Coefficient of Fail.

Commarch Team Formation

Commarch Report

2 09/25

Commarch-ery: Reporting and analysis using GBAB, GBAT, Github, and Gource

Smoke Test

HFOSS@RIT SugarLabs Bundle

Commarch Team Formation

Homework - Bugfix

*** 9/26
to 9/28

Hackathon @ Cornell: http://bigredhacks.com

6 1 09/30

Commarch Presentations I

Commarch Report

2 10/02

Guest Lecture: Hudl & FOSS in (SIH) 87-1600

*** 10/04
to 10/05

Hackathon @ Syracuse: http://hackupstate.com

7 1 10/07

XO Projects Info/Demo Day!

Homework - Team Proposal

2 10/09

EDU: Curriculum Exploration

NY & MA 4th Grade Curriculum

8 1 10/14

No Class: Monday Class Schedule

NY & MA 4th Grade Curriculum

2 10/16

EDU: Curriculum Discussion

Homework - Team Proposal

9 1 10/21

No Class: Go To ROCpy

ROCpy on Meetup.com
2 10/23

Remote Lecture via IRC

All Things Open Conference
10 1 10/28


2 10/30


*** 11/01

Unnofficial: Tentative Date for BarcampROC

11 1 11/04

Election Night Hackathon: (SIH) 87-1600

2 11/06


*** 11/07
to 11/09

Hackathon: RIT48

12 1 11/11


2 11/13


13 1 11/18

TUESDAY 7-9pm ROCpy Demos (carpool in parking lot 6:15pm)

ROCpy on Meetup.com

2 11/20


*** 11/22

Conference: Rochester Mini-Maker Faire

Rochester Mini-Maker Faire
14 1 11/25

Lit Review 2

2 11/27

No Class: Happy Thanksgiving

15 1 12/02


2 12/04


16 1 12/09

Playtesting Session ???

2 12/11

Playtesting Session ???

*** 12/10

Playtesting Session ???

*** 12/12

Playtesting Session ???

17 1 12/16

Return XO's & Final Presentations (w/ Pizza)

Final Presentation Details

2 12/18

No Class: </hfoss>


Attendance is required for this course. Students are allotted 2 excused absences per semester.

Subsequent absences will result in a 10% reduction of your final letter grade for each class missed.


Assignments are due at 4:59pm of the day they are marked as due, to be useful in class.

Late submissions will be deducted 10% per day they are late.

Your final grade for the quarter will be derived from the following weights.

Component Weight
In-Class Participation 10%
Quizzes 10%
Literature Reviews 10%
Team Peer Assessment 15%
Completed Project 15%
Final Presentation 20%
FOSS Dev Practices (Blog posts, commits, tickets, IRC) 20%

Blog updates – students are required to keep a blog to which they post updates about their investigations, progress, success, and pitfalls. This blog can be hosted anywhere, but must be added to the course participant page (there are instructions on how to do this in Homework - First Flight).

  • You must make at least one blog post per week to receive full credit. This is in addition to any assignments that are posted to your blog for that week. A week Ends on Sunday at 11:59pm.
  • You must participate regularly in the course’s IRC channel: asking and answering questions.
  • Contributions to the course curriculum, syllabus, and rubric are factored in here as well.

Blogging is good for you and good for the FLOSS community at large.

The details for the final can be found at Final.

Lightning Talks - Extra Credit

For the first portion of class, any student has the opportunity to give a lightning talk on a topic of their chosing. Your lightning talk must be less than 5 minutes in length and must be at least remotely related to the course material.

You will receive +1 extra credit points towards your final grade for every lightning talk you give. Only the first 2 lightning talks offered will be allowed during a given class. Talks will be chosen from among those offered by students on a FIFO basis.