Difference between revisions of "Fall 2007 Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
m
(→‎Week 6 (Oct 8) – Developing the Browser)
Line 152: Line 152:
  
 
* '''TODO'''
 
* '''TODO'''
 +
** Complete the [[Modifying the Browser Lab|lab]] and '''post a patch''' to your personal wiki page.
 
** Look at the [http://developer.mozilla.org/devnews/index.php/2007/10/08/keeping-an-eye-on-blockers/ 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.
 
** Look at the [http://developer.mozilla.org/devnews/index.php/2007/10/08/keeping-an-eye-on-blockers/ 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''' of our experience '''watching a user in bugzilla''' from last week

Revision as of 11:36, 9 October 2007

Introduction

The fall is broken into two parts. First, open source and Mozilla specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the Mozilla project and its community. Second, students are taught about Mozilla’s extensibility model, and how to write Firefox Addons and Extensions.

Part I – Essential Mozilla Development Skills and Concepts

Week 1 (Sept 3) Course introduction

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

Week 3 (Sept 17) - Managing and Building large source trees

  • Revision Control Systems (RCS)
    • Introduction to RCS
    • cvs, svn, hg
    • Common concepts and tasks
      • Repository
      • 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
  • TODO
    • Watch online lectures about the Mozilla build system.
    • Practice creating a simple makefile
    • 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.
  • NOTE
    • Thursday's class will be special, as we will have a guest speaker flying here to talk to you about the build. Please have your build done before Thursday so you can ask questions and understand what he's talking about.

Week 4 (Sept 24) - Navigating the Mozilla source tree

  • TODO
    • 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.
    • Review, and where appropriate, comment on blog postings by other students.

Week 5 (Oct 1) – Bugs, Bugzilla, and Debugging

  • TODO
    • 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 (Ted, Andrew, 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 (Oct 8) – Developing the Browser

  • Readings/Resources
  • TBA
  • TODO
    • 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.
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Fall_2007_Weekly_Schedule&oldid=13082"