An excerpt from Syllabus:
An open course – students will have access to the ‘document source’ for the syllabus and grading rubric. 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).
A fun course – while the primary deliverable for the course is a working web-based game, we are going to subject the course itself to gamification. Instead of grading students’ final projects individually, projects will be pitted against one another through a scheme developed by the students themselves, called the Final Project Rubric.
Part of the experience of being an open source developer is the instrinsic motivation that drives you to build open software. That motivation can be different for each person. Its not something that is ever taught and is difficult to develop into a course curriculum for sure!
Your assignment here is to take part in creating Final Project Rubric.
You should have divided up into your teams for the final project by this point. Do the following with your github accounts to setup both for the final project and for this homework:
- Designate one person from your team whose github account will be the primary account for your team. The primary designee will be responsible for merging pull requests from their teammates both for the final project and for this homework.
- All other members of your team should:
- Delete their tos-rit-projects-seminar repositories on github.
- Fork the tos-rit-projects-seminar repo from their team’s primary account (the designee’s account).
You will be responsible in this homework for forking your team’s repo as described above, committing patches to the document (Final Project Rubric), pushing to your own github repo and issuing pull requests. You may add to the document as well as delete from it.
Although open source development is typically thought of as a cooperative mode of production, some participants derive their motivation from a competitive outlook towards their peer developers. As an experiment, you will all be graded in competition with one another for this assignment.
- There are 100 possible points.
- The student with the highest impact will receive 100 points.
- All other students who contribute patches will receive a weighted grade between 100 and 75 points based on their impact.
- Students who submit no patches will receive 0 points.
Your impact is defined as the number of lines added + the number of lines deleted. You can see a graph of your impact so far here.
Good luck! And make an awesome rubric worthy of awesome projects!