http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/ A weblog by Charles-H. Schulz. Mon, 26 Jul 2010 17:53:22 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/comment-page-1/#comment-1164 Xavier Wed, 16 Jul 2008 22:21:06 +0000 http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/#comment-1164 I'm shocked by Michael Meeks' comments as well. I’m shocked by Michael Meeks’ comments as well.

]]> http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/comment-page-1/#comment-115 Michael Meeks Tue, 09 Oct 2007 16:55:51 +0000 http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/#comment-115 Rebuttal to this sort of nonsense here: http://www.gnome.org/~michael/activity.html#2007-10-09 Rebuttal to this sort of nonsense here:
http://www.gnome.org/~michael/activity.html#2007-10-09

]]> http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/comment-page-1/#comment-114 Boycott Novell » Why Would Novell Want to Fork OOO? Tue, 09 Oct 2007 16:52:11 +0000 http://standardsandfreedom.net/index.php/2007/10/09/and-so-novell-forked/#comment-114 [...] 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 [...] [...] 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 [...]

]]>