I think now would be an excellent time for an EU directive that all government documents must at all times be stored in an openly standardised format. So no OOXML Transitional.
> Open Source is a global effort, but current political situation makes collaboration hard and trust difficult to earn. Especially when development is not transparent and open.
I find this an odd statement. I would understand an explanation that forking was chosen on ideological grounds, but, how is development "not transparent and open" in an open source project? Sounds a bit contradictory. Plus doesn't the fact that a fully functioning fork was performed effortlessly show that the project was indeed truly transparent and open?
Open source doesn't necessarily mean the development is open and transparent. For example, sqlite is open source, but the development process isn't very open. Development is done entirely by the sqlite team.
> how is development "not transparent and open" in an open source project?
Please have a look at how Android is developed, and how each new version is released. It's far from the only example of "open source but closed development process".
Never mind "shared source" like QNX where people can pass through hoops to view source, but code is not open in the libre sense.
> They are using Microsoft formats instead of the open-source one.
They will need to focus on Microsoft's formats for the foreseeable future because of the sheer amount of archaic, but still vitally important, government processes which depend on them.
Once Euro Office gains a significant foothold in those government processes, then they'll have the market power to influence. And, hopefully, force change in Microsoft's behaviour by forcing them to compete against a cheaper and just as capable open product suite.
They need to focus on archaic government processes which rely on document formats that require proprietary software to view properly, while good open source software for the same task exists. And where lacking, focus on improving open source support for a particular task.
A good start would be to cut use of this OOXML Transitional format entirely. Default to LibreOffice's default formats, and (perhaps) support OOXML Strict where it helps transition.
That way any government employee saving their work in OOXML Transitional or other proprietary format, would automatically stick out as a dumbass who failed to do their job. Pass documents that are published through some validators / allowed-format checkers, and the public only gets stuff that's viewable with software of their choosing.
None of this is hard. It's mostly about changing defaults & a bit of employee training.
Oh that and the following paragraphs are salty, after all of the mess of Euro-Office violating their copyright (OO's arguments about which may or may not hold up in court).
Personally, I'll probably just stick with LibreOffice until things calm down a bit.