667
edits
Changes
no edit summary
=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 project. 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 community.
* Use existing open source code whenever possible
* Be open to helping others and to being helped
==Intellectual Property==
Given that this course is focused on open source development, and given that students work on real open source codebases, all student work will become open source. The particular license used will be determined based on the particular project and open source project.
==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:
* '''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:** '''15%''' - [[DPS909 and OSD600 0.1 Release 2014|0.1 Release]] (Due Sept 26Fri Feb 3)** '''20%''' - 0.2 Release (Due Oct 17Fri Feb 24)** '''20%''' - 0.3 Release (Due Nov 14Fri Mar 24)** '''20%''' - 0.4 Release (Due Dec 5Thurs April 13)* '''1520%''' - 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.* '''5%''' - [[FSOSS 2014 Report]]. You , and many labs will be marked on require you to write a report that will be based on research and analysis you will do at [http://fsoss.ca FSOSS 2014]blog post in order to submit them.* '''5%''' - [[2014 Open Source Project Case Study]]. You At the end of the term, you will be marked on a class presentation about an open source project in which you study, its community, code, demo and culturediscuss the work of your releases.
==Resources==
* [[DPS909 and & OSD600 Fall 2014 Notes|Class Notes, links, and other info]]* [[Fall 2014 Open Source Students]]* [http://github.com Github]* [[Git Cheatsheet and GotchasWinter 2017]]
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet]
== Archives ==