And so Novell forked…
9 10 2007This article is my first one on Groklaw. I really wanted to express my feelings about the whole story concerning Novell’s fork. And by the way, are they really forking? There are still several engineers from Novell out there on our mailing lists, and I wish we can still work with them. Yet Michael Meeks’s move essentially turned Novell contributors into read-only members of OpenOffice.org.
Anyway, here’s the summarized version of the article; ever since Novell signed their agreement with Microsoft, they became weird and started to do all kinds of oddities. It’s a pity, but it seems we can do nothing about it. So at some point, they started to become divisive in their politics and emphasize the JCA and Sun as being a major issue of the project. I am however shocked by Michael Meeks’ hypocrisy on all this: he’s still working for the sole company pretending to be an Open Source player but gleefully developing implementations of Microsoft technologies before the rest of the industry even starts to think about it. Should the term « proactive competitors » apply here?
What should be noted here is the essential difference between Novell’s overall strategy and the Samba approach of the problem. Samba is solving a crucial compatibility problem by developing a technology communicating with the existing Microsoft world. Novell, through Mono, Silverlight and the OOXML plugin implements Microsoft technologies even before they become dominant. This double difference (direct implementation of Microsoft technologies and early support of them on the market) bears a name: gleefully partnering with Microsoft.
I pretty much see what Novell’s initial reasoning was behind all this: let the crazies go to the FSF (that much would tell a lot about their whole perception of Free Software) while we are the reasonable, responsible guys out there who truly understood Linux in the enterprise. That could fly but not if all what you’re doing is disrupting the community and several FOSS projects while partnering with Microsoft on intellectual property and implementing technologies that are riddled with patents. That’s Novell number one problem. And as I wrote on Groklaw, Novell remains silent as a grave about their engineers’ actions. Interesting but odd.
[…] Charles H. Schulz has written a piece that was published on Groklaw which attempts to shed some light on the background of the dispute, and offers some conjecture on what Meeks’ motivation may be: Bear with me now: The OpenOffice.org project is developing import filters for OpenXML, but not export filters. Why? Because, I believe, it does not want to make a service to Microsoft by being the second major office suite to produce OpenXML documents on the fly. Novell sees this issue from a different point of view, but let’s not get carried away. Working with Microsoft on interoperability, as Novell claims, includes working on OpenXML filters and plugins. While Novell contributes quite normally to OpenOffice.org’s import filters, it is also developing an OpenXML export filter that won’t be available in OpenOffice.org– that is, if you choose to use OpenOffice.org and not “Open Office, Novell Edition”. And since these export filters are supposedly developed in collaboration with Microsoft, this technology would logically include Microsoft’s sacred intellectual property that Sun and many others don’t want to see covered by the JCA. This could, perhaps, explain Michael’s odd questions on this list of OpenOffice.org […]
Rebuttal to this sort of nonsense here:
http://www.gnome.org/~michael/activity.html#2007-10-09
I’m shocked by Michael Meeks’ comments as well.