Changes

Jump to: navigation, search

OSD600

2,315 bytes removed, 13:55, 15 January 2019
Grading
=Topics in Open Source Development=
==[http://cswww.senecac.onsenecacollege.ca/index.phpcgi-bin/subject?outlines1=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 GitHub, mailing lists, IRC, 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 (e.g., Firefox). 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:
* Use existing open source code whenever possible
* Be open to helping others and to being helped
 
===Details===
 
* Each student must pick a project from the list of proposed projects, or have another project idea approved by the instructor. Projects have been created in consultation with the Mozilla community.
* Students are strongly encouraged to work individually, and only in rare circumstances will partnerships be allowed.
* Create a project page based on the [[Sample Project|'Sample Project' template]]. If someone has already created a page for a project you want to work on, 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 become a Contributor instead (see below).
* Become a Contributor to one or more other projects. This is something that will just happen as you interact on IRC or in class. As people need help, you can choose to get involved with things. You are encouraged to use the [[Contrib Opportunities]] page to list and find things you can do. 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 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 project status in the Project News section. You should be updating this page at least once per week.
* Update your blog at least once and hopefully 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 Property==
==Grading==
Detailed grading information will be discussed later in the term. Below is a breakdown of how students will be graded, and [http://vocamusblog.humphd.netorg/davevocamus-680/?p=680 this blog post] gives more details about the rationale:
* '''6080%''' - Project Deliverables (e.g., code, documentsPull Requests, documentation), marked in terms of quality, quantity, process, etc. Your project will be marked at three milestone releases, the number and values being:** 5'''10% ''' - [[OSD & DPS909 Winter 2010 OSD600 Initial Project Plan2019 Release 0.1|Initial Project PlanRelease 0.1]] (Due Week of January 25)due Wed, Jan 30** 15'''30% ''' - [[OSD & DPS909 Winter 2019 Release 0.1 2|Release (Due Week of February 15)** 15% - 0.2 Release (Due Week of March 15)]] due Wed, Mar 6** 25'''20% ''' - [[OSD & DPS909 Winter 2019 Release 0.3 |Release (Due Week of April 5)0.3]] due Fri, Mar 22** '''20%''' - Project Wiki Page and Blog[[OSD & DPS909 Winter 2019 Release 0.4|Release 0. You will be marked on your project and personal page's quality, depth of explanation, frequency of update4]] due Wed, etc. Apr 10* '''20%''' - Contributions to other projectsLabs/Blog: will be marked Done/Not Done (i.e. You , no subjective grading will be marked on applied). Students are expected to complete all course labs in order to pass the quantity and quality of your contributions to other groupscourse.
==Resources==
* [[DPS909 and & OSD600 Fall 2010 Weekly Schedule|Weekly ScheduleWinter 2019]]* [[Fall 2010 https://seneca-open-source.slack.com Seneca Open Source Students]Slack](sign-up with your @myseneca.ca email)
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet]
==Examples== Here are a list of good student artifacts from the previous course, which should provide examples for future students to follow: * '''Blog''' - [http://armenzg.blogspot.com/ Armen], [http://crashopensource.blogspot.com/ Lukas], [http://jamesboston.ca/cms/taxonomy/term/1/0 James], [http://ehren.wordpress.com/ Ehren]* '''Personal Wiki''' - [[User:Armenzg|Armen]], [[User:Backinblakk|Lukas]]* '''Project Wiki''' - [[Automated localization build tool]], [[Extending the Buildbot]], [[Buildbot and EC2]] ==Archives==
* [[OSD600 Fall 2007]]
* [[OSD600 Fall 2008]]
* [[OSD600 Fall 2010]]
* [[OSD600 Summer 2010]]
* [[OSD600 Fall 2011]]
* [[OSD600 Fall 2012]]
* [[OSD600 Fall 2013]]
* [[OSD600 Fall 2015]]
* [[OSD600 Winter 2017]]
* [[OSD600 Fall 2017]]
* [[OSD600 Winter 2018]]
* [[OSD600 Fall 2018]]
 
[[Category:OSD600]]

Navigation menu