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.

* Use the communication modes particular to the open source world through participation in such things as GithubGitHub, mailing lists, wikis, etc.

* Work collaboratively with fellow students and members of the Mozilla open source community.

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 codebaseits codebases. Through this experience students will learn about the processes, tools, and practices involved in developing software as part of a large open source community.

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.

* Be open to helping others and to being helped

* '''7580%''' - Project Deliverables (e.g., code, documentsPull Requests, documentation), marked in terms of quality, quantity, process, etc. Your project will be marked at four milestone releases, the number and values being:** '''1510%''' - [[OSD & DPS909 & OSD600 Winter 2017 2019 Release 0.1 | Release 0.1 Release (Due Fri Feb 10)]]due Wed, Jan 30** '''2030%''' - [[OSD & DPS909 Winter 2019 Release 0.2 |Release (Due Fri Feb 24)0.2]] due Wed, Mar 6** '''20%''' - [[OSD & DPS909 Winter 2019 Release 0.3 |Release (Due 0.3]] due Fri , Mar 24)22** '''20%''' - [[OSD & DPS909 Winter 2019 Release 0.4 |Release (Due Thurs April 13)0.4]] due Wed, Apr 10* '''20%''' - Labs/Blog. You : will be marked on your blog's qualityDone/Not Done (i.e., depth of explanation, frequency of update, etcno subjective grading will be applied). You Students are expected to blog weekly throughout the complete all course, and many labs will require you to write a blog post in order to submit them.* '''5%''' - At pass the end of the term, you will be marked on a class presentation in which you demo and discuss the work of your releasescourse.

* [[DPS909 & OSD600 Winter 20172019]]* [https://seneca-open-source.slack.com Seneca Open Source Slack] (sign-up with your @myseneca.ca email)