<?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: Forkability</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2005/12/29/forkability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2005/12/29/forkability/</link>
	<description>what was</description>
	<pubDate>Mon, 15 Mar 2010 03:05:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: links for 2006-01-02 at protocol7</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/12/29/forkability/#comment-2262</link>
		<dc:creator>links for 2006-01-02 at protocol7</dc:creator>
		<pubDate>Mon, 02 Jan 2006 12:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=78#comment-2262</guid>
		<description>[...] Forkability A discussion on defining a standard or software open if someone can fork it (tags: standards) [...]</description>
		<content:encoded><![CDATA[<p>[...] Forkability A discussion on defining a standard or software open if someone can fork it (tags: standards) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Sickles</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/12/29/forkability/#comment-2250</link>
		<dc:creator>Dan Sickles</dc:creator>
		<pubDate>Fri, 30 Dec 2005 17:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=78#comment-2250</guid>
		<description>As fto forkability, I like Richard Stallman's response to Sun's open source claims: 

http://linux.sys-con.com/read/47210.htm?CFID=547041&#38;CFTOKEN=C2CE5A81-DED5-E061-5625137C0F1A35A6</description>
		<content:encoded><![CDATA[<p>As fto forkability, I like Richard Stallman&#8217;s response to Sun&#8217;s open source claims: </p>
<p><a href="http://linux.sys-con.com/read/47210.htm?CFID=547041&amp;CFTOKEN=C2CE5A81-DED5-E061-5625137C0F1A35A6" rel="nofollow">http://linux.sys-con.com/read/47210.htm?CFID=547041&amp;CFTOKEN=C2CE5A81-DED5-E061-5625137C0F1A35A6</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/12/29/forkability/#comment-2245</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Fri, 30 Dec 2005 06:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=78#comment-2245</guid>
		<description>I agree that forkability is a good quick test for the openness of software; if your code cannot be forked, you are not an Ephraimite.  But I think standards are different: the quick test for an open standard is "Can anyone implement it against the will of the maintainer?"  If so, it's open.  Just being able to change the text of the standard is not enough.</description>
		<content:encoded><![CDATA[<p>I agree that forkability is a good quick test for the openness of software; if your code cannot be forked, you are not an Ephraimite.  But I think standards are different: the quick test for an open standard is &#8220;Can anyone implement it against the will of the maintainer?&#8221;  If so, it&#8217;s open.  Just being able to change the text of the standard is not enough.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
