1
edit
Changes
m
→Week 5 (Oct 5) – Bugs, Bugzilla, and Debugging
** Begin work on your project, based on your initial project plan.
** Review, and where appropriate, comment on blog postings by other students.
== Week 5 (Oct 5) – Bugs, Bugzilla, and Debugging ==
* What is a bug?
** Open vs. Closed Bug Tracking - [http://www.arcanology.com/2007/09/19/ie-and-the-demise-of-borgzilla/ discussion of Mozilla vs Microsoft/IE]
** BMO - https://bugzilla.mozilla.org
** Searching for Bugs
** How to File a Bug
** Dupes, Depends, Blocks
** Following bugs through bugzilla
* Mozilla Bug Case Studies
** Adding animation support to the PNG format - For Firefox 3.0, [http://en.wikipedia.org/wiki/APNG animation support was added to PNG], and then Mozilla's image library. See the [http://littlesvr.ca/apng/ project page] and [https://bugzilla.mozilla.org/show_bug.cgi?id=257197 bug 257197].
** Plug-in Watcher - Give the browser (and extension developers) a way to monitor the CPU load for a plugin (e.g., Flash playing a movie). This feature shipped in Firefox 3.0. See the [http://zenit.senecac.on.ca/wiki/index.php/Plugin-watcher project page] and [https://bugzilla.mozilla.org/show_bug.cgi?id=412770 bug 412770].
** Adding GPS Support to Fennec on Windows CE - Mozilla was interested in getting GPS support added to the Windows CE platform for Fennec. This project added it, and it will ship as part of the first Fennec release. See the [http://zenit.senecac.on.ca/wiki/index.php/Add_GPS_Support_for_Windows_Mobile project page], [http://www.ndaversa.com/2009/04/21/10-release-update/ blog], [https://bugzilla.mozilla.org/show_bug.cgi?id=477557 bug 477557], and [https://bugzilla.mozilla.org/show_bug.cgi?id=482613 bug 482613].
** Mercurial Web Improvements - Mozilla's HG Web interface is written in Python, JavaScript, and jQuery. A number of enhancements where requested for Mozilla's needs. This project added this, fixing nine issues in all. See the [http://zenit.senecac.on.ca/wiki/index.php/Mercurial_history_browsing project page], [http://blog.sidkalra.com/ student blog], and bugs [https://bugzilla.mozilla.org/show_bug.cgi?id=459727 459727], [https://bugzilla.mozilla.org/show_bug.cgi?id=445560 445560], [https://bugzilla.mozilla.org/show_bug.cgi?id=448707 448707], [https://bugzilla.mozilla.org/show_bug.cgi?id=468089 468089], [https://bugzilla.mozilla.org/show_bug.cgi?id=459823 459823], [https://bugzilla.mozilla.org/show_bug.cgi?id=471321 471321], [https://bugzilla.mozilla.org/show_bug.cgi?id=453162 453162], [https://bugzilla.mozilla.org/show_bug.cgi?id=486939 486939].
* Debugging Tools and Techniques
** C++ with VS.NET and gdb
** JS with Venkman and Firebug
** DOMi
** Error Console
** Lab - [[Dive into Mozilla Debugging Mozilla Lab|Debugging Mozilla]]
* '''Guest Speakers'''
** [http://blog.mozilla.com/bhearsum/ Ben Hearsum] (bhearsum) and [http://armenzg.blogspot.com/ Armen Zambrano Gasparnian] (armenzg) of the Mozilla Build Team will be visiting the [[SBR600]] and [[DPS909]]/[[OSD600]] classes on Thursday.
** Please show our guests respect by being punctual.
** Bring your questions!
* '''Readings/Resources'''
** [[The Life-cycle of a Bug]] (on-line lecture) by Mozilla's Mike Connor
** [http://belmont.senecac.on.ca/pub/mozilla.lecture/lecture/mozilla-20073/vlad-debugging-seneca.avi Strategies for Debugging Mozilla] (on-line lecture) by Mozilla's Vladimir Vukićević
** [http://www.toolness.com/wp/?p=25 Account of fixing a first bug, by Mozilla's Atul Varma]
* '''TODO'''
** Create a [https://bugzilla.mozilla.org bugzilla] account
** Find 3+ bugs related to your project, and add them to your project wiki page
** CC yourself on two bugs that relate to your project
** Watch a user in bugzilla for the week and blog about the experience (e.g., ted, mfinkle, bsmedberg, or someone else related to your project)
** Be working on your 0.1 release. Ask for help if you're stuck
** Register for [http://fsoss.ca FSOSS] or join as a [[Volunteer|volunteer]].
** Come up with some ways for others to contribute to your project and add them to your project wiki page. Remember, you're asking for help, so be clear about what you need done, and make it easy so that people will pick you vs. another project.
== Week 6 (Oct 12) – Bug Fixing: Putting it all together (building, debugging, patches, bugs) ==
* Finding a bug, filing, fixing, patching
* [https://developer.mozilla.org/En/Developer_Guide/How_to_Submit_a_Patch Submitting a Patch for Review]
* Using '''cvs/hg log''', '''blame''', and the list of [https://developer.mozilla.org/en/Mozilla_Modules_and_Module_Ownership Module Owners] to determine who should review
* Good Examples of Bugs
** [https://bugzilla.mozilla.org/show_bug.cgi?id=343416 Bug 343416]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=335878 Bug 335878]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=132183 Bug 132183]
* Lab - [[Thunderbird Bug Fix Lab|Fixing a bug in Thunderbird]]
* '''Readings/Resources'''
** [https://developer.mozilla.org/En/Developer_Guide/How_to_Submit_a_Patch Submitting Getting your patch in the tree]
** [http://weblogs.mozillazine.org/lilmatt/2007/05/it_begins.html Personal blog account of fixing a bug]
** [http://fdiv.net/2007/05/15/the-secret-life-of-a-thunderbird-patch/#more-74 Personal blog account of fixing a bug in Thunderbird]
* '''TODO'''
** No class on Monday due to Thanksgiving.
** Complete work on your 0.1 release, updating your blog, your wiki page, etc. '''Due next week'''
** Register for [http://fsoss.ca FSOSS] or join as a [[Volunteer|volunteer]].
** Complete and add '''2 new contributions''' to your personal list of contributions.
** Complete this week's [[Thunderbird Bug Fix Lab|lab]] (hopefully during class time). Make sure you complete the '''Wiki''' and '''Blog''' requirements in the lab.
== Week 7 (Nov 2) – Modifying the Browser -- In Tree ==
* JavaScript development
* Debugging JavaScript
* Working with Chrome in the Source Tree
* JAR files
* Lab - [https://wiki.mozilla.org/Education/Learning/ModifyBrowser Modifying the Browser Lab]
* '''Readings/Resources'''
* Watch [http://www.youtube.com/watch?v=hQVTIJBZook JavaScript: The Good Parts] Google lecture by [http://www.crockford.com/ Douglas Crockford].
* '''TODO'''
** Blog about two things you learned about JavaScript while watching Crockford's talk. What surprised you most?
** Complete the [https://wiki.mozilla.org/Education/Learning/ModifyBrowser lab] and '''post a patch''' to your personal wiki page.
** Look for opportunities to help other projects as part of your contrib mark. Blog about things people can do for your project.
** Work on your 0.2 project release, blogging about your plans and progress.
** Remember that you are required to blog '''at least once per week'''.
