<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: what fsf got wrong</title>
	<atom:link href="http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/</link>
	<description>Ramblings on software, law, and the spaces in between.</description>
	<lastBuildDate>Sun, 12 Feb 2012 11:08:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Entenda quais são e como funcionam licenças de software livre</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-26904</link>
		<dc:creator>Entenda quais são e como funcionam licenças de software livre</dc:creator>
		<pubDate>Wed, 09 Apr 2008 13:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-26904</guid>
		<description></description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://tieguy.org/blog/wp-content/plugins/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] caras do Kernel estão (e não estão) falando sobre a GPLv3 O que os caras do Kernel entenderam erradoo que a FSF entendeu erradoTags: FSFGNUGPLLinuxOpensourcecréditos: MeioBit      0 Comments          &copy; linuxnarede &#8211; Todos [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moving to Freedom</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-4462</link>
		<dc:creator>Moving to Freedom</dc:creator>
		<pubDate>Sun, 03 Dec 2006 20:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-4462</guid>
		<description>&lt;strong&gt;GNU/Solaris and GPLv3...&lt;/strong&gt;


I found an interesting article at The Register yesterday, &#8220;Is &#8216;GNU/Solaris&#8217; emerging from the Microsoft-Novell deal?&#8221;  It would be awesome if Sun released the Solaris kernel under the GPLv3, because I think that would be a chan...</description>
		<content:encoded><![CDATA[<p><strong>GNU/Solaris and GPLv3&#8230;</strong></p>
<p>I found an interesting article at The Register yesterday, &#8220;Is &#8216;GNU/Solaris&#8217; emerging from the Microsoft-Novell deal?&#8221;  It would be awesome if Sun released the Solaris kernel under the GPLv3, because I think that would be a chan&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pauses Caf&#233; &#187; Blog Archive &#187; Licensing by intent</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2803</link>
		<dc:creator>Pauses Caf&#233; &#187; Blog Archive &#187; Licensing by intent</dc:creator>
		<pubDate>Thu, 28 Sep 2006 07:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2803</guid>
		<description>[...] It seems that there are many things both camps got wrong (you can read more on Luis Villa&#8217;s blog, here, here and here). [...]</description>
		<content:encoded><![CDATA[<p>[...] It seems that there are many things both camps got wrong (you can read more on Luis Villa&#8217;s blog, here, here and here). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Radcliffe</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2777</link>
		<dc:creator>Mark Radcliffe</dc:creator>
		<pubDate>Tue, 26 Sep 2006 01:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2777</guid>
		<description>I am puzzled by the view that patents are immoral. Copyrights and patents are simply laws that are designed to encourage certain economic behaviour (although the French/German approach to copyrights are more based on personal right). If you couch the discussion as one about morality, you will lose a large portion of your audience, because these decisions are clearly so economic in character. That said, complaints about the patent system have been common throughout US history and the system has been modified to deal with the problems (see the change to eliminate &quot;submarine patents&quot;). Similarly, I think that the kernal guys have missed a major chance to try to persuade Eben and Richard. In fairness, I am running one of the committees so I have made my decision to participate, but I think that they are open to persuasion on many issues. Frankly, DRM does not appear to be an issue in which they are willing to compromise, but you will never know if you are outside of the process.</description>
		<content:encoded><![CDATA[<p>I am puzzled by the view that patents are immoral. Copyrights and patents are simply laws that are designed to encourage certain economic behaviour (although the French/German approach to copyrights are more based on personal right). If you couch the discussion as one about morality, you will lose a large portion of your audience, because these decisions are clearly so economic in character. That said, complaints about the patent system have been common throughout US history and the system has been modified to deal with the problems (see the change to eliminate &#8220;submarine patents&#8221;). Similarly, I think that the kernal guys have missed a major chance to try to persuade Eben and Richard. In fairness, I am running one of the committees so I have made my decision to participate, but I think that they are open to persuasion on many issues. Frankly, DRM does not appear to be an issue in which they are willing to compromise, but you will never know if you are outside of the process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Myers</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2764</link>
		<dc:creator>Rob Myers</dc:creator>
		<pubDate>Mon, 25 Sep 2006 14:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2764</guid>
		<description>The problem with the Kernel Developers position on DRM (and this can be seen in Debian-Legal&#039;s attitude to the Creative Commons anti-DRM language as well) is that they view DRM as a technology, not as an extension of copyright law. DRM has power only through law: it would not be illegal to remove or reverse-engineer DRM otherwise. But too many hackers idealise DRM systems as code and DRM-laden files as data. They ignore the legal dimension, and this leads to confused reasoning. 

To cite the FSD or DFSG freedom to modify code in support of this new excess of copyright law is an example of that confused reasoning. You cannot modify BSD-licensed code to remove the copyright header for example, and you cannot add the string &quot;all rights reserved&quot; to the top of a GPL-2-licensed file, yet despite restricting your freedom in this way neither license breaks the FSD or the DFSG. If the BSD license said &quot;you may not write a script to remove this header&quot;, would that break the DFSG?

DRM is an extension of copyright law that can prevent computer users from exercising their freedoms. Those who support DRM seem to view code, rather than human beings, as the subject of Free Software&#039;s freedoms. This is an impoverished understanding of freedom. But if you must write DRM code, the GPL-3 will not prevent you. It just removes the legal privileges that such code would otherwise have to remove users&#039;  freedom.</description>
		<content:encoded><![CDATA[<p>The problem with the Kernel Developers position on DRM (and this can be seen in Debian-Legal&#8217;s attitude to the Creative Commons anti-DRM language as well) is that they view DRM as a technology, not as an extension of copyright law. DRM has power only through law: it would not be illegal to remove or reverse-engineer DRM otherwise. But too many hackers idealise DRM systems as code and DRM-laden files as data. They ignore the legal dimension, and this leads to confused reasoning. </p>
<p>To cite the FSD or DFSG freedom to modify code in support of this new excess of copyright law is an example of that confused reasoning. You cannot modify BSD-licensed code to remove the copyright header for example, and you cannot add the string &#8220;all rights reserved&#8221; to the top of a GPL-2-licensed file, yet despite restricting your freedom in this way neither license breaks the FSD or the DFSG. If the BSD license said &#8220;you may not write a script to remove this header&#8221;, would that break the DFSG?</p>
<p>DRM is an extension of copyright law that can prevent computer users from exercising their freedoms. Those who support DRM seem to view code, rather than human beings, as the subject of Free Software&#8217;s freedoms. This is an impoverished understanding of freedom. But if you must write DRM code, the GPL-3 will not prevent you. It just removes the legal privileges that such code would otherwise have to remove users&#8217;  freedom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2727</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Sun, 24 Sep 2006 12:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2727</guid>
		<description>And I might add that the kernel guys could clearly have raised these objections within the system first. They&#039;d come off less as whiny children and more as reasonable adults if they&#039;d done that. Even if you think Eben and RMS are total jackasses, there is something to be said for holding the moral high ground- which frankly no party does at this point.</description>
		<content:encoded><![CDATA[<p>And I might add that the kernel guys could clearly have raised these objections within the system first. They&#8217;d come off less as whiny children and more as reasonable adults if they&#8217;d done that. Even if you think Eben and RMS are total jackasses, there is something to be said for holding the moral high ground- which frankly no party does at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2726</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Sun, 24 Sep 2006 12:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2726</guid>
		<description>I&#039;ve taken the liberty of editing that last post to point out that it came from an OSDL employee. I might note that it would also have had more credibility if it spelled &#039;Eben&#039; correctly. :)

Sch: Linus has been just as aggressive and belittling, if not more so- go see some of his posts on groklaw, for example. He&#039;s been &lt;i&gt;incredibly&lt;/i&gt; rude to PJ. 

More relevantly than any personal attacks one way or the other, I object to your characterization of the other commitees as yes men- you clearly clearly missed the point of my first essay. Most of us feel that (1) this is RMS&#039;s process, and we&#039;re helping fix the license as best we can within that framework, whether or not we use it later and more importantly (2) most of us feel that patents and DRM are substantial and important threats and abuses which must be dealt with. So if agreeing about freedom and wanting to make the best possible license within the constraints offered makes us yes men... well, then, I guess we&#039;re yes men. But I think that&#039;s a broken and bogus characterization, and I hope most people see through that if that is the tack OSDL and the embedded vendors are going to take.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve taken the liberty of editing that last post to point out that it came from an OSDL employee. I might note that it would also have had more credibility if it spelled &#8216;Eben&#8217; correctly. :)</p>
<p>Sch: Linus has been just as aggressive and belittling, if not more so- go see some of his posts on groklaw, for example. He&#8217;s been <i>incredibly</i> rude to PJ. </p>
<p>More relevantly than any personal attacks one way or the other, I object to your characterization of the other commitees as yes men- you clearly clearly missed the point of my first essay. Most of us feel that (1) this is RMS&#8217;s process, and we&#8217;re helping fix the license as best we can within that framework, whether or not we use it later and more importantly (2) most of us feel that patents and DRM are substantial and important threats and abuses which must be dealt with. So if agreeing about freedom and wanting to make the best possible license within the constraints offered makes us yes men&#8230; well, then, I guess we&#8217;re yes men. But I think that&#8217;s a broken and bogus characterization, and I hope most people see through that if that is the tack OSDL and the embedded vendors are going to take.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sch [OSDL]</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2716</link>
		<dc:creator>Sch [OSDL]</dc:creator>
		<pubDate>Sun, 24 Sep 2006 05:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2716</guid>
		<description>The kernel developers did not directly particpate in the GPLv3 review process because it was clear from the beginning that any direct comments would not cause change. After the first draft, Linus and others made it clear what they thought of the &quot;DRM&quot; clauses. But Eban/Richard did not change their position one bit; they just clarified it and made it stronger. Why would any group of people who disagree want to particpate in a process where their input is ignored, they are belittled (see Eban&#039;s comments about Linus), and it was never a consensus process at all? The members of Committee B, which is the only group that seems to not contain all yes people, is well aware of the kernel communities opinions. In fact, at the last meeting Committee B was surprised to find out that
the concerns and opinions of the kernel community matched those of the Commitee.</description>
		<content:encoded><![CDATA[<p>The kernel developers did not directly particpate in the GPLv3 review process because it was clear from the beginning that any direct comments would not cause change. After the first draft, Linus and others made it clear what they thought of the &#8220;DRM&#8221; clauses. But Eban/Richard did not change their position one bit; they just clarified it and made it stronger. Why would any group of people who disagree want to particpate in a process where their input is ignored, they are belittled (see Eban&#8217;s comments about Linus), and it was never a consensus process at all? The members of Committee B, which is the only group that seems to not contain all yes people, is well aware of the kernel communities opinions. In fact, at the last meeting Committee B was surprised to find out that<br />
the concerns and opinions of the kernel community matched those of the Commitee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2704</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Sat, 23 Sep 2006 21:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2704</guid>
		<description>Their deep pockets make them the most interesting target for patent trolls, though.</description>
		<content:encoded><![CDATA[<p>Their deep pockets make them the most interesting target for patent trolls, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/comment-page-1/#comment-2702</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Sat, 23 Sep 2006 18:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://tieguy.org/blog/2006/09/22/what-fsf-got-wrong/#comment-2702</guid>
		<description>Mind you, the kernel hackers &lt;em&gt;can&lt;/em&gt; more or less ignore patent threats. For one thing, they have a lot of contributors from industry, so they would have powerful backing in any case. For another, the rights to their codebase is spread over thousands of contributors, so any patent attack on the kernel would punch water. They simply donâ€™t have a lot to worry about.

Small projects run by just a handful of developers without corporate backing (ie. the majority of free software) are under much bigger threat from patent claims.</description>
		<content:encoded><![CDATA[<p>Mind you, the kernel hackers <em>can</em> more or less ignore patent threats. For one thing, they have a lot of contributors from industry, so they would have powerful backing in any case. For another, the rights to their codebase is spread over thousands of contributors, so any patent attack on the kernel would punch water. They simply donâ€™t have a lot to worry about.</p>
<p>Small projects run by just a handful of developers without corporate backing (ie. the majority of free software) are under much bigger threat from patent claims.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

