DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule

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

• Course introduction
• Intro to open source
• Intro to the OpenOffice.org project
  • OpenOffice.org Overview
  • Becoming a contributor
  • Sun, Community

• 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)

• TODO
  • Create an account on this wiki for yourself
  • Create a personal wiki page on this wiki
  • Add a link for yourself to the People page and the Winter 2009 Open Source Students page
  • Create a blog (WordPress or Blogger 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 (Jan 19) - Collaborative and Community Development Practices

• Collaborative development using on-line tools
• Intro to Internet Relay Chat (IRC)
• Blogs and Planets
  • Novell's OpenOffice.org Planet
  • Planet OpenOffice.org
  • OpenSource@Seneca Planet
• 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)
    • How to Edit a page
  • Wikis used by OpenOffice.org
    • http://wiki.services.openoffice.org/wiki/Main_Page
    • http://wiki.services.openoffice.org/wiki/Education_Project

• Readings/Resources
  • Participating in OpenOffice.Org
  • OpenOffice.Org Programming
  • OpenOffice.Org Issues
  • OOo Education Classroom
  • SVN OOo
  • Source Control in Ten Minutes: a Subversion tutorial
  • DistCC

• 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
  • Intro to Make
• Building Large Open Source Projects from Source

• Readings/Resources (to be completed)
  • Version Control With Subversion (Online Book)
  • GNU Make
  • Two simple makefile examples
  • Cpp Coding Standards
  • Writer Code Conventions

• TODO (to be completed)
  • Install disstcc to work with all linux boxes at CDOT
  • Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.
  • Make two copies of the code and configure them; one to complie localy and other using distcc.
  • Start Building
    • OOo Fedora Build
    • OOo Mac Build
    • OOo Windows Build

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
    • Summery (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)
  • Priority Levels
  • Bug Writing Guidelines
  • Issue Life cycle
  • About Issues
• TODO
  • Complete the build at least on two platforms
  • Collaboratively 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

• Learning to be Lost Productively
  • Adding to Open Office is not like writing a program from scratch
  • Leverage the existing code by reading, studying, and copying existing code
• OpenOffice.org Source Code structure and style
  • Developers Guide
  • OOo directory structure
• Searching for Code
  • {OpenGrok
• How to Make Changes
  • Building
  • Installing
  • Hacking
  • Hackers Tutorials
• Hacking procedure on Fedora

• Resources
  • "Roundtrip to Shanghai via Tokyo!!!"
• TODO
  • complete week 4 TODO
  • run, maka a change, build, run

Week 6 (Feb 9) Patches, Build, GDB

• Guest Lecturer Eric Bachard, lead of OOo Education Project
  • Patches
  • Build
  • GDB
• Resources
  • (To Be Completed)
• TODO
  • complete week 5 TODO
  • (To be completed)