Difference between revisions of "I want to be an OpenOffice.org developer"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Development resources)
Line 23: Line 23:
 
* [[Hacking]]
 
* [[Hacking]]
 
* [[Debugging]] - for when it all goes wrong  
 
* [[Debugging]] - for when it all goes wrong  
* [[OOo and Mercurial]] and [[OOo and Subversion]] - How to use the SCMs that OOo uses
+
* [[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  

Revision as of 15:30, 27 October 2009

Becoming an OpenOffice.org developer

Your first build

You are at the start of a long, but very exciting journey! There are many ways to get started, but the easiest one is to:

  • Get the source code and build you own OpenOffice.org so that you are able to modify things

Template:Documentation/Note

  • Pick up your favorite bug/annoyance, and try to fix that
  • When you see that hacking OOo pleases you, it's time to look for bigger tasks, get in contact on IRC


Development resources

Further reading

Education project

Template:Documentation/Tip

Template:Documentation/Tip

Template:Documentation/Tip

Personal tools