Difference between revisions of "FAQ OpenOffice.org and NeoOffice"
(remove obsolete OOo X11 item, reorder items and clarify some text) |
m (some rewording and minor text moves) |
||
| Line 6: | Line 6: | ||
Users and many organizations benefit from the power and the generous license of the project. The original license even allowed taking all the code, documentation, templates, etc. and not contributing anything back into the project. This resulted in many forks: | Users and many organizations benefit from the power and the generous license of the project. The original license even allowed taking all the code, documentation, templates, etc. and not contributing anything back into the project. This resulted in many forks: | ||
| − | * OpenOffice.org | + | * the core project: OpenOffice.org |
* Lotus Symphony | * Lotus Symphony | ||
* RedOffice | * RedOffice | ||
| Line 16: | Line 16: | ||
* etc. | * etc. | ||
| − | There are different kinds of collaboration between the projects. They all have in common that they take the new features, improvements, and the many bugfixes from the core project and extend it to their needs. Some of the projects contribute all their changes back. Some projects contribute developer power for isolating problems. Some projects contribute by writing good bug reports to get the upstream developers involved. Some projects just replace the branding and sell it as their product. Some just take and never give back and instead threaten with lawsuits if the core project | + | There are different kinds of collaboration between the projects. They all have in common that they take the new features, improvements, and the many bugfixes from the core project and extend it to their needs. Some of the projects contribute all their changes back. Some projects contribute developer power for isolating problems. Some projects contribute by writing good bug reports to get the upstream developers involved. Some projects just replace the branding and sell it as their product. Some just take and never give back and instead threaten with lawsuits if the core project touches their niche. |
Since specialized needs of these forks are sometimes not directly applicable to the core project and the effort needed to integrate their changes into such a complex multi-platform, multi-language office suite require valuable development and testing resources there will always be the temporary need for specialized branches of the core project. We always work on making the core project as generally useful as possible, so the goal is to reduce the need for non-core forks. | Since specialized needs of these forks are sometimes not directly applicable to the core project and the effort needed to integrate their changes into such a complex multi-platform, multi-language office suite require valuable development and testing resources there will always be the temporary need for specialized branches of the core project. We always work on making the core project as generally useful as possible, so the goal is to reduce the need for non-core forks. | ||
| Line 26: | Line 26: | ||
'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. Due to license incompatibilities NeoOffice code does not contribute back to OpenOffice.org, and usually does not help to fix OpenOffice.org bugs. | '''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. Due to license incompatibilities NeoOffice code does not contribute back to OpenOffice.org, and usually does not help to fix OpenOffice.org bugs. | ||
| − | Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way). | + | Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way). It is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI). |
| − | NeoOffice | + | NeoOffice used a subclause of OpenOffice.org's license to change it to another license which is incompatible with the core project. so, to avoid legal issues, OpenOffice.org developers had to rewrite some subsystems, since NeoOffice code cannot be used in OpenOffice.org. Even when the licence for a fork change was compatible with the core project other kinds of legal threats were [[http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1187 used]]. |
| − | + | ||
| − | + | ||
More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice] | More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice] | ||
| Line 72: | Line 70: | ||
The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''. | The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''. | ||
So every change must be rewritten for OpenOffice.org project, using another implementation. | So every change must be rewritten for OpenOffice.org project, using another implementation. | ||
| − | |||
A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon. | A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon. | ||
Further informations are available at: '''http://porting.openoffice.org/mac/''' | Further informations are available at: '''http://porting.openoffice.org/mac/''' | ||
Revision as of 14:27, 6 January 2009
Contents
- 1 What is OpenOffice.org
- 2 What is NeoOffice?
- 3 OpenOffice.org Aqua
- 4 Q1: Where can I find OpenOffice.org or NeoOffice?
- 5 Q2: Why does there seem to be several parallel efforts?
- 6 Q3: Where do I get support for OpenOffice.org Mac/Aqua ?
- 7 Q4: But it would be more efficient, if there would be only one effort...
What is OpenOffice.org
OpenOffice.org is the name of productivity application suite, the project and the website. Please note the .org part of the project name, which is needed for legal reasons.
Users and many organizations benefit from the power and the generous license of the project. The original license even allowed taking all the code, documentation, templates, etc. and not contributing anything back into the project. This resulted in many forks:
- the core project: OpenOffice.org
- Lotus Symphony
- RedOffice
- Go-OOo
- OxygenOffice
- NeoOffice
- Luxuriosity Office
- MagyarOffice
- etc.
There are different kinds of collaboration between the projects. They all have in common that they take the new features, improvements, and the many bugfixes from the core project and extend it to their needs. Some of the projects contribute all their changes back. Some projects contribute developer power for isolating problems. Some projects contribute by writing good bug reports to get the upstream developers involved. Some projects just replace the branding and sell it as their product. Some just take and never give back and instead threaten with lawsuits if the core project touches their niche.
Since specialized needs of these forks are sometimes not directly applicable to the core project and the effort needed to integrate their changes into such a complex multi-platform, multi-language office suite require valuable development and testing resources there will always be the temporary need for specialized branches of the core project. We always work on making the core project as generally useful as possible, so the goal is to reduce the need for non-core forks.
What is NeoOffice?
NeoOffice is one of these forks, which specialized in making the power of OpenOffice.org available for Mac OS X.
Fork Means NeoOffice is another project, and is not OpenOffice.org. Due to license incompatibilities NeoOffice code does not contribute back to OpenOffice.org, and usually does not help to fix OpenOffice.org bugs.
Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way). It is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).
NeoOffice used a subclause of OpenOffice.org's license to change it to another license which is incompatible with the core project. so, to avoid legal issues, OpenOffice.org developers had to rewrite some subsystems, since NeoOffice code cannot be used in OpenOffice.org. Even when the licence for a fork change was compatible with the core project other kinds of legal threats were [used].
More informations in About NeoOffice
OpenOffice.org Aqua
The [OpenOffice.org Aqua] project brought native support for Mac Aqua into the OpenOffice.org core project. Since the 3.0 release Mac/Aqua is considered one of the primary platforms of the core project.
Mac OS X port Home: [Mac OS X port Home] Aqua links: [Aqua Version of OpenOffice.org] Blogs: [Developers blogs]
Q1: Where can I find OpenOffice.org or NeoOffice?
A: You can download both from respective sites.
Download OpenOffice.org from here (openoffice.org)
Download NeoOffice from here (neooffice.org)
Q2: Why does there seem to be several parallel efforts?
A: This is a very normal situation in open source. And because of historical and personal choices.
This mail from Kevin Hendricks provides some historical details.
If you want to really understand the situation, here's some additional reading for you: History of NeoOffice and OpenOffice.org, Quote from Patrick may explain some of the licensing situation, and finally, you may also want to read another FAQ
Q3: Where do I get support for OpenOffice.org Mac/Aqua ?
A: The support.openoffice.org is the main place for all support related to openoffice.org.
The OpenOffice.org for Mac OSX support page is specifically for Mac OS X users.
Q4: But it would be more efficient, if there would be only one effort...
A: Probably. A proposal to work together has been made, and NeoOffice developers refused.
OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is community project.
The NeoOffice project is a Patrick Luby and Ed Peterlin project only.
The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, because of the licensing issues. So every change must be rewritten for OpenOffice.org project, using another implementation.
A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.
Further informations are available at: http://porting.openoffice.org/mac/
