667
edits
Changes
no edit summary
==[http://cs.senecac.on.ca/index.php?outline=DPS911 Subject Description]==
This course builds on the skills and knowledge developed in [[DPS909]] 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.
==Course Outcomes==
* work on a real world software project
* solve implementation problems by working with existing open source technical documentation and existing code
* work in a self-directed manner to plan and complete a major open source programming project
* create appropriate technical and introductory documentation for a software product
* devise and implement a QA and testing strategy in order to insure the quality of the software being produced
* apply the concepts, techniques and principles acquired in previous programming and open source courses to the programming of a an open source project
* work within a community open source context, which means leveraging globally distributed tools and communication practices in order to include feedback in the development process
* participate in regular group meetings to review progress on the project
===Details===
* 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 List|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.
* Students are expected to be self-directed and highly motivated. It is the responsibility of the student to make sure that projects move forward, and that external dependencies are resolved quickly (e.g., problems getting info from someone on-line).
* Students will blog at least once per week. On your blog you should discuss the current iteration of your work, your thinking for future releases, and any interesting anecdotes or information about interactions with other people in the community.
* 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)
==Intellectual Property==
Detailed grading information will be discussed later in the term.
* '''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''' a written report due at the end of the term. Details TBA.ve learned, to be done in class and online
==Resources==
* [[Winter 2008 2018 DPS911-and OSD700 Weekly Schedule]]* [[Winter 2008 DPS911 Students]]* [[Project ListResources]]
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet]
==Archives==
* [[DPS911 Winter 2015]]
* [[DPS911 Winter 2014]]
* [[DPS911 Winter 2013]]
* [[DPS911 Winter 2010]]
* [[DPS911 Winter 2008]]
* [[DPS911 Winter 2009]]