Difference between revisions of "Development"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Added and updated some links.)
(cleanup of the most important infos for Apache OpenOffice)
Line 1: Line 1:
 
__TOC__
 
__TOC__
== Getting started with OOo development ==
+
== Getting started with Apache OpenOffice development ==
  
You are at the start of a long, but very exciting journey! OpenOffice.org is a large and inclusive project. No matter what your interests are, there is always a place for you here. There are many ways to get started, but the easiest one is to:
+
You are at the start of a long, but very exciting journey! Apache OpenOffice is a large and inclusive project. No matter what your interests are, there is always a place for you here. There are many ways to get started, but the easiest one is to:
  
 
=== Get the source code and start building ===
 
=== Get the source code and start building ===
Build you own OpenOffice.org so that you are able to modify things
+
Build you own OpenOffice so that you are able to modify things
{{Template:Documentation/Tip| The [[Documentation/Building_Guide|Building Guide]] will walk you through this.}}
+
{{Template:Documentation/Tip| The [[Documentation/Building_Guide_AOO|Building Guide]] will walk you through this.}}
  
 
=== Fix a bug or an annoyance ===
 
=== Fix a bug or an annoyance ===
Line 13: Line 13:
  
 
=== Contribute more ===
 
=== Contribute more ===
When you see that hacking OOo pleases you, it's time to look for bigger tasks, get in contact on [[IRC]] or on the mailing list: mailto:dev@openoffice.org The list is friendly and supportive; the people want to help.
+
When you see that hacking AOO pleases you, it's time to look for bigger tasks, get in contact on [[IRC]] or on the mailing list: mailto:ooo-dev@openoffice.apache.org The list is friendly and supportive; the people want to help.
  
  
Line 23: Line 23:
 
* [[Documentation/Building Guide AOO|Building Guide]]
 
* [[Documentation/Building Guide AOO|Building Guide]]
 
* [[Documentation/DevGuide|Development Guide]]
 
* [[Documentation/DevGuide|Development Guide]]
* [http://svn.services.openoffice.org/opengrok/ Opengrok] - source browser
+
* [http://opengrok.adfinis-sygroup.org/source/ Opengrok] - source browser
* [http://hg.services.openoffice.org/hg/ Mercurial-Webinterface]
+
 
* [http://api.openoffice.org OpenOffice.org API]
 
* [http://api.openoffice.org OpenOffice.org API]
* [http://eis.services.openoffice.org/ Environment Information System also called EIS], more infos can be found [[EIS|here]].
+
* [https://issues.apache.org/ooo/ Bugtracker]
* [http://qa.openoffice.org/issues/ Bugtracker]
+
 
* [[Environment Variables]] - a description of handy environment variables used at runtime  
 
* [[Environment Variables]] - a description of handy environment variables used at runtime  
 
* [[Source code directories| A description of the source directories]]
 
* [[Source code directories| A description of the source directories]]
Line 39: Line 37:
 
* [[Hacking]]
 
* [[Hacking]]
 
* [[Debugging]] - for when it all goes wrong  
 
* [[Debugging]] - for when it all goes wrong  
* [[Mercurial]] and [[OOo and Subversion]] - How to use the SCMs that OOo uses
 
 
* [[Contributing Patches]] - for when you have something to fold back
 
* [[Contributing Patches]] - for when you have something to fold back
 
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them  
 
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them  
Line 45: Line 42:
 
* [[Compiler versions used by port maintainers and release engineers]]  
 
* [[Compiler versions used by port maintainers and release engineers]]  
 
* [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]]  
 
* [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]]  
* [[Tinderbox]] - test new child workspaces and show your build logfile to others
 
  
 
== Education project ==
 
== Education project ==

Revision as of 10:28, 2 November 2012

Getting started with Apache OpenOffice development

You are at the start of a long, but very exciting journey! Apache OpenOffice is a large and inclusive project. No matter what your interests are, there is always a place for you here. There are many ways to get started, but the easiest one is to:

Get the source code and start building

Build you own OpenOffice so that you are able to modify things


Fix a bug or an annoyance

Pick up your favorite bug/annoyance, and try to fix that. Read how to Contribute a patch via Issue Tracker.


Contribute more

When you see that hacking AOO pleases you, it's time to look for bigger tasks, get in contact on IRC or on the mailing list: mailto:ooo-dev@openoffice.apache.org The list is friendly and supportive; the people want to help.


Create an extension

Exensions are easy to write and fun to see in action. You can add features that millions of others will use by using Java, Python, StarBasic, or JavaScript. Find more on Extension development wiki page. The OpenOffice.org UNO component model is quite extensive and can be daunting at first. To help you, there is a comprehensive Development Guide. The easiest way to get started is by using the plugins for Netbeans and for Eclipse. Plus, you can get help from mailto:dev@api.openoffice.org.


Development resources

Further reading

Education project





Personal tools