DPS909 and OSD600 Fall 2008 Weekly Schedule
Contents
- 1 Introduction
- 2 Part I – Essential Open Source Development Skills and Concepts
- 2.1 Week 1 (Sept 1) Course introduction
- 2.2 Week 2 (Sept 8) - Collaborative and Community Development Practices
- 2.3 Week 3 (Sept 15) - Managing and Building large source trees
- 2.4 Week 4 (Sept 22) - Navigating the Mozilla source tree
- 2.5 Week 5 (Sept 29) – Bugs, Bugzilla, and Debugging
- 2.6 Week 6 (Oct 13) – Bug Fixing
- 2.7 Week 7 (Oct 27) – Modifying the Browser -- In Tree
- 2.8 Week 8 (Nov 3) – Modifying the Browser -- Extensions
- 2.9 Week 9 (Nov 10) - XPCOM Part I: Modular C++ Development in Mozilla
- 2.10 Week 10 (Nov 17) - XPCOM Part II: Using XPCOM
- 2.11 Week 11 (Nov 24) – Chrome
Introduction
The fall is broken into two parts. First, general open source and and community (i.e., Mozilla) specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of their chosen project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.
Part I – Essential Open Source Development Skills and Concepts
Week 1 (Sept 1) Course introduction
- Course introduction
- Intro to open source
- Intro to Mozilla project
- Mozilla Project Overview
- Community, Foundation, Corporation
- The Mozilla Manifesto
- Mozilla platform and technologies
- Intro to the OpenOffice.org project
- Readings/Resources
- "Cathedral and Bazaar" by Eric Raymond
- "Revolution OS" [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)
- Mike Shaver discusses the Mozilla Manifesto [MP3]
- TODO
- 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
- 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.
- 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 8) - Collaborative and Community Development Practices
- Collaborative development using on-line tools
- Intro to Internet Relay Chat (IRC)
- Blogs and Planets
- Using Wikis for collaborative writing
- Wikipedia and MediaWiki
- Intro to course wiki
- "Yes, you can edit it!"
- Common Editing tasks, History, Reverting changes
- Watches, Recent Changes
- Comparing selected versions (cf. diff)
- Editing help
- Wikis used by Mozilla and OpenOffice.org
- http://developer.mozilla.org (a.k.a., devmo, MDC)
- http://wiki.mozilla.org (a.k.a., wmo or wiki.m.o)
- http://wiki.services.openoffice.org/wiki/Main_Page
- Project discussion
- Guests
-
On Thursday September 11th during class, we'll be joined by OpenOffice.org's Community Manger, Louis Suarez-Potts . Louis will talk about open source community, the OpenOffice.org project, and answer your questions.Postponed - Also on Thursday September 11th from 5:00 - 6:00, the Fedora project leader, Paul Frields, will be hosting an IRC discussion on freenode:#seneca for the LUX students. You are encouraged to join and listen to Paul discuss the Fedora project, Linux, and how their community works. You can also see a video of Paul talking about Fedora here.
-
- Readings/Resources
- Mozilla Community (on-line lecture) by Mozilla's Mike Beltzner
- 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
- Learning Collaborative Development Lab Fall 2008
- TODO
- Ensure all TODO items from week 1 are completed
- 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
- Complete this week's lab by Friday.
- Look at the Potential Projects page 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.
- Add your wiki page to the class list for your section: Students in DPS909 Fall 2008 or Students in OSD600 Fall 2008
Week 3 (Sept 15) - Managing and Building large source trees
- Revision Control Systems (RCS)
- Using Make to build software
- Intro to Make
- Building Large Open Source Projects from Source
- Readings/Resources
- 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
- Mozilla's Build System (on-line lecture) by Mozilla's Ted Mielczarek
- TODO
- Watch online lectures about the Mozilla build system.
- Attend part/all of the Mozilla Developer Day (T1014, S1209) and blog about your experience, what you learned, who you met, etc.
- Create a simple makefile
- Do the lab on your home machine and blog about the experience. Note: Do not put build output in your blog. You can use your wiki pages for that. The blog should be commentary on the experience of building a large piece of open source software.
- Pick your project and start working on it. Create a proper project page for your project in the Project List. See instructions here.
- NOTE
- Tuesday's class will be special, since the Mozilla Developer Day will be happening downstairs in T1014, and S1209. You are all invited to attend any/all of the Monday/Tuesday sessions. There will be no formal class/lab, as we will be attending the event.
- 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 vs. incremental builds
- Working with Patches
- Readings/Resources
- Reading: Chapter 11 (pages 379-397) of Diomidis Spinellis, Code Reading: The Open Source Perspective, ISDN 0-201-79940-5 - information about the book - eBook version via Seneca Library and Safari
- TODO
- Lab - Source Code Reading Lab
- Lab - Working with patches
- 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.
- Review, and where appropriate, comment on blog postings by other students.
Week 5 (Sept 29) – Bugs, Bugzilla, and Debugging
- What is a bug?
- Open vs. Closed Bug Tracking - 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
- Debugging Tools and Techniques
- C++ with VS.NET and gdb
- JS with Venkman and Firebug
- DOMi
- Error Console
- Lab - Debugging Mozilla
- Readings/Resources
- The Life-cycle of a Bug (on-line lecture) by Mozilla's Mike Connor
- Strategies for Debugging Mozilla (on-line lecture) by Mozilla's Vladimir Vukićević
- Account of fixing a first bug, by Mozilla's Atul Varma
- TODO
- Create a 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 FSOSS or join as a 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 13) – Bug Fixing
- Finding a bug, filing, fixing, patching
- Code Review, Module Owners and Peers
- Using cvs/hg log and bonsai to determine who should review
- Good Examples of Bugs
- Lab - Fixing a bug in Thunderbird
- Readings/Resources
- TODO
- Be working on your 0.1 release, updating your blog, your wiki page, etc.
- Register for FSOSS or join as a volunteer.
- Complete and add 2 new contributions to your personal list of contributions.
- Complete this week's lab (hopefully during class time). Make sure you complete the Wiki and Blog requirements in the lab.
Week 7 (Oct 27) – Modifying the Browser -- In Tree
- Readings/Resources
- TBA
- TODO
- Complete the lab and post a patch to your personal wiki page.
- 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 8 (Nov 3) – Modifying the Browser -- Extensions
- Readings/Resources
- 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/
- Building Firefox Extensions (on-line lecture) by Mozilla's Mark Finkle
- Video: Best practices & design patterns for add-ons by Mike Beltzner
- TODO
- Complete the lab and post the .xpi to your personal wiki page.
- Be working on your 0.2 release and write a blog post to update everyone on what you're planning, what you've done since 0.1, etc.
Week 9 (Nov 10) - XPCOM Part I: Modular C++ Development in Mozilla
- Intro to XPCOM
- XPCOM can be built in C++ or using JS
- Components, Interfaces, and XPIDL
- Lab: Creating a Binary C++ XPCOM Component. Use pre-built tree here if you don't have a Firefox build. NOTE: must be extracted to C:\temp.
- Readings/Resources
- Introduction to XPCOM (on-line lecture) by Mozilla's Benjamin Smedberg
- Benjamin Smedberg's XPCOM Slides
- "Creating XPCOM Components" -- an excellent on-line book working step-by-step through creating a real XPCOM component.
- JS Component Wizard
- TODO
- 0.2 release is due sometime this week.
- Update your wiki page
- Upload your release "code"
- Blog about your release, giving any instructions on how to use it, screenshots of it being used, etc.
- Begin the lab. Because your 0.2 is due this week, you are not require do to complete the lab until next week. Put a zip with all your lab files on your personal wiki page when done.
- 0.2 release is due sometime this week.
- NOTE
- Thursday's class will be special, as we will have a guest speaker (Tom Aratyn) coming to talk about Extension Development.
Week 10 (Nov 17) - XPCOM Part II: Using XPCOM
- Review of XPCOM
- Using XPCOM Components
- Lab: Creating a Binary C++ XPCOM Component. Use pre-built tree here if you don't have a Firefox build. NOTE: must be extracted to C:\temp.
- Readings/Resources
- Introduction to XPCOM (on-line lecture) by Mozilla's Benjamin Smedberg
- Benjamin Smedberg's XPCOM Slides
- "Creating XPCOM Components" -- an excellent on-line book working step-by-step through creating a real XPCOM component.
- TODO
- 0.3 release.
- Finish the lab. Put a zip with all your lab files on your personal wiki page when done.
Week 11 (Nov 24) – Chrome
- XUL
- XUL Overlays
- Common XUL Widgets
- Lab: adding chrome/UI to the FirstXpcom component
- Readings/Resources
- TODO
- Complete lab and blog about the experience
- Update your project wiki page with a final roadmap for your 0.3 release, as well as what you've done to date.