==[http://cswww.senecac.onsenecacollege.ca/index.phpcgi-bin/subject?outlines1=DPS909 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 of an 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 mailing listsGitHub, IRCSlack, wikis, etc.

* Write software that integrates and interacts with the Mozilla project’s codeexisting 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.

This is a project course, and the majority of each student’s mark will come from work done on a real Mozilla 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. Students will also have the opportunity to contribute their own code to real-world software projects, thereby gaining important experience.

First, consider the typical rules around cheating and plagiarism. In this assignmentcourse, students are encouraged to work within the set of best practices natural to open source development. Open source developers do not write from scratch what already exists and is freely available for use. Students should be thinking in terms or of code reuse. It is acceptable for students to use code from other open source projects, so long as the license is amenable to the use.

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 Mozilla open source community. This means that collaboration between students and even other members of the Mozilla open source community is acceptable practice.

* Work with and within the Mozilla open source community

* Be open to helping others and to being helped

===Details=Intellectual Property==

* Each student must pick a project from the list of proposed projectsGiven that this course is focused on open source development, or have another project idea approved by the instructor. * Create a project page based on the [[Sample Project|template in the wiki]]. If someone has already created a page for a project you want to and given that students work onreal open source codebases, speak to that person to see if you can join him/her. If s/he says yes, add your name to the Project Leader(s) section; otherwise pick another project and all student work will become a Contributor instead (see below). * Become a Contributor to one or more other projectsopen source. This is something that The particular license used will just happen as you interact be determined based on IRC or in class. As people need help, you can choose to get involved with things. For example: helping to debug something, doing research into a problem, writing some tricky code. Over time your list of contributions to other peoples’ projects should grow. Keep track of this in your personal page. * Keep your the particular project page on the wiki updated. Add technical information to the Project Details section as you get a better understanding of the problem, and keep track of your open source project status in the Project News section. You should be updating this page at least once per week.* Update your blog twice a week. Remember that the more you write, the easier it will be to get help from other people: it is easier for people to understand your question with supporting documentation on the web.* Update your personal page on the wiki with permanent information, such as a list of your contributions to various projects.

==Intellectual PropertyGrading==

Given that this course Detailed grading information will be discussed later in the term. Below is focused on open source developmenta breakdown of how students will be graded, and given that we students working on real pieces of the Mozilla codebase, all student work will become open source[http://blog.humphd. The particular license used will be determined based on org/vocamus-680/?p=680 this blog post] gives more details about the other parts of Mozilla with which you are interacting.rationale:

Detailed grading information will be discussed later in the term.* '''60%''' - [[Fall 2007 Major Project|Final Project]] Deliverables (e.g., code, documents), marked in terms of quality, quantity, etc. Your Students must satisfactorily complete all project will be marked at three milestone releases, the number deliverables and values being:** 15% - 0.1 Release ** 15% - 0.2 Release** 30% - 0.3 Release* '''15%''' - Project Wiki Page and Blog. You will be marked on your project and personal page's quality, depth of explanation, frequency of update, etc. * '''20%''' - Contributions labs to other projects. You will be marked on pass the quantity and quality of your contributions to other groups.* '''5%''' - FSOSS Paper. You will be marked on a paper to be written in response to [http://fsoss.senecac.on.ca FSOSS]. '''NOTE:''' You must attend FSOSS in order to complete this assignment, which means [http://fsoss.senecac.on.ca/2007/register.php registering]. Students receive a discount, and volunteering Seneca students can get in for freecourse.

* [[DPS909 & OSD600 Fall 2007 Weekly Schedule2020]]- Weekly Course Notes and Links* [[Project List]]* [[Potential Projects]https://seneca-open-source.slack.com Seneca Open Source Slack]- Our main communication platform is Slack. You can sign-up with your @myseneca.ca email address.* [httphttps://zenittelescope.senecaccdot.on.ca/~chris.tyler/planetsystems/ Telescope Open Source@Seneca PlanetBlog]- All student open source blogs are aggregated here in our custom blogging software