DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule

From CDOT Wiki
Revision as of 10:29, 24 April 2009 by Wfred (talk | contribs) (→‎Week 13 (Apr 12) - Presenting Issues)
Jump to: navigation, search

Introduction

The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org 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 (Jan 12) - Course Introduction

  • TODO
    • Create an account on this wiki for yourself
    • Create a personal wiki page on this wiki


Week 2 (Jan 19) - Collaborative and Community Development Practices



  • 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.
    • Download the "Sun Microsystems Inc. Contributor Agreement (SCA)" from OpenOffice.Org Programming, sign it and email it to Copyrightfax@sun.com and CC it to Fardad.
    • Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.
    • Add this wiki page to your watch list.
    • Here is the IP addresses of the CDOT continent for you to log in to!
    • Setup distcc on assigned computers

Week 3 (Jan 26) - Complete distcc Installation, Managing and Building Large Source Trees

  • Revision Control Systems (RCS)
    • Introduction to RCS
    • cvs, svn, hg
    • Common concepts and tasks
      • Repository
      • Local working copy
      • Typical read-only activities: checkout, update
  • Using make to build software
  • Building large open source projects from source



Week 4 (Feb 2) - Building Open Office (Continued), Issues

  • Build
    • Complete your build and update relative build wiki pages
    • If completed move to next platform (at least two)
  • Issues
    • Filing or submitting rules
      • Only one problem per issue
      • Summary (recognizable, descriptive, meaningful)
      • Able to recreate (step by step instructions)
      • Providing samples
      • Use attachments
      • Avoid links, add relevant info. instead
    • Handling and "Life Cycle"
    • "Issue Tracker" (a modified version of Bugzilla)
  • Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)
  • TODO
    • Complete the build at least on two platforms
    • Collaborative-ly create and complete OOo Issues wiki page. A brief document from creating an issue to closing it.

Week 5 (Feb 9) - Navigating The Source Code


Week 6 (Feb 16) - Patches, Build, GDB

  • Guest lecturer Eric Bachard, lead of OOo Education Project
    • Patches
    • Build
    • GDB
  • Resources
  • TODO
    • Complete week 5 TODO
    • Test and experiment with patches ie. create, dry run, apply... (blog, wiki)
    • Use GDB and run OpenOffice in debug mode (blog, wiki)

Week 7 (Feb 23) - Selecting a Project (Issue)

Study break Week (Mar 02) - Study break

Week 8 (Mar 09) - Working on Issues

Resources to help you with your projects:

Week 9 (Mar 16) - Presenting Issues

Week 10 (Mar 23) - Presenting Issues

Week 11 (Mar 30) - Presenting Issues

  • Thu:
    • IRC: #OSD600

Week 12 (Apr 05) - Presenting Issues

  • Tue:
    • On IRC #OSD600
  • Thu:
    • On IRC #OSD600

Week 13 (Apr 12) - Presenting Issues


Resources to help you with your projects:

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&oldid=25662"