Winter 2008 OSD600 Weekly Schedule
From CDOT Wiki
- 1 Week 1 (Jan 8) Course introduction
- 2 Week 2 - Managing and Building large source trees
- 3 Week 3 - Build (Continued)
- 4 Week 4 - Navigating the Mozilla Source Tree
- 5 Week 5 – Bugs, Bugzilla, and Debugging
- 6 Week 6 – Developing the Browser
- 7 Week 7 – Release 0.1
- 8 Break Week
- 9 Week 8 – Toward 0.2
- 10 Week 9 – Extending the Browser
- 11 Week 10 – 0.2
- 12 Week 11 – Bug Fixing
- 13 Week 12 – XPCOM
- 14 Week 13 – Presentations / Major Project Due
- 15 Previous Versions of OSD600
Week 1 (Jan 8) Course introduction
- Course introduction
- Intro to open source
- Intro to Mozilla project
- Mozilla Communication Tools
- 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
- 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. Your personal page should initially include your contact information and a link to your blog; as you progress through the course, update this page with information about your work.
- Add your blog feed and info to the Open Source@Seneca Planet List so that it appears in the OpenSource@Seneca Planet
- Write a blog posting containing your reaction to and reflections on "The Catederal and the Bazaar" and "Revolution OS".
- Start lurking on irc.mozilla.org - especially the #seneca and #developers channels (Note: to access the #seneca channel, you must be registered - type "/nickserv help" in your IRC client or refer to http://freenode.net/faq.shtml#registering for more information)
- IRC tutorial - http://www.irchelp.org/irchelp/irctutorial.html#intro
Week 2 - Managing and Building large source trees
- Revision Control Systems (RCS)
- Introduction to RCS
- cvs, svn, hg
- Common concepts and tasks
- Local Working Copy
- RCS Changes (changesets) vs. Backups
- Typical read-only activities: Checkout, Update, Log, Status
- Using Make to build software
- Intro to Make
- Mozilla has over 50,000 Makefiles
- Building Mozilla from Source
- Getting started in Open Source projects, or "Learning to be at the festival" (on-line lecture) by David Humphrey (given at Mozilla24 in Stanford): Formats - mpg, ogg, mp4
- Two simple makefile examples
- How the Mozilla Build Works (on-line lecture) by Mozilla's J. Paul Reed
- Release Builds: from source tree to exe (on-line lecture) by Mozilla's Robert Helmer
- Complete all TODO items from Week 1
- Watch online lectures about the Mozilla build system.
- Practice creating a simple makefile
- Try performing a Debug Mozilla build on your home machine and blog about the experience
- Look at the Project List and Potential Projects pages and pick 3 projects on which you'd like to work--next week, you'll narrow this to just one. List them here along with your name so other students can see and groups can form.
Week 3 - Build (Continued)
- Do a Debug Mozilla build on your home machine and blog about the experience
- Finalize your project choice, form a group (if you are working in a group), and create a proper project page for your project in the Project List. See the full project instructions.
- Blog about your project selection and your plans for the next step.
- Learning to be Lost Productively
- Adding to Mozilla is not like writing a program from scratch
- Leverage the existing code by reading, studying, and copying existing code
- Mozilla Source Code structure and style
- Searching for Code
- How to Make Changes
- building with client.mk in mozilla/ vs. incremental builds
- Working with Patches
- Lab - Learning to use LXR/MXR effectively: Source Code Reading Lab - Blog about your experience.
- Lab - cvs diff and patch: Incremental Build Lab
- Practice doing incremental builds and applying patches
- Identify the main file(s) that your project will be changing and blog about your experience finding them and your observations about those files.
- State your 0.1 release target on your project's wiki page (explain what you will have completed by the time you reach 0.1 release). Discuss this with your professor (this can be done via IRC!).
- Review, and where appropriate, comment on blog postings by other students.
Week 5 – Bugs, Bugzilla, and Debugging
- What is a bug?
- Debugging Tools and Techniques
- C++ with VS.NET and gdb
- JS with Venkman
- Error Console
- Lab - Debugging Mozilla
- The Life-cycle of a Bug (on-line lecture) by Mozilla's Mike Connor
- Create a bugzilla account
- Find 5+ 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 (best to choose someone else related to your project)
- 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 – Developing the Browser
- Complete the lab and post a patch to your personal wiki page.
- Look at the list of current FF3/Gecko1.9 blocker bugs and CC yourself on three bugs that are related to your project, or that you find interesting.
- Write a blog summary of our experience watching a user in bugzilla from last week
- Write a blog summary updating your progress on your 0.1 release.
- Make sure your project wiki page is up to date and matches your 0.1 release goals.
- Start looking for opportunities to help other projects as part of your contrib mark. Each student should have a list of ways you can get involved on their project wiki page.
Week 7 – Release 0.1
- Finish your 0.1, release it (via your project Wiki), and blog about it (with a link to the release on your project page).
- Catch up on blogging.
- Plan your 0.2.
Week 8 – Toward 0.2
March 4 Guest: Mike Shaver
- Complete your 0.2 plan and update your project wiki page.
- Blog about your 0.2 plans as well as any help you need from other students
- Complete and add 1 new contribution to your personal list of contributions.
Week 9 – Extending the Browser
- Firefox Extensions
- Lab - Modifying the Browser Part II - writing an extension
- Video: Best practices & design patterns for add-ons by Mike Beltzner
- MozDev documentation on Extensions: http://developer.mozilla.org/en/docs/Extensions
- Personal HOWTO for creating an extension: http://roachfiend.com/archives/2004/12/08/how-to-create-firefox-extensions/
- Complete the lab and post the .xpi to your personal wiki page.
- Blog about your experience writing your first extension. What was hard? What did you find confusing?
- Complete your 0.1 release and write a blog post about what you've created, how to use it, and where to give feedback
Week 10 – 0.2
- Release your 0.2, update the project wiki page, and blog about it
Ben Hearsum visit -- Thursday
Week 11 – Bug Fixing
- Finding a bug, filing, fixing, patching
- Code Review, Module Owners and Peers
- Using CVS Log and Bonsai to determine who should review
- Good Examples of Bugs
- Lab - Fixing a bug in Thunderbird
- Complete this week's lab (hopefully during class time). Make sure you complete the Wiki and Blog requirements in the lab.
Week 12 – XPCOM
- Intro to XPCOM
- Optional Lab: Creating a Binary C++ XPCOM Component.
- Prepare your 0.3 release
Week 13 – Presentations / Major Project Due
- Complete this week's lab, put a zip with all your files on your personal wiki page when done, and blog about the experience.
- Prepare for a brief (10-20 minute) demo on Thursday.
- Catch up on your blogging!