<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Open Letter to Simon Phipps, Chief Open Source Officer at Sun Microsystems</title>
	<atom:link href="http://robertogaloppini.net/2006/12/27/open-letter-to-simon-phipps-chief-open-source-officer-at-sun-microsystems/feed/" rel="self" type="application/rss+xml" />
	<link>http://robertogaloppini.net/2006/12/27/open-letter-to-simon-phipps-chief-open-source-officer-at-sun-microsystems/</link>
	<description>“equally critical of proprietary and open source myths, advocating software choice beyond marketing and romanticism”</description>
	<pubDate>Thu, 17 May 2012 04:18:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Simon Phipps</title>
		<link>http://robertogaloppini.net/2006/12/27/open-letter-to-simon-phipps-chief-open-source-officer-at-sun-microsystems/comment-page-1/#comment-1005</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Sat, 03 Feb 2007 16:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/?p=41#comment-1005</guid>
		<description>Hi Roberto.

I've looked into this and the problem was that, by using the GPL rather than the LGPL for your contribution, it was necessary for Sun's legal team to conduct an extensive discussion about the implications of distributing it with OpenOffice.org (which as you know is licensed under LGPL), and that discussion was disrupted by staffing changes in mid-stream. Some delay in public comment was inevitable because of the fact you'd used a license the OpenOffice.org community has not chosen and because seeking legal advice in the US is necessarily a confidential matter under US law. I apologise for the extra delay that was unavoidably caused by the staffing changes. 

I have now received legal advice that gives me confidence that inclusion of this great facility will be OK from a licensing perspective, and it will proceed forthwith. I'd like to thank you and your team for both your important contribution to OpenOffice.org and for your patience waiting for the process to complete.

S.</description>
		<content:encoded><![CDATA[<p>Hi Roberto.</p>
<p>I&#8217;ve looked into this and the problem was that, by using the GPL rather than the LGPL for your contribution, it was necessary for Sun&#8217;s legal team to conduct an extensive discussion about the implications of distributing it with OpenOffice.org (which as you know is licensed under LGPL), and that discussion was disrupted by staffing changes in mid-stream. Some delay in public comment was inevitable because of the fact you&#8217;d used a license the OpenOffice.org community has not chosen and because seeking legal advice in the US is necessarily a confidential matter under US law. I apologise for the extra delay that was unavoidably caused by the staffing changes. </p>
<p>I have now received legal advice that gives me confidence that inclusion of this great facility will be OK from a licensing perspective, and it will proceed forthwith. I&#8217;d like to thank you and your team for both your important contribution to OpenOffice.org and for your patience waiting for the process to complete.</p>
<p>S.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mirco</title>
		<link>http://robertogaloppini.net/2006/12/27/open-letter-to-simon-phipps-chief-open-source-officer-at-sun-microsystems/comment-page-1/#comment-67</link>
		<dc:creator>Mirco</dc:creator>
		<pubDate>Mon, 01 Jan 2007 23:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/?p=41#comment-67</guid>
		<description>I've worked on Thesaurus please let it be uasble. Thanks a lot.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve worked on Thesaurus please let it be uasble. Thanks a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

