Comments on: Lyon Summary http://www.robweir.com/blog/2006/09/lyon-summary.html?utm_source=rss&utm_medium=rss&utm_campaign=lyon-summary Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable Tue, 07 Feb 2012 11:20:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: hAl http://www.robweir.com/blog/2006/09/lyon-summary.html#comment-91 hAl Wed, 20 Sep 2006 09:28:00 +0000 http://www.robweir.com/blog/2006/09/lyon-summary.html#comment-91 I think KOffice seems a brighter prospect than OpenOffice. <br/>OpenOffice.org carries a lot of legacy bagage and is still very much under the control of Sun developers. KOffice is less mature but can adapt much easier to take full advantage of the Opendocument format possibilities and find new ones. <br/>I think OOo is not a good thing for the future development of the standard format as it has so much relation to the formaat that it would be very hard to get new functionality in that other OSS projects could use but that OOo has no intention of supporting.<br/><br/>My money would be on true OSS community products for the future of ODF and not on a so much Sun related organisationas OOo. I think KOffice seems a brighter prospect than OpenOffice.
OpenOffice.org carries a lot of legacy bagage and is still very much under the control of Sun developers. KOffice is less mature but can adapt much easier to take full advantage of the Opendocument format possibilities and find new ones.
I think OOo is not a good thing for the future development of the standard format as it has so much relation to the formaat that it would be very hard to get new functionality in that other OSS projects could use but that OOo has no intention of supporting.

My money would be on true OSS community products for the future of ODF and not on a so much Sun related organisationas OOo.

]]> By: C. T. Rambler http://www.robweir.com/blog/2006/09/lyon-summary.html#comment-90 C. T. Rambler Tue, 19 Sep 2006 15:31:00 +0000 http://www.robweir.com/blog/2006/09/lyon-summary.html#comment-90 An open source OpenDocument Developer Kit (ODDK) is a necessary tool to encourage adoptin of OpenDocument. More than once I am put off good technology by the fact that I have to develope everything from scratch and use my own custom thing instead.<br/><br/>Having a development kit is going be a great weapon against the _other_ effort. It lowers the barrier to entry for developers. I hate to see the other party wins on development kit issue.<br/><br/>Also, GPL will be too "viral" and will severely limited ODDK use. Something like LGPL where you are forced to contribute back your modification will be ideal in an idealistic world. ODDK should probably be licensed under Apache-like license. An open source OpenDocument Developer Kit (ODDK) is a necessary tool to encourage adoptin of OpenDocument. More than once I am put off good technology by the fact that I have to develope everything from scratch and use my own custom thing instead.

Having a development kit is going be a great weapon against the _other_ effort. It lowers the barrier to entry for developers. I hate to see the other party wins on development kit issue.

Also, GPL will be too “viral” and will severely limited ODDK use. Something like LGPL where you are forced to contribute back your modification will be ideal in an idealistic world. ODDK should probably be licensed under Apache-like license.

]]>