<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BlogNerds&#187; gnu</title>
	<atom:link href="http://www.blognerds.com/category/gnu/feed" rel="self" type="application/rss+xml" />
	<link>http://www.blognerds.com</link>
	<description>Tech News, Gadgets, and Trends</description>
	<lastBuildDate>Tue, 25 Aug 2009 13:47:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>GPLv2 and GPLv3 Coexisting In the Same Project?</title>
		<link>http://www.blognerds.com/gnu/gplv2-and-gplv3-coexisting-in-the-same-project.html</link>
		<comments>http://www.blognerds.com/gnu/gplv2-and-gplv3-coexisting-in-the-same-project.html#comments</comments>
		<pubDate>Sat, 16 Jun 2007 18:43:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[gnu]]></category>

		<guid isPermaLink="false">http://blognerds.com/2007/06/16/gplv2-and-gplv3-coexisting-in-the-same-project/</guid>
		<description><![CDATA[cyclop writes &#8220;I am coding a data analysis application in my laboratory that I would like to release as free (as in freedom) software. Moreover I am going to begin a small OSS game that will be based, in part, on GPLv2 libraries. Problem is: in both cases, I&#8217;d like to be able to exchange [...]]]></description>
		<wfw:commentRss>http://www.blognerds.com/gnu/gplv2-and-gplv3-coexisting-in-the-same-project.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GPLv2 Vs. GPLv3</title>
		<link>http://www.blognerds.com/gnu/gplv2-vs-gplv3.html</link>
		<comments>http://www.blognerds.com/gnu/gplv2-vs-gplv3.html#comments</comments>
		<pubDate>Mon, 04 Jun 2007 07:35:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[gnu]]></category>

		<guid isPermaLink="false">http://blognerds.com/2007/06/04/gplv2-vs-gplv3/</guid>
		<description><![CDATA[chessweb writes &#8220;Here is a rather enlightening article by Richard Stallman on the reasons for moving to GPLv3 that puts the previous TiVo post into the right context.&#8221; From the article: &#8220;One major danger that GPLv3 will block is tivoization. Tivoization means computers (called &#8216;appliances&#8217;) contain GPL-covered software that you can&#8217;t change, because the appliance [...]]]></description>
		<wfw:commentRss>http://www.blognerds.com/gnu/gplv2-vs-gplv3.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FSF Releases Fourth and Final Draft of GPLv3</title>
		<link>http://www.blognerds.com/gnu/fsf-releases-fourth-and-final-draft-of-gplv3.html</link>
		<comments>http://www.blognerds.com/gnu/fsf-releases-fourth-and-final-draft-of-gplv3.html#comments</comments>
		<pubDate>Fri, 01 Jun 2007 10:19:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[gnu]]></category>

		<guid isPermaLink="false">http://blognerds.com/2007/06/01/fsf-releases-fourth-and-final-draft-of-gplv3/</guid>
		<description><![CDATA[An anonymous reader writes &#8220;The most notable changes found in this latest draft include making GPLv3 compatible with version 2.0 of the Apache license, ensuring that distributors who make discriminatory patent deals after March 28 may not convey software under GPLv3, adding terms to clarify how users can contract for private modification of free software [...]]]></description>
		<wfw:commentRss>http://www.blognerds.com/gnu/fsf-releases-fourth-and-final-draft-of-gplv3.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MS-Funded Study Atacks GPL3 Draft Process</title>
		<link>http://www.blognerds.com/gnu/ms-funded-study-atacks-gpl3-draft-process.html</link>
		<comments>http://www.blognerds.com/gnu/ms-funded-study-atacks-gpl3-draft-process.html#comments</comments>
		<pubDate>Tue, 22 May 2007 18:53:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[gnu]]></category>

		<guid isPermaLink="false">http://blognerds.com/2007/05/22/ms-funded-study-atacks-gpl3-draft-process/</guid>
		<description><![CDATA[QCMBR writes &#8220;A new Microsoft-funded study by a Harvard Business School professor concludes that developers don&#8217;t want extensive patent licensing requirements in the GPL3. There are significant problems with the study, however, especially given the very small sample size. &#8216;Although 332 emails were sent to various developers, only 34 agreed to participate in the survey [...]]]></description>
		<wfw:commentRss>http://www.blognerds.com/gnu/ms-funded-study-atacks-gpl3-draft-process.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MS-Funded Study Attacks GPL3 Draft Process</title>
		<link>http://www.blognerds.com/gnu/ms-funded-study-attacks-gpl3-draft-process.html</link>
		<comments>http://www.blognerds.com/gnu/ms-funded-study-attacks-gpl3-draft-process.html#comments</comments>
		<pubDate>Tue, 22 May 2007 18:53:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[gnu]]></category>

		<guid isPermaLink="false">http://blognerds.com/2007/05/22/ms-funded-study-attacks-gpl3-draft-process/</guid>
		<description><![CDATA[QCMBR writes &#8220;A new Microsoft-funded study by a Harvard Business School professor concludes that developers don&#8217;t want extensive patent licensing requirements in the GPL3. There are significant problems with the study, however, especially given the very small sample size. &#8216;Although 332 emails were sent to various developers, only 34 agreed to participate in the survey [...]]]></description>
		<wfw:commentRss>http://www.blognerds.com/gnu/ms-funded-study-attacks-gpl3-draft-process.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

