Difference between revisions of "I want to be an OpenOffice.org developer"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) (→Becoming an OpenOffice.org developer) |
B michaelsen (Talk | contribs) m (moved warning-free code and and compiler versions here, removed links to outdated pages) |
||
| Line 26: | Line 26: | ||
* [[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 | ||
* [[Tips]] - misc. hints & tips. | * [[Tips]] - misc. hints & tips. | ||
| − | * [ | + | * [[Compiler versions used by port maintainers and release engineers]] |
| − | * [ | + | * [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]] |
| − | + | ||
== Education project == | == Education project == | ||
Revision as of 15:34, 20 October 2009
Contents
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
- 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
- Development Guide
- Opengrok - source browser
- Mercurial-Webinterface
- OpenOffice.org API
- Environment Information System also called EIS, more infos can be found here.
- Environment Variables - a description of handy environment variables used at runtime
- A description of the source directories
Further reading
- Tutorials - hacker tutorials to get the hang of the code
- Hacking
- Debugging - for when it all goes wrong
- OOo and Mercurial and OOo and Subversion - How to use the SCMs that OOo uses
- 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
- Tips - misc. hints & tips.
- Compiler versions used by port maintainers and release engineers
- Warning-free Code and Correct C++
