667
edits
Changes
no edit summary
==[http://www.senecacollege.ca/cgi-bin/subject?s1=OSD600 Subject Description]==
This course introduces students to the technological, social, and pragmatic aspects of developing open source software through direct involvement in the Mozilla projectlarge open source projects. Students will learn to use the tools, techniques, and strategies of open source developers. This is a project-based programming course. The Mozilla project has been chosen as an example open source project because of its maturity, breadth and depth of technology, and strong community.
==Course Outcomes==
* Describe the history and philosophy of an open source project
* Choose between the various open source licenses understanding the implications for users, developers, and the software community in general
* Use the communication modes particular to the open source world through participation in such things as GithubGitHub, mailing lists, wikis, etc.
* Use the tools of open source development, for example: distributed revision control; documentation tools; automated build and test systems; debuggers; source code utilities; tracking systems; on-line resources, etc.
* Work with a pre-existing large source code base
* Write software that integrates and interacts with existing open source systems. For example: add-ons; bug fixes; new features; etc.
* Work collaboratively with fellow students and members of the Mozilla open source community.
==Major Project==
This is a project course, and the majority of each student’s mark will come from work done on a real development project. The primary goal of this project is to get students involved in the Mozilla open source development community and its codebase. Through this experience students will learn about the processes, tools, and practices involved in developing software as part of a large open source community.
===Philosophy===
Second, consider the typical restrictions on peer-collaboration. In this project students are encouraged to work together, to help one another, to look at each other's code, etc. Open source collaboration is about leveraging the collective knowledge of a community to help solve the problems of the individual.
Third, consider the sharp dividing line between student projects in most programming courses. For the most part, students are evaluated on their ability to do a particular project or to solve a particular problem on their own. The outcome is measured against peer outcomes. However, in this course students are not in competition with their peers; rather, they are all working on one large project (ie.eg., Mozilla) with many sub-projects within it. As a result, there is no clean line to divide one student’s work from another, or even student work from that of the open source community. This means that collaboration between students and even other members of the open source community is acceptable practice.
To summarize, students should:
Detailed grading information will be discussed later in the term. Below is a breakdown of how students will be graded, and [http://blog.humphd.org/vocamus-680/?p=680 this blog post] gives more details about the rationale:
* '''75%''' - Project Deliverables (e.g., code, documents), marked in terms of quality, quantity, process, etc. Your project will be marked at four milestone releases, the number and values being:** '''25%''' - [[DPS909/OSD600 0.1 Release|0.1 Release]]
** '''25%''' - 0.2 Release
** '''25%''' - 0.3 Release
* '''15%''' - Blog. You will be marked on your blog's quality, depth of explanation, frequency of update, etc. You are expected to blog weekly throughout the course, and many labs will require you to write a blog post in order to submit them.* '''1025%''' - Labs, which will be marked Done/Not Done (i.e., no subjective grading will be applied). Students are expected to complete all course labsin order to pass the course.
==Resources==
* [[DPS909 & OSD600 Fall 2017Winter 2018]]
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet]
* [[DPS909 & OSD600 Fall 2017 Winter 2018 Bug List]]
== Archives ==
* [[OSD600 Fall 2015]]
* [[OSD600 Winter 2017]]
* [[OSD600 Fall 2017|Fall 2017]]
[[Category:OSD600]]