<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Ma.gnolia: Deryck Hodge's Bookmarks Tagged With "license"</title>
    <link>http://ma.gnolia.com/rss/lite/people/deryck/tags/license</link>
    <atom:link rel="self" href="http://ma.gnolia.com/rss/lite/people/deryck/tags/license"/>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Deryck Hodge's Bookmarks Tagged With "license"</description>
    <creativeCommons:license>
http://creativecommons.org/licenses/by-nc-sa/2.5/    </creativeCommons:license>
    <item>
      <title>The GPL and Principles</title>
      <dc:creator>
deryck      </dc:creator>
      <creativeCommons:license>
http://creativecommons.org/licenses/by-nc-sa/2.5/      </creativeCommons:license>
      <description>&lt;p&gt;I've been enjoying reading the last few pots from Ian Bicking.  This is the most recent as of this linking, and he has some thoughtful and insightful comments on the principles that underpin the GPL.  A couple posts earlier he talks about the GPL vs. the permissive licenses.  He's very fair, avoiding the territory of flame wars, and though I generally prefer the GPL exactly for the principles it conveys, I do understand that there are pros and cons either way, and each license has strengths and weaknesses.&lt;/p&gt;
</description>
      <pubDate>Tue, 06 May 2008 12:20:16 PDT</pubDate>
      <link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles//don/</link>
      <guid>http://ma.gnolia.com/people/deryck/bookmarks/dresicokak</guid>
      <category domain="http://ma.gnolia.com/tags">open source</category>
      <category domain="http://ma.gnolia.com/tags">freedom</category>
      <category domain="http://ma.gnolia.com/tags">free software</category>
      <category domain="http://ma.gnolia.com/tags">gpl</category>
      <category domain="http://ma.gnolia.com/tags">license</category>
    </item>
  </channel>
</rss>
