That would make maintenance easier, and we could maybe along the line outsource the UNO in its own project, trying to attract more developers for their applications.
We talked about separating UNO from OpenOffice code wise. Maybe: reduce the need for popup windows.Įnhance the modularization. Retain the concept of the UI as much as possible and extend it. But the discussions are quite difficult for me, so I process this topic only slowly. I would like to go into improvements here. However a lot of modern concepts are applicable on old style preparing for the new compilers. That means our Code can not adapt the latest concepts. General: We support pretty old compilers. Maybe a port for raspberry py is possible. MacOSx port for Silicon needs to be start soon.
Windows 64 bit Version has to be continued in line with SDK updates. Lets see if this topic can get some angle.
I see that long term, we need to first align on a vision.Īnother topic is picture manipulation. Base in its concept is not anything near state of the art. Apache POI is currently more likely to happen. For the later it is most likely we implement Apache POI, I see another way to rip the LO OOXML filter and put it into an extension as an alternative approach. I see 2 priority bugs: The issues with the profile and the power supply cases where OpenOffice starts eating files are quite important.Ģ Major features we need to focus on: ODF 1.3 support and increase OOXML support. We have some regression Issues and then an extensive testing is needed to ensure we do not miss any other regressions.
Priority depends on if a topic get dev power or not.įirst target is bringing the 4.2.0 to release. I see us all as equal, so no promises that anything will happen. This is my List, unaligned with what other developers or community members, even you the reader might think. I would like to use the opportunity to provide my vision on where I want to move. I know that the LibreOffice team wants to work with Apache to make OpenOffice more modern (using libre code i think)īut what's the future for OpenOffice? Is Apache planning anything?
There hasn't been a major update since 2014 i think While OpenOffice is still very good it feels old and is old compared the LibreOffice Ngk wrote:So what's the future like for OpenOffice But since I have no intend on starting a war with LO, I would rather fix the fork, I leave the topic as is, and rather research the commiters intend.Īs long as a Code change is available under APL2 we can integrate that into our core code.
I have my doubts this is a water proof license governance that can stand in front of a court.
IMHO all code is APL2, but I understood that the intend is that the commit follows the first mentioned license in a file. Since LibreOffice seems to have many more active programmers, and since Apache’s programmers are inevitably contributing to LibreOffice, I don’t see how Apache OpenOffice can keep up.Īs I say, I have not verified this and if someone can point to a similar brief explanation I will be pleased to read it. (In fact, both versions got it from the same source: IBM’s Symphony.) Indeed, Apache has had to replace OpenOffice code that was copyleft-only, but when it introduced a big new sidebar, LibreOffice was able to incorporate it immediately. It means that LibreOffice can take code from Apache OpenOffice (that’s the point of permissive licences) but Apache OpenOffice can’t take code from LibreOffice (that’s the point of “copyleft” license)s. The difference in licences puts Apache OpenOffice at a disadvantage. Not everybody wants to write free code for somebody else’s benefit. However, OpenOffice has changed from a “copyleft” (GPL) licence to a permissive Apache license, which means anybody can use the code for commercial purposes. “Copyleft” licences try to ensure that the code contributed by open source programmers can only be re-used on the same terms. LibreOffice is being developed under two “copyleft” licences: GNU’s LGPLv3 and the Mozilla Public License (MPLv2).