<?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/"
	
	>
<channel>
	<title>Comments on: Open Source Licenses</title>
	<atom:link href="http://www.epanorama.net/blog/2009/08/30/open-source-licenses/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Tue, 28 Apr 2026 21:36:21 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-1372571</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 07:59:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-1372571</guid>
		<description><![CDATA[Four ways Ubiquiti Networks is creatively violating the GPL
http://libertybsd.net/ubiquiti/

1. Giving the appearance of compliance
2. Refusing to provide the source to their modified bootloader, even though they made changes that introduced security vulnerabilities
3. Providing source code to a version of Linux, just not the one that they actually ship, and hoping that nobody notices
4. Dragging out GPL code requests for months on end, then inexplicably going silent]]></description>
		<content:encoded><![CDATA[<p>Four ways Ubiquiti Networks is creatively violating the GPL<br />
<a href="http://libertybsd.net/ubiquiti/" rel="nofollow">http://libertybsd.net/ubiquiti/</a></p>
<p>1. Giving the appearance of compliance<br />
2. Refusing to provide the source to their modified bootloader, even though they made changes that introduced security vulnerabilities<br />
3. Providing source code to a version of Linux, just not the one that they actually ship, and hoping that nobody notices<br />
4. Dragging out GPL code requests for months on end, then inexplicably going silent</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-904466</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 14 Aug 2014 06:58:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-904466</guid>
		<description><![CDATA[Open Source Businesses Programming
Ask Slashdot: Corporate Open Source Policy?
http://ask.slashdot.org/story/14/08/13/171230/ask-slashdot-corporate-open-source-policy

Comments:
Having a solid Contributor License Agreement process in place would probably be a good idea. That way, it&#039;s clear who owns the code that comes in and encourages people to contribute while defining a (necessary evil) process for doing so. You&#039;ll lose random passers-by, but just one passer-by who gets litigious could be more of a headache than it&#039;s worth.

I&#039;m not sure if the idea of a contributor license as you suggest is in the spirit of open source.

 In particular, make sure you actually own the copyrights or have a distribution license for everything you intend to open source. All it takes is one lazy cowboy coder and Google to screw your whole project. Also, understand the license you intend to distribute under, and what licenses are incompatible with it.

Or does corporate America avoid this entire opportunity/entanglement/briar patch?

Yes, to a large degree, and they&#039;re stuck in the last century. IP has always been an imaginary government monopoly meant to enhance the business interests of a certain caste; originally that was the author/inventor, but that ship has long sailed - now it&#039;s corporate profits almost exclusively (and you may find exceptions that prove the rule).]]></description>
		<content:encoded><![CDATA[<p>Open Source Businesses Programming<br />
Ask Slashdot: Corporate Open Source Policy?<br />
<a href="http://ask.slashdot.org/story/14/08/13/171230/ask-slashdot-corporate-open-source-policy" rel="nofollow">http://ask.slashdot.org/story/14/08/13/171230/ask-slashdot-corporate-open-source-policy</a></p>
<p>Comments:<br />
Having a solid Contributor License Agreement process in place would probably be a good idea. That way, it&#8217;s clear who owns the code that comes in and encourages people to contribute while defining a (necessary evil) process for doing so. You&#8217;ll lose random passers-by, but just one passer-by who gets litigious could be more of a headache than it&#8217;s worth.</p>
<p>I&#8217;m not sure if the idea of a contributor license as you suggest is in the spirit of open source.</p>
<p> In particular, make sure you actually own the copyrights or have a distribution license for everything you intend to open source. All it takes is one lazy cowboy coder and Google to screw your whole project. Also, understand the license you intend to distribute under, and what licenses are incompatible with it.</p>
<p>Or does corporate America avoid this entire opportunity/entanglement/briar patch?</p>
<p>Yes, to a large degree, and they&#8217;re stuck in the last century. IP has always been an imaginary government monopoly meant to enhance the business interests of a certain caste; originally that was the author/inventor, but that ship has long sailed &#8211; now it&#8217;s corporate profits almost exclusively (and you may find exceptions that prove the rule).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: terrastegels</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-5894</link>
		<dc:creator><![CDATA[terrastegels]]></dc:creator>
		<pubDate>Sun, 10 Jan 2010 12:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-5894</guid>
		<description><![CDATA[I find it amazing that you always find the time to write about things like this. I like your blog, so I hope that my post will inspire you to post some more good things!]]></description>
		<content:encoded><![CDATA[<p>I find it amazing that you always find the time to write about things like this. I like your blog, so I hope that my post will inspire you to post some more good things!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurie Jones</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-5892</link>
		<dc:creator><![CDATA[Laurie Jones]]></dc:creator>
		<pubDate>Mon, 21 Dec 2009 11:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-5892</guid>
		<description><![CDATA[Really worth my time. I just want to encourage you in continuing to post entries such as this one. Thank you.]]></description>
		<content:encoded><![CDATA[<p>Really worth my time. I just want to encourage you in continuing to post entries such as this one. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Ferguson</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-5890</link>
		<dc:creator><![CDATA[Lisa Ferguson]]></dc:creator>
		<pubDate>Fri, 18 Dec 2009 09:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-5890</guid>
		<description><![CDATA[This is the kind of entry that I&#039;m looking for. Keep up the good work. I look forward to your future entries.]]></description>
		<content:encoded><![CDATA[<p>This is the kind of entry that I&#8217;m looking for. Keep up the good work. I look forward to your future entries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: juan</title>
		<link>https://www.epanorama.net/blog/2009/08/30/open-source-licenses/comment-page-1/#comment-5886</link>
		<dc:creator><![CDATA[juan]]></dc:creator>
		<pubDate>Mon, 31 Aug 2009 01:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=449#comment-5886</guid>
		<description><![CDATA[Hi, im from Venezuela and i want to give you thanks about the article about PARALLEL PORT that i readed in ¨epanorama¨ , im student and it was very usefull ...  mm not really .. it was very fun to test... i traduced some of the article: the part abouT linux and PORTCONTROL.. and i posted it to my blog...i hope tou dont be angry..
your articles and circuits are very usefull
excuse me for my poor english,,,

watch the article here. http://blog-j.homelinux.com/?p=208  .....it just say how to install and use PORTCONTROL ..in spanish of course..]]></description>
		<content:encoded><![CDATA[<p>Hi, im from Venezuela and i want to give you thanks about the article about PARALLEL PORT that i readed in ¨epanorama¨ , im student and it was very usefull &#8230;  mm not really .. it was very fun to test&#8230; i traduced some of the article: the part abouT linux and PORTCONTROL.. and i posted it to my blog&#8230;i hope tou dont be angry..<br />
your articles and circuits are very usefull<br />
excuse me for my poor english,,,</p>
<p>watch the article here. <a href="http://blog-j.homelinux.com/?p=208" rel="nofollow">http://blog-j.homelinux.com/?p=208</a>  &#8230;..it just say how to install and use PORTCONTROL ..in spanish of course..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
