Development/Simplifying entry for new developers
Contents
Purpose of this initiative
This is an initiative started to make it easier for new developers to start to contribute to the project.
It identifies several issues which together might make contributing harder for interested developers.
The solutions will be applied to the contributing and development websites.
Workplaces
- https://openoffice.apache.org/get-involved.html
- https://www.openoffice.org/development/tryouts/index.html
Possible issues
These are the possible problems identified:
Building the software
This effort is now here: Apache OpenOffice Building Guide
CVS and SVN are both outdated.
Articles covering code which is nowdays available in Mercurial instead should be updated.
Contribution - Programming
The page has a strange introduction, that begins with a to do list. Maybe the user already has an idea of what he would like to do. The page tells the user to start building the code. The programmer should learn what it is like to develop in the community first.
https://openoffice.apache.org/get-involved.html
Building on Windows
Promotes ooo-build and says building the Vanilla build is painful.
https://wiki.openoffice.org/wiki/Windows#Using_vanilla_source
I want to be an OpenOffice developer wiki page
Suggest to delete the following page.
I want to be an OpenOffice developer
 |
That page has been recently updated. I consider it useful in its current state, although the page title is awkward. So, move maybe - but not delete. Also, it is linked from the Main Page currently. Maybe I want to be an OpenOffice developer should be merged into Development, and then made a redirect to that page. --B michaelsen 22:36, 7 November 2009 (UTC) |
Getting the source code
Create a guide that works for all operating systems, that everyone can point to.
 |
Implemented. See: Documentation/Building_Guide_AOO |
Build Windows Tcsh
Is this page still valid?
http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#BuildRequirements
|
No thats totally outdated. --B michaelsen 22:36, 7 November 2009 (UTC) |
Installing
Installing only has content about the ooobuild fork, not about real OOo.
Developer Types
New developers
- Will start at contributing/development
- Want to know what is required of him/her
- Want to learn the basics
- Want to learn only the things that is required to do the work
Existing developers
- Will start directly at development
- Want to get reference documentation
- Want to have this information close at hand
API Developers/Core Developers
Some devs might only want to develop extensions or by using the API, others might want to extend OOo itself.
These pages may be related or interesting to new developers.
- https://openoffice.apache.org/get-involved.html
- https://www.openoffice.org/development/
- https://www.openoffice.org/tools/
- https://www.openoffice.org/qa/issue_handling/project_issues.html
- https://www.openoffice.org/projects/accepted.html
- https://www.openoffice.org/api/DevelopersGuide/DevelopersGuide.html
- https://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide
- https://www.openoffice.org/licenses/sca.pdf
- https://www.openoffice.org/FAQs/faq-licensing.html#usinglicenses
- https://www.openoffice.org/copyright/copyrightapproved.html
- https://www.openoffice.org/dev_docs/guidelines.html
- Development
- To-Dos
- Contributing_Patches
- I want to be an OpenOffice developer
- Documentation/Building Guide AOO
- Building_OpenOffice.org
- Hacking
- Summer_of_Code_2008/proposals
- Cpp_Coding_Standards
- Extensions_development
- Extensions_development_java
- Extensions_development_basic
- Extensions_development_python
- Documentation/BASIC_Guide
- Uno/Cpp/Tutorials/Introduction_to_Cpp_Uno
- Using_Cpp_with_the_OOo_SDK
- Education_Project
- Education_ClassRoom/Practice
- Windows
Contributing Members
Per Eriksson
Martin Hollmichel
Mathias Bauer
Bjoern Michaelsen
