<?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: BSD License Explained In Layman Terms</title>
	<atom:link href="http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Bob Berliner</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111470</link>
		<dc:creator>Bob Berliner</dc:creator>
		<pubDate>Tue, 12 Oct 2010 16:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111470</guid>
		<description><![CDATA[Google uses Yahoo BSD licensed code in iGoogle so take a look at how they copyright since you can bet they&#039;ve got some good attorneys making sure it&#039;s correct:


/* ===============BEGIN BSD LICENSED PORTION============= */
/*
Copyright (c) 2007, Yahoo! Inc. All rights reserved.
Code licensed under the BSD License:
http://developer.yahoo.net/yui/license.txt
version: 2.2.0
*/

#modules .yui-b {
  position:static;
  display:block;
  margin:0 0 1em 0;
  float:none;
  width:auto;
  overflow:hidden;
}
.yui-gb .yui-u {
  float:left;
  margin-left:2%;
  *margin-left:1.895%;
  width:32%;
}
.yui-gb div.first {
  margin-left:0;
}
#modules,.yui-gb {
  zoom:1;
}
/* ===============END BSD LICENSED PORTION============= */]]></description>
		<content:encoded><![CDATA[<p>Google uses Yahoo BSD licensed code in iGoogle so take a look at how they copyright since you can bet they&#8217;ve got some good attorneys making sure it&#8217;s correct:</p>
<p>/* ===============BEGIN BSD LICENSED PORTION============= */<br />
/*<br />
Copyright (c) 2007, Yahoo! Inc. All rights reserved.<br />
Code licensed under the BSD License:<br />
<a href="http://developer.yahoo.net/yui/license.txt" rel="nofollow">http://developer.yahoo.net/yui/license.txt</a><br />
version: 2.2.0<br />
*/</p>
<p>#modules .yui-b {<br />
  position:static;<br />
  display:block;<br />
  margin:0 0 1em 0;<br />
  float:none;<br />
  width:auto;<br />
  overflow:hidden;<br />
}<br />
.yui-gb .yui-u {<br />
  float:left;<br />
  margin-left:2%;<br />
  *margin-left:1.895%;<br />
  width:32%;<br />
}<br />
.yui-gb div.first {<br />
  margin-left:0;<br />
}<br />
#modules,.yui-gb {<br />
  zoom:1;<br />
}<br />
/* ===============END BSD LICENSED PORTION============= */</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111466</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Mon, 11 Oct 2010 04:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111466</guid>
		<description><![CDATA[So do I understand correctly that I can use code with a BSD license in an application that I intend to sell?  Where and how am I supposed to include the copyright and disclaimer portions with the application that utilizes said code?]]></description>
		<content:encoded><![CDATA[<p>So do I understand correctly that I can use code with a BSD license in an application that I intend to sell?  Where and how am I supposed to include the copyright and disclaimer portions with the application that utilizes said code?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: melwyn</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111436</link>
		<dc:creator>melwyn</dc:creator>
		<pubDate>Sat, 02 Oct 2010 19:32:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-111436</guid>
		<description><![CDATA[if i develop a software using python or gcc can i Sell it?
if i rewrite vlc player in java can i Sell it?
if i can sell should i make my source code public?]]></description>
		<content:encoded><![CDATA[<p>if i develop a software using python or gcc can i Sell it?<br />
if i rewrite vlc player in java can i Sell it?<br />
if i can sell should i make my source code public?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandeepan Kundu</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-109102</link>
		<dc:creator>Sandeepan Kundu</dc:creator>
		<pubDate>Mon, 22 Dec 2008 05:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-109102</guid>
		<description><![CDATA[as long as the copyright, conditions and disclaimer are present.
can somebody explain me this line in detail...
exactly what copyright msg should contain...

i am really confused with this terms....]]></description>
		<content:encoded><![CDATA[<p>as long as the copyright, conditions and disclaimer are present.<br />
can somebody explain me this line in detail&#8230;<br />
exactly what copyright msg should contain&#8230;</p>
<p>i am really confused with this terms&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-66690</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Mon, 27 Aug 2007 20:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-66690</guid>
		<description><![CDATA[Perhaps also important: &lt;a href=&quot;http://zzzoot.blogspot.com/2007/08/study-reduced-open-source-developer.html&quot; rel=&quot;nofollow&quot;&gt;
Study: Reduced Open Source developer productivity linked to &quot;restrictive&quot; FLOSS licenses (where &quot;restrictive&quot;=GPL and non-restrictive=BSD)&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>Perhaps also important: <a href="http://zzzoot.blogspot.com/2007/08/study-reduced-open-source-developer.html" rel="nofollow"><br />
Study: Reduced Open Source developer productivity linked to &#8220;restrictive&#8221; FLOSS licenses (where &#8220;restrictive&#8221;=GPL and non-restrictive=BSD)</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64588</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 09 Aug 2007 20:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64588</guid>
		<description><![CDATA[@jldugger- Yes. Simple typo, actually.  Updated with the fix.  Thanks for the heads up.]]></description>
		<content:encoded><![CDATA[<p>@jldugger- Yes. Simple typo, actually.  Updated with the fix.  Thanks for the heads up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jldugger</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64586</link>
		<dc:creator>jldugger</dc:creator>
		<pubDate>Thu, 09 Aug 2007 19:36:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64586</guid>
		<description><![CDATA[Lest this post become part of the interpretation of BSD, let&#039;s clarify that you&#039;re not allowed to use the name of the originating Parent Company, not &quot;your&quot; parent company, without permission. One makes sense, the other does not.]]></description>
		<content:encoded><![CDATA[<p>Lest this post become part of the interpretation of BSD, let&#8217;s clarify that you&#8217;re not allowed to use the name of the originating Parent Company, not &#8220;your&#8221; parent company, without permission. One makes sense, the other does not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: new back</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64571</link>
		<dc:creator>new back</dc:creator>
		<pubDate>Thu, 09 Aug 2007 15:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64571</guid>
		<description><![CDATA[That is true, you can&#039;t change the license. But, if you are not distriuting the work further you don&#039;t have to give out the modified source code either. You can&#039;t build an obligation (under present terms) that internally only used copies should all be published. And that&#039;s what providing a service in fact is under at least the terms used in GPLv2.]]></description>
		<content:encoded><![CDATA[<p>That is true, you can&#8217;t change the license. But, if you are not distriuting the work further you don&#8217;t have to give out the modified source code either. You can&#8217;t build an obligation (under present terms) that internally only used copies should all be published. And that&#8217;s what providing a service in fact is under at least the terms used in GPLv2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64568</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 09 Aug 2007 15:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64568</guid>
		<description><![CDATA[@new back-  Incorrect.  Any derivative work of GPL-licensed code must also retain the GPL license, regardless.  GPL code prevents the work from becoming proprietary.]]></description>
		<content:encoded><![CDATA[<p>@new back-  Incorrect.  Any derivative work of GPL-licensed code must also retain the GPL license, regardless.  GPL code prevents the work from becoming proprietary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: new back</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64559</link>
		<dc:creator>new back</dc:creator>
		<pubDate>Thu, 09 Aug 2007 14:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64559</guid>
		<description><![CDATA[To clarify this.

I was referring to creating a derivative using previously GPL-licensed software, and not having to release the code. I could take some GPL&#039;d webmail code, modify it heavily, start charging people for the magnificent new service, and never have to release a thing. In the service case the GPLv2 at least does not force me to release anything no matter how much GPL&#039;d software I use and for what. It is really obvious from the license when you investigate it objectively. 

Freedom is good. I don&#039;t believe in forced freedom. Maturing is a process that should be nurtured and guided, not forced. It won&#039;t succeed (well) that way.]]></description>
		<content:encoded><![CDATA[<p>To clarify this.</p>
<p>I was referring to creating a derivative using previously GPL-licensed software, and not having to release the code. I could take some GPL&#8217;d webmail code, modify it heavily, start charging people for the magnificent new service, and never have to release a thing. In the service case the GPLv2 at least does not force me to release anything no matter how much GPL&#8217;d software I use and for what. It is really obvious from the license when you investigate it objectively. </p>
<p>Freedom is good. I don&#8217;t believe in forced freedom. Maturing is a process that should be nurtured and guided, not forced. It won&#8217;t succeed (well) that way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64555</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 09 Aug 2007 13:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64555</guid>
		<description><![CDATA[@Joseph Scott-  Yes.  Any BSD-licensed derivative can be relicensed.  I am not granted the right to change the BSD-licensed software itself, only derivative works.

@Nobody- Yes.  BSD is not a copyleft license, as it is not GPL compatible.  However, a license being copyleft doesn&#039;t mean a lot to most lay people.  Only FSF and Gnu zealots worry about such things.  Other people worry about productivity and practicality.

@new back-  It&#039;s one thing to use tools that are GPL to create a service or software from scratch. It&#039;s another to create a GPL-licensed derivative of the service or software, and not release the code.  And yes, BSD is a truly liberating license.]]></description>
		<content:encoded><![CDATA[<p>@Joseph Scott-  Yes.  Any BSD-licensed derivative can be relicensed.  I am not granted the right to change the BSD-licensed software itself, only derivative works.</p>
<p>@Nobody- Yes.  BSD is not a copyleft license, as it is not GPL compatible.  However, a license being copyleft doesn&#8217;t mean a lot to most lay people.  Only FSF and Gnu zealots worry about such things.  Other people worry about productivity and practicality.</p>
<p>@new back-  It&#8217;s one thing to use tools that are GPL to create a service or software from scratch. It&#8217;s another to create a GPL-licensed derivative of the service or software, and not release the code.  And yes, BSD is a truly liberating license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: new back</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64533</link>
		<dc:creator>new back</dc:creator>
		<pubDate>Thu, 09 Aug 2007 07:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64533</guid>
		<description><![CDATA[If you provide a service such as Gmail using modified GPL&#039;d components you don&#039;t have to release the modified source code. The SAAS situation (distributing the results that come out of software) is quite different from working with actually distributed software. There&#039;s really nothing in the license forcing you to do that. This is true at least for v2, I have not read v3 yet since no significant project is yet using it.

The high level of freedom offered by BSD licenses is great.]]></description>
		<content:encoded><![CDATA[<p>If you provide a service such as Gmail using modified GPL&#8217;d components you don&#8217;t have to release the modified source code. The SAAS situation (distributing the results that come out of software) is quite different from working with actually distributed software. There&#8217;s really nothing in the license forcing you to do that. This is true at least for v2, I have not read v3 yet since no significant project is yet using it.</p>
<p>The high level of freedom offered by BSD licenses is great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nobody</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64532</link>
		<dc:creator>Nobody</dc:creator>
		<pubDate>Thu, 09 Aug 2007 07:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64532</guid>
		<description><![CDATA[I believe the licenses mess won&#039;t be any clearer with the &lt;a href=&quot;http://trolltech.com/products/qt/gplexception&quot; rel=&quot;nofollow&quot;&gt;new trolltech gpl exception&lt;/a&gt;. Anyway it&#039;s always good to remind clearly the point of most used licensed. I would add that BSD is not a copy-left license, it means you can modify the bsd-licensed code and use it as you want (redistribute the code in binary or source code format) without having to publish your modifications to anyone.]]></description>
		<content:encoded><![CDATA[<p>I believe the licenses mess won&#8217;t be any clearer with the <a href="http://trolltech.com/products/qt/gplexception" rel="nofollow">new trolltech gpl exception</a>. Anyway it&#8217;s always good to remind clearly the point of most used licensed. I would add that BSD is not a copy-left license, it means you can modify the bsd-licensed code and use it as you want (redistribute the code in binary or source code format) without having to publish your modifications to anyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Scott</title>
		<link>http://pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64512</link>
		<dc:creator>Joseph Scott</dc:creator>
		<pubDate>Thu, 09 Aug 2007 05:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2007/08/08/bsd-license-explained-in-layman-terms/#comment-64512</guid>
		<description><![CDATA[I don&#039;t think the BSD license grants people the ability to change the license of code exactly.  Work based on BSD licensed code can be under a different license (like Mac OS X using FreeBSD code).  That would be a situation where other licenses can apply.

That is different than taking the BSD licensed dd implementation and then distributing it as is without modification under a different license.  I don&#039;t believe the BSD license gives you the right to do that.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the BSD license grants people the ability to change the license of code exactly.  Work based on BSD licensed code can be under a different license (like Mac OS X using FreeBSD code).  That would be a situation where other licenses can apply.</p>
<p>That is different than taking the BSD licensed dd implementation and then distributing it as is without modification under a different license.  I don&#8217;t believe the BSD license gives you the right to do that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
