667
edits
Changes
no edit summary
===Details===
* Each student must pick a actively and independently participate in the course open source project from the list of proposed projects(s). This means using IRC, mailing lists, wikis, filing bugs, following bugs, writing patches, doing reviews, or have another project idea approved by the instructoretc. Projects have been created in consultation with the Mozilla community.* Students , and students are strongly encouraged not allowed to work individuallyon other projects (i.e., and only in rare circumstances suggesting your own project will partnerships not 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 Students are expected to work both ontheir own, 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 helppart of an active community, you can choose to get involved both with things. You are encouraged to use members of the [[Contrib Opportunities]] page to list class 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 pagethe wider open source community.
* 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.
Detailed grading information will be discussed later in the term. Below is a breakdown of how students will be graded, and [http://vocamus.net/dave/?p=680 this blog post] gives more details about the rationale:
* '''6080%''' - Project Deliverables (e.g., code, documents), marked in terms of quality, quantity, etc. Your project will be marked at four milestone releases, the number and values being:** '''1520%''' - 0.1 Release (Due Sept 2927)** '''1520%''' - 0.2 Release (Due Oct 2018)** '''1520%''' - 0.3 Release (Due Nov 1715)** '''1520%''' - 0.4 Release (Due Dec 86)
* '''20%''' - Project Wiki Page and Blog. You will be marked on your project and personal page's quality, depth of explanation, frequency of update, etc.
==Resources==
* [[DPS909 and OSD600 Fall 2011 2012 Weekly Schedule and Notes|Weekly Schedule and Notes]]* [[Fall 2011 2012 Open Source Students]]* [http://etherpad.mozilla.com:9000/ Mozilla's Etherpad] and [http://etherpad.cdot.proximity.on.ca:9000/ Seneca's Etherpad]
* [http://github.com Github]
* [[Git Cheatsheet and Gotchas]]
* [http://wiki.mozilla.org Mozilla Wiki]
* [https://developer.mozilla.org/en-US/ Mozilla Developer Network]
==Examples==
