Changes

This course builds on the skills and knowledge developed in [[OSD600]] by having the student take a partially developed students continue their work in open source project to completioncontribution. The student must Students should have an open source project in progress, along with a faculty mentor and coordinator approval, in order /community to which they want to enrollcontribute. Through first-hand experience the student , students will learn what is necessary to take move from "good first bug" style contribution toward becoming a working program and polishcommunity member able to work on all manner of bugs, refactorfeatures, and improve it on the way to making 1.0 product releaseother tasks.

* apply the concepts, techniques and principles acquired in previous programming and open source courses to the programming of a an open source project

This is a project course, and the student’s mark will come from work done on a real open source project. The goal of this project is to get students to move beyond "learning" and "hacking" on a piece of open source software, and to focus on creating something of excellent quality. Furthermore, students will be expected to create something of value within the community. As was the case in [[OSD600DPS909]], given the nature of the project, students will be expected to work using an open and transparent methodology, one which enables and encourages collaboration with the open source community.

* Each student must have an existing open source will focus on a particular project, preferably something in the 0.3 rangeor community. Students who don't have a an existing project/community, or who have a project of questionable value and potential, must work with their professor to find a suitable alternative quickly.* Each student will create, or continue working on an existing project wiki page. All project documentation, releases, and other deliverables should go in this wiki page--nothing is to be handed-in by hand, and all marking will be done out of the wiki page.

* Update your personal page on Students will be required to lead regular demo and teaching presentations, both within the class, and also via online tools (blog, wiki with permanent information, such as a list of your contributions to various projects.recordings, etc)

* '''70%''' 7 bi-weekly releases marked at 10% each''' must be completed. Assuming a project at version 0.3, this represents releases 0.4 through 1.0** Each release requires you should correspond to update your Project Wiki pagea bug being fixed, write a Blog postpull request being made, and make your release/code available on the web or in bugzillaetc. You will be marked every two weeks as follows:

* '''1510%''' 3 project demos marked at 5% each. Demos will be done for your professor and colleagues- Code, but will also be marked as on-line artifacts; that isprocess (e.g., did you will be expected to do something that can be shown on-line (screencasts/screenshotsit vs. did they land it), diagramscompleteness, blog postsquality, etc.)ambitiousness* '''155%- Demo, status update, review of what you''' final project presentationve learned, to be done in class and online

* [[Winter 2015 2018 DPS911 and OSD700 Resources]]