<?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"
	>
<channel>
	<title>Comments on: Refining MySQL Community Server</title>
	<atom:link href="http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/</link>
	<description>MySQL, FOSS, Sun and Community plus a dash of running and mountaineering</description>
	<pubDate>Sun, 12 Oct 2008 13:25:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Articles</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-19903</link>
		<dc:creator>Articles</dc:creator>
		<pubDate>Sat, 03 Nov 2007 17:09:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-19903</guid>
		<description>MySQL AB has announced some changes in the way it handles the Community and Enterprise releases of MySQL.</description>
		<content:encoded><![CDATA[<p>MySQL AB has announced some changes in the way it handles the Community and Enterprise releases of MySQL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Informatyka &#187; Blog Archive &#187; MySQL Enterprise Server trudniej dostępny</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18642</link>
		<dc:creator>Informatyka &#187; Blog Archive &#187; MySQL Enterprise Server trudniej dostępny</dc:creator>
		<pubDate>Tue, 21 Aug 2007 07:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18642</guid>
		<description>[...] Oczywiście kod, który pozostaje na licencji GNU GPLv2, musi być dostępny w postaci źródeł, ale firma przekonuje, że ma ten obowiązek wyłącznie wobec klientów, ponieważ tylko im dostarcza binaria. Dla pozostałych jest wersja Community Server. Firma wprowadziła jeszcze kilka innych zmian w dotychczasowej praktyce, ale kontrowersje wywołało tylko zniknięcie paczek Enterprise z publicznego serwera FTP. [...]</description>
		<content:encoded><![CDATA[<p>[...] Oczywiście kod, który pozostaje na licencji GNU GPLv2, musi być dostępny w postaci źródeł, ale firma przekonuje, że ma ten obowiązek wyłącznie wobec klientów, ponieważ tylko im dostarcza binaria. Dla pozostałych jest wersja Community Server. Firma wprowadziła jeszcze kilka innych zmian w dotychczasowej praktyce, ale kontrowersje wywołało tylko zniknięcie paczek Enterprise z publicznego serwera <a href="http://FTP" rel="nofollow">http://FTP</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: XAM &#187; Blog Archive &#187; MySQL Enterprise Server trudniej dostępny</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18641</link>
		<dc:creator>XAM &#187; Blog Archive &#187; MySQL Enterprise Server trudniej dostępny</dc:creator>
		<pubDate>Tue, 21 Aug 2007 05:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18641</guid>
		<description>[...] Oczywiście kod, który pozostaje na licencji GNU GPLv2, musi być dostępny w postaci źródeł, ale firma przekonuje, że ma ten obowiązek wyłącznie wobec klientów, ponieważ tylko im dostarcza binaria. Dla pozostałych jest wersja Community Server. Firma wprowadziła jeszcze kilka innych zmian w dotychczasowej praktyce, ale kontrowersje wywołało tylko zniknięcie paczek Enterprise z publicznego serwera FTP. [...]</description>
		<content:encoded><![CDATA[<p>[...] Oczywiście kod, który pozostaje na licencji GNU GPLv2, musi być dostępny w postaci źródeł, ale firma przekonuje, że ma ten obowiązek wyłącznie wobec klientów, ponieważ tylko im dostarcza binaria. Dla pozostałych jest wersja Community Server. Firma wprowadziła jeszcze kilka innych zmian w dotychczasowej praktyce, ale kontrowersje wywołało tylko zniknięcie paczek Enterprise z publicznego serwera <a href="http://FTP" rel="nofollow">http://FTP</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The MySQL Dramarama : Open Source Hypocrisy</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18524</link>
		<dc:creator>The MySQL Dramarama : Open Source Hypocrisy</dc:creator>
		<pubDate>Wed, 15 Aug 2007 18:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18524</guid>
		<description>[...] The Register&#8217;s Developer section has a good overview, and MySQL&#8217;s own Kaj Arn&#246; explains on his own blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Register&#8217;s Developer section has a good overview, and MySQL&#8217;s own Kaj Arn&ouml; explains on his own blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenSourceCommunity.org</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18523</link>
		<dc:creator>OpenSourceCommunity.org</dc:creator>
		<pubDate>Wed, 15 Aug 2007 13:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18523</guid>
		<description>&lt;strong&gt;MySQL Moves to Paid Tarball&lt;/strong&gt;

It turns out that the MySQL group has decided it to be a good idea to remove the source tar-balls from their community site and only make that available to paid subscribers. 

Read more from: http://www.regdeveloper.co.uk/2007/08/14/mysql_tarball_communit</description>
		<content:encoded><![CDATA[<p><strong>MySQL Moves to Paid Tarball</strong></p>
<p>It turns out that the MySQL group has decided it to be a good idea to remove the source tar-balls from their community site and only make that available to paid subscribers. </p>
<p>Read more from: <a href="http://www.regdeveloper.co.uk/2007/08/14/mysql_tarball_communit" rel="nofollow">http://www.regdeveloper.co.uk/2007/08/14/mysql_tarball_communit</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: javamorg</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18513</link>
		<dc:creator>javamorg</dc:creator>
		<pubDate>Wed, 15 Aug 2007 06:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18513</guid>
		<description>java.org » 
http://javam.org/mysql-kapaniyor/
MySQL kapanıyor !!!
MySQL kaynak kodu enterprise’a eklenerek ücretli hale getirildi.
Özetle:
* Açık kaynak topluluğu kendi haline bırakılacak
* Para ödeyen enterprise kullanıcılarına öncelik verilip onların dertleriyle ilgilenilecek...</description>
		<content:encoded><![CDATA[<p>java.org »<br />
<a href="http://javam.org/mysql-kapaniyor/" rel="nofollow">http://javam.org/mysql-kapaniyor/</a><br />
MySQL kapanıyor !!!<br />
MySQL kaynak kodu enterprise’a eklenerek ücretli hale getirildi.<br />
Özetle:<br />
* Açık kaynak topluluğu kendi haline bırakılacak<br />
* Para ödeyen enterprise kullanıcılarına öncelik verilip onların dertleriyle ilgilenilecek&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Wooley&#8217;s Blog &#187; Blog Archive &#187; MySQL hides Enterprise source code.</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18511</link>
		<dc:creator>Peter Wooley&#8217;s Blog &#187; Blog Archive &#187; MySQL hides Enterprise source code.</dc:creator>
		<pubDate>Wed, 15 Aug 2007 02:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18511</guid>
		<description>[...] It appears that MySQL is hiding its Enterprise source code. In the article, Kaj Arnö attempts to make clear that the Community Builds (aka free builds) will still be available in all their forms. But, the real key is that the Tarballs, the bundles of code that were easily accessible, are being moved from the public FTP to the enterprise server. [...]</description>
		<content:encoded><![CDATA[<p>[...] It appears that MySQL is hiding its Enterprise source code. In the article, Kaj Arnö attempts to make clear that the Community Builds (aka free builds) will still be available in all their forms. But, the real key is that the Tarballs, the bundles of code that were easily accessible, are being moved from the public FTP to the enterprise server. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySql kapanıyor !!!</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18504</link>
		<dc:creator>MySql kapanıyor !!!</dc:creator>
		<pubDate>Tue, 14 Aug 2007 23:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18504</guid>
		<description>[...] http://www.planetmysql.org/kaj/?p=123 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.planetmysql.org/kaj/?p=123" rel="nofollow">http://www.planetmysql.org/kaj/?p=123</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jcole&#8217;s weblog: Jeremy Cole&#8217;s take on life. &#187; Blog Archive &#187; On serving two markets and mistakes</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18478</link>
		<dc:creator>jcole&#8217;s weblog: Jeremy Cole&#8217;s take on life. &#187; Blog Archive &#187; On serving two markets and mistakes</dc:creator>
		<pubDate>Mon, 13 Aug 2007 18:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18478</guid>
		<description>[...] Jump forward to the most recent announcements. Once again we got an early look at the changes, and once again, we voiced our concerns. This time it basically amounted to &#8220;Is taking away the Enterprise source supposed to convince people to buy Enterprise?&#8221; Their answer was &#8220;Yep&#8221;. Our only response could be &#8220;Uh, good luck with that.&#8221; Once again, our concerns mostly centered around whether the Enterprise product made sense, and once again we said that it didn&#8217;t. We told them flat out that a single person mirroring the code would nullify all the &#8220;force people to buy&#8221; effects of their removal of the source, while nullifying none of the good will they lose by hiding it. [...]</description>
		<content:encoded><![CDATA[<p>[...] Jump forward to the most recent announcements. Once again we got an early look at the changes, and once again, we voiced our concerns. This time it basically amounted to &#8220;Is taking away the Enterprise source supposed to convince people to buy Enterprise?&#8221; Their answer was &#8220;Yep&#8221;. Our only response could be &#8220;Uh, good luck with that.&#8221; Once again, our concerns mostly centered around whether the Enterprise product made sense, and once again we said that it didn&#8217;t. We told them flat out that a single person mirroring the code would nullify all the &#8220;force people to buy&#8221; effects of their removal of the source, while nullifying none of the good will they lose by hiding it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What would make me buy MySQL Enterprise? at Xaprb</title>
		<link>http://blogs.mysql.com/kaj/2007/08/08/refining-mysql-community-server/#comment-18461</link>
		<dc:creator>What would make me buy MySQL Enterprise? at Xaprb</dc:creator>
		<pubDate>Sun, 12 Aug 2007 20:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmysql.org/kaj/?p=123#comment-18461</guid>
		<description>[...] MySQL AB&#8217;s recent changes to the Community/Enterprise split have made people go as far as calling the split a failure. I don&#8217;t think it&#8217;s working well either, but it could be fixed. Here&#8217;s what I think would make Enterprise a compelling offer. [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL AB&#8217;s recent changes to the Community/Enterprise split have made people go as far as calling the split a failure. I don&#8217;t think it&#8217;s working well either, but it could be fixed. Here&#8217;s what I think would make Enterprise a compelling offer. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
