Difference between revisions of "DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
(Week 10 (Mar 16) - Presenting Issues)
Line 186: Line 186:
**Name4, Issue, Issue Link.
**Name4, Issue, Issue Link.
* Thu:  
* Thu:  
**Name5, Issue, Issue Link.
**Daeseon Moon, Issue, Issue Link.
**Name6, Issue, Issue Link.
**Name6, Issue, Issue Link.

Revision as of 12:08, 17 March 2009


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

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

Week 8 (Mar 02) -

Week 9 (Mar 09) -

  • Tue: filling spots
  • Thu:
    • Name1, Issue, Issue Link.
    • Name2, Issue, Issue Link.

Week 10 (Mar 16) - Presenting Issues

  • Tue:
    • Name3, Issue, Issue Link.
    • Name4, Issue, Issue Link.
  • Thu:
    • Daeseon Moon, Issue, Issue Link.
    • Name6, Issue, Issue Link.

Week 11 (Mar 23) - Presenting Issues

  • Tue:
    • Name7, Issue, Issue Link.
    • Name1, Issue, Issue Link.
  • Thu:
    • Daeseon Moon, Issue, Issue Link.
    • Name3, Issue, Issue Link.

Week 12 (Mar 30) - Presenting Issues

  • Tue:
    • Name4, Issue, Issue Link.
    • Jerry Pau, Issue, Issue Link.
  • Thu:
    • Fred Wang, Issue, Issue Link.
    • Bartosz Barcicki, Issue, Issue Link.

Week 13 (Apr 06) - Presenting Issues