Difference between revisions of "Development"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) (→Getting started with OOo development) |
m (→Education project) |
||
| (24 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == Getting started with | + | __TOC__ |
| − | + | == 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 your own OpenOffice so that you are able to modify things | ||
| + | {{Tip| The [[Documentation/Building_Guide_AOO|Building Guide]] will walk you through this.}} | ||
| − | + | === Fix a bug or an annoyance === | |
| + | Pick up your favorite bug/annoyance, and try to fix that. Read how to [[Contributing_Patches|Contribute a patch]] via Issue Tracker. | ||
| + | {{Tip| Browse [[https://bz.apache.org/ooo/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&field0-0-0=votes&type0-0-0=greaterthan&value0-0-0=50&order=issues.votes%20desc,%20issues.priority,%20issues.issue_type Top voted issues]] or review our [[To-Dos]] list that presents the key issues of interest to the core components}} | ||
| − | + | === 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 [https://openoffice.apache.org/mailing-lists.html development mailing list]. The list is friendly and supportive; the people want to help. | ||
| − | == | + | == Create an extension == |
| + | Extensions 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 [[Extensions_development|Extension development]] wiki page. The OpenOffice UNO component model is quite extensive and can be daunting at first. To help you, there is a comprehensive [[Documentation/DevGuide|Development Guide]]. The easiest way to get started is by using the plugins for [[OpenOffice_NetBeans_Integration|Netbeans]] and for [[OpenOffice_Eclipse_Integration|Eclipse]]. Plus, you can get help from the [https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public DEV mailing list]. | ||
| − | * [[ | + | == Development resources == |
| − | * [[ | + | * [[Documentation/Building Guide AOO|Building Guide]] |
| − | * [ | + | * [[Documentation/DevGuide|Development Guide]] |
| − | * [ | + | * [http://opengrok.adfinis-sygroup.org/source/ Opengrok] - source browser |
| − | * [ | + | * [http://api.openoffice.org OpenOffice.org API] |
| − | * [[Environment Variables]] - a description of handy environment variables used at runtime | + | * [https://issues.apache.org/ooo/ Bugtracker] |
| + | * [[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]] | ||
| − | * [[ | + | * [[Localization for developers]] |
| − | * [[ | + | * [[Build Bootstrapping]] |
| − | + | ||
| − | * [[ | + | == Further reading == |
| + | * [[IRC Communication|Meet the team on IRC]] | ||
* [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]] | * [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]] | ||
| + | * [[Tutorials]] - hacker tutorials to get the hang of the code | ||
| + | * [[Hacking]] | ||
| + | * [[Debugging]] - for when it all goes wrong | ||
| + | * [[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]] | ||
| + | * [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]] | ||
| + | |||
| + | == Education project == | ||
| + | {{Tip|If you don't find the instructions in the Wiki good enough to guide you or if you are interested in some aspect that is not covered, feel free to subscribe and ask on the [mailto:dev@openoffice.apache.org dev@openoffice.apache.org] mailing list. See [[Communication]] for more information on how to get in touch with the {{AOo}} project.}} | ||
| + | |||
| + | {{Tip|Another solution is to contact the [[Education Project]], which aims to find future OpenOffice developers, mainly students, who are discovering OpenOffice Project. Get in touch on IRC: [ircs://irc.libera.chat/openoffice #openoffice on Libera.Chat]}} | ||
| + | {{Tip|On the [[Education_ClassRoom|ClassRoom]] page, you will find more information about the essentials. For example [[Education_ClassRoom/Practice|Practice]], or [[Education_ClassRoom/Previous_Logs|IRC Meetings Logs]] we did as "ClassRooms".}} | ||
| − | [[Category:Development]] | + | ---- |
| + | <references/> | ||
| + | [[Category:Development]][[Category:Build System]][[Category:SCM]] | ||
Latest revision as of 14:04, 27 August 2021
Contents
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 your own OpenOffice so that you are able to modify things
 |
The Building Guide will walk you through this. |
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.
|
Browse [Top voted issues] or review our To-Dos list that presents the key issues of interest to the core components |
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 development mailing list. The list is friendly and supportive; the people want to help.
Create an extension
Extensions 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 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 the DEV mailing list.
Development resources
- Building Guide
- Development Guide
- Opengrok - source browser
- OpenOffice.org API
- Bugtracker
- Environment Variables - a description of handy environment variables used at runtime
- A description of the source directories
- Localization for developers
- Build Bootstrapping
Further reading
- Meet the team on IRC
- Using C++ with OOo SDK
- Tutorials - hacker tutorials to get the hang of the code
- Hacking
- Debugging - for when it all goes wrong
- 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++
Education project
|
If you don't find the instructions in the Wiki good enough to guide you or if you are interested in some aspect that is not covered, feel free to subscribe and ask on the dev@openoffice.apache.org mailing list. See Communication for more information on how to get in touch with the Apache OpenOffice project. |
|
Another solution is to contact the Education Project, which aims to find future OpenOffice developers, mainly students, who are discovering OpenOffice Project. Get in touch on IRC: #openoffice on Libera.Chat |
|
On the ClassRoom page, you will find more information about the essentials. For example Practice, or IRC Meetings Logs we did as "ClassRooms". |
