What's next for Apache OpenOffice

Jimjag has shown some willingness to do that, imperfect but promising. Everyone needs to let go of the past to take advantage of the opportunity of _today_.

As I noted elsewhere, don't become what you hate...

And the success of Open Source projects rarely depends on differences between licenses, who screams loudest, or what FUD is somewhere on the internet.

The only thing that will matter for the future of AOO is whether or not AOO development will get back on track.

Think of the translation volunteer example I described.
Who is responsible that they will still be available when the translations will be needed for making the 4.2.0 release?

I pointed out an area where your skills could be very helpful for getting AOO development back on track.
I don't personally care about AOO, and whether or not the future of AOO is important enough for you to participate in the actual development of AOO is your decision.

You mean like your completely baseless claim that nginx was an Apache httpd fork?

The post confronting you with evidence to the contrary is one of those you conveniently ignore. Well at least it shows clearly what you are really after.

The sheer level of 'leg in throat' you exhibited with the nginx claim by itself is staggering in how much of a bald-faced and brazen lie it is, trivially debunked in five minutes of Googling.

Especially with the near-zero overlap in configuration or outward-facing components the two projects display would refute it to begin with, and nginx at this point actually being the better of the two for maintaining backwards compatibility in their configuration files w/ the 2.2 -> 2.4 config-file changes that purged major configuration-file syntax components.

So that claim came across purely as trying to claim "Yet another project profiting unjustly by stealing something from an Apache project!" like a fanatic. Note: Being a fanatic is not a good thing. Being fanatical can be, but losing those last two letters is a pitfall.

Apache unfortunately with their long-standing stance on licensing acts more and more like a fanatic with each passing year, and in my line of work as a 'mercenary' Linux Admin (meaning I handle and have on-going access to hundreds of unique environments of various sizes regardless of what components they have; as long as the sites stay functional and the developers can push code changes the clients are happy) I see developers moving from Solr, httpd, Cassandra, and ActiveMQ to Sphinx, nginx, ReThinkDB, and RabbitMQ month after month.

Many Apache projects, while they did build the backbone of the internet, have had a newer generation of services and tools developed that surpass what they offer, usually in features or ease of maintenance/deployment. About the only remaining 'infrastructure level' projects I can think of that Apache offers the only pony in the horse-show is Hadoop, and Tomcat, both of which are only of common use in my experienc ein fairly large environments where you usually have development teams not developers.

But please, continue railing against the dying of the light of the permission Apache license and evil forks that cared more about the end-users than your stigmata. The rest of us will continue getting up every day and getting work done with tools that work, instead of ones that are mostly name-recognition and inertia-based. :)