Difference between revisions of "DPS909 and OSD600 Fall 2010 Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
(Week 1 (Sept 7) Course introduction)
Line 81: Line 81:
 
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b>
 
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b>
 
** Watch online lectures for this week about open source community, blog your reactions.
 
** Watch online lectures for this week about open source community, blog your reactions.
 +
 +
 +
== Week 3 (Sept 20) – Bugs, Bugzilla, and Testing ==
 +
 +
* What is a bug?
 +
** Open vs. Closed Bug Tracking
 +
*** Microsoft - http://connect.microsoft.com/
 +
*** Mozilla - https://bugzilla.mozilla.org
 +
*** Chrome - http://code.google.com/p/chromium/issues/list
 +
** Searching for Bugs
 +
** How to File a Bug
 +
** Dupes, Depends, Blocks
 +
** Following bugs through bugzilla
 +
 +
* '''Readings/Resources'''
 +
** [[The Life-cycle of a Bug]] (on-line lecture) by Mozilla's Mike Connor
 +
** [http://www.toolness.com/wp/?p=25 Account of fixing a first bug, by Mozilla's Atul Varma]
 +
 +
* '''Lab'''
 +
** Continuing... [[Firefox Performance Testing Lab Fall 2010|Firefox Performance Testing]]
 +
 +
* '''TODO'''
 +
** Create a [https://bugzilla.mozilla.org bugzilla] account
 +
** CC yourself on some of the Chrome Experiments bugs in Mozilla's bugzilla
 +
** Work with #seneca on irc to figure out which bugs you need to file on your Chrome tests
 +
** Be working on your first project release.  Ask for help if you're stuck
 +
** Register for [http://fsoss.ca FSOSS] or join as a [[Volunteer|volunteer]].

Revision as of 14:40, 20 September 2010

Week 1 (Sept 7) Course introduction

  • TODO
    • Complete readings and watching/listening to this weeks resources.
    • Create an account on this wiki for yourself
    • Create a personal wiki page on this wiki, and add a link for yourself to the People page as well as the Winter 2010 students page
    • Create a blog (wordpress or blogspot or whatever) and create a feed category or tag called "open source"
    • Read the Blog Guidelines for instructions on how to use your blog in the course
    • Add your blog feed and info to the Open Source@Seneca Planet List so that it appears in the OpenSource@Seneca Planet
    • Blog on your reactions to the readings for this week, and also introduce yourself.
    • Begin learning how to use IRC for communication. We'll cover this in detail next week, but it's better to get started early.

Week 2 (Sept 13) - Collaborative and Community Development Practices

  • TODO
    • Ensure all TODO items from week 1 are completed
    • Complete Lab as a group by end of week
    • Begin (or continue) reading the CDOT Blog Planet, as this is where we will share class announcements and discussions.
    • Consider creating an account on Twitter to use in conjunction with your blog
    • Dial-in to one of the Mozilla Status calls happening this week, and blog about the experience. I'd recommend the Firefox call.
    • Join at least one Mozilla Mailing list
    • Comment in at least one other student's blog with your feedback to what they wrote. Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.
    • Watch online lectures for this week about open source community, blog your reactions.


Week 3 (Sept 20) – Bugs, Bugzilla, and Testing

  • TODO
    • Create a bugzilla account
    • CC yourself on some of the Chrome Experiments bugs in Mozilla's bugzilla
    • Work with #seneca on irc to figure out which bugs you need to file on your Chrome tests
    • Be working on your first project release. Ask for help if you're stuck
    • Register for FSOSS or join as a volunteer.