Re: Apache replacement

2015-10-10 Thread toki
On 10/10/15 13:48, donaldupre wrote: >The decision making will stay with Apache. There is nothing preventing an organization from collecting the source code Apache releases, modifying it, and commercially distributing the resulting program. As such, Apache's decision making becomes totally irrele

Re: Apache replacement

2015-10-10 Thread donaldupre .
Please allow me to clarify. According to your suggestion, the contributors will be managed by Apache. The decision making will stay with Apache. But apache proved to fail in those aspects... About creating a derivative product, after reading so many comments and opinions online suggesting a merge o

Re: Apache replacement

2015-10-10 Thread Andrea Pescetti
donaldupre . wrote: What does it take to buy back OpenOffice from Apache? I'm sure there are commercial entities that will be happy to develop it. Those entities can ask their employees to contribute to OpenOffice, and help shape the project with their contributions. This addresses all items

Re: Apache replacement

2015-10-10 Thread donaldupre .
There is the brand name "OpenOffice" to be bought. The exact problems with Apache: 1. Lack of releases, should be 3-4 per year as minimum. 2. The tired and boring look and feel of the homepage, blog, facebook, twitter. 3. Lack of innovation, the sidebar is not an example for innovation. 4. The lost

Re: Apache replacement

2015-10-10 Thread Damjan Jovanovic
Hi OpenOffice is under a very liberal license: anyone can fork it and continue developing it independently (eg. NeoOffice), there's nothing to be bought. What are your exact problems with the job Apache is doing? Regards Damjan On Sat, Oct 10, 2015 at 12:36 PM, donaldupre . wrote: > Hi > Wha

Apache replacement

2015-10-10 Thread donaldupre .
Hi What does it take to buy back OpenOffice from Apache? I'm sure there are commercial entities that will be happy to develop it. Apache isn't doing a great job... Best regards, Don PS I don't want a merge with LibreOffice!