Skip to content

start:

Participate in OpenOffice.org

Programming

Programming

OpenOffice.org is a large and inclusive project. No matter what your interests are, there is always a place for you here. Unfortunately, new contributors often don't know where to begin.

The good news is that we have a good To-dos list. It complements our general Development Category, which lists most of the tools a developer will need to get started. Be sure to checkout our wiki, as it has lots of useful information.

Plus, we are here to help. Send an email to dev@openoffice.org and we'll help you get started. The list is friendly and supportive; the people want to help. Meanwhile, here are some ideas for you:

  1. Visit the Development Category homepage
    The Development Category is the necessary resource for anyone interested in working on OpenOffice.org code or wanting to write add ons, and so on. It links to all tools, documentation, snippets, and information that a developer or any coder. Our wiki for developers is equally invaluable.

  2. Review the To-Dos
    Our to-dos page presents the key issues of interest to the core components. Recommended for all contributors prior to working on the OpenOffice.org code.

  3. Add a feature
    Most of OpenOffice.org is written in C++. However, new features can be added using Java, Python, StarBasic, or JavaScript. The OpenOffice.org component model is quite extensive and can be daunting at first. To help you, there is a comprehensive Developers Guide. Plus, you can get help from dev@api.openoffice.org.

  4. Contribute to a core module
    Core components are written in C++. If you know C++ you can start by finding the project or component that interests you. Join that project's mailing list and introduce yourself. You will probably need to familiarize yourself with the Developers Guide.

  5. Create an extension
    Exensions are easy to write and fun to see in action. With relatively little effort, you can add features that millions of others will use. Extensions can be proprietary or open, and they can tie into the depths of the code or simply link up to it. It's all up to you. For more information, look at our repository and our developer wiki on the subject.

  6. Fix a bug
    In most cases this will require knowing C++ and sometimes Java. Start by finding a bug that itches you. Then contact the development list and we will help you fix it.

  7. Use your XML knowledge
    OpenOffice.org uses XML for all of its files. XSLT tools are available to support non-native XML. If you know XML and XSLT there is much you can do here. For instance, you can provide an SVG input transformation so OpenOffice.org can open SVG files.

  8. Spread the file format
    The OpenOffice.org file format is just a collection of zipped XML files. And the technology generating them is interesting. Take a look at our ODF toolkit project for more information on this.

  9. Work on a current top request
    We usually have a set of must-dos, but these tend to change. Ask the development list for help.

Say you just want to send us a patch. Great! Here's what to do:

How to submit code to OpenOffice.org

We ask that all code submitted to OpenOffice.org be submitted via Issue Tracker . In your submission please list "Issue Type" as PATCH. Your code will be sent to the committer for the appropriate project.

Submit a signed and filled-out copy of the Sun Microsystems Inc. Contributor Agreement (SCA) . It is a pdf and you must print it out and send it to: 

Fax: +1-408-549-9923 
- or - 
Mail a signed original to: 
Eric Renaud 
OpenOffice.org/Sun Microsystems 
4120 Network Circle, USCA12-105 
Santa Clara, CA 95054 USA 
- or - 
Scan a signed original and email to Copyrightfax@sun.com

We explain our reasons for requiring the SCA in the Licensing FAQ. The FAQ further explain the use and advantages of our copyright policy.

In order for your code to be committed to the source tree:

  • Your SCA must have been received. This Agreement covers all submissions of code.
  • The committer must approve your code for submission.

OpenOffice.org maintains a list of persons and companies who have filed a copyright assignment. If you have filed an Agreement or prior form and your name is not on the list, please contact us.

You might also find it useful to visit our Guidelines for Participate in OpenOffice.org page, which outlines the way in which your work can be channeled into this project.