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

From CDOT Wiki
Jump to: navigation, search
m (→‎Week 4 (Feb 2)Building Open Office (Continued), Issues)
(→‎Week 5 (Feb 9) Navigating the source code)
Line 136: Line 136:
 
* How to Make Changes
 
* How to Make Changes
 
** [http://wiki.services.openoffice.org/wiki/Building Building]
 
** [http://wiki.services.openoffice.org/wiki/Building Building]
 +
** [[Installing]]
 
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]
 
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]
 
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers Tutorials]
 
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers Tutorials]

Revision as of 20:36, 14 February 2009

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



  • 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
      • 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)
  • 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
  • Searching for Code
  • How to Make Changes


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