<?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: Ext JS and the fun with Open Source licenses</title>
	<atom:link href="http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Noah</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263243</link>
		<dc:creator>Noah</dc:creator>
		<pubDate>Mon, 28 Apr 2008 16:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263243</guid>
		<description>I just posted a commentary about Jack&#039;s post as well: http://noahk17.blogspot.com/2008/04/my-extjs-drama.html</description>
		<content:encoded><![CDATA[<p>I just posted a commentary about Jack&#8217;s post as well: <a href="http://noahk17.blogspot.com/2008/04/my-extjs-drama.html" rel="nofollow">http://noahk17.blogspot.com/2008/04/my-extjs-drama.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: graemerocher</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263184</link>
		<dc:creator>graemerocher</dc:creator>
		<pubDate>Sun, 27 Apr 2008 10:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263184</guid>
		<description>Although I sympathise with Jack&#039;s situation the fact is you cannot have your cake and eat it.

Jack has been able to expose Ext-JS to a huge amount of publicity that Ext-JS would not have got had it been licensed under a restrictive license like GPL

The result is he has used the community driven nature of open source software and obtained a large number of users as a result and now turned around and slapped those same users in the face.

You are either open or you are not, you cannot have it both ways.</description>
		<content:encoded><![CDATA[<p>Although I sympathise with Jack&#8217;s situation the fact is you cannot have your cake and eat it.</p>
<p>Jack has been able to expose Ext-JS to a huge amount of publicity that Ext-JS would not have got had it been licensed under a restrictive license like GPL</p>
<p>The result is he has used the community driven nature of open source software and obtained a large number of users as a result and now turned around and slapped those same users in the face.</p>
<p>You are either open or you are not, you cannot have it both ways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slightlyoff</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263178</link>
		<dc:creator>slightlyoff</dc:creator>
		<pubDate>Sun, 27 Apr 2008 03:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263178</guid>
		<description>Sean:

How is it impractical? We&#039;ve been managing to build a vibrant community of highly professional contributors for Dojo for years now. Many of us have gotten employment *because* of that work and the character of the community has remained in-tact. No license changes, no usage fees.

Everyone has a right to charge whatever they choose for their work, but I don&#039;t think you can extrapolate from one example to suggest that projects *must* charge usage fees to continue to produce high-quality work...unless you&#039;re also arguing that there&#039;s something fundamentally different about your chosen example. Otherwise, YUI, Dojo, TIBCO/GI, JQuery, Prototype and many others provide plenty of proof that you don&#039;t need to charge, and that&#039;s just in the JavaScript space. Taking a look at the larger world of Open Source makes the point even more plain.

Regards</description>
		<content:encoded><![CDATA[<p>Sean:</p>
<p>How is it impractical? We&#8217;ve been managing to build a vibrant community of highly professional contributors for Dojo for years now. Many of us have gotten employment *because* of that work and the character of the community has remained in-tact. No license changes, no usage fees.</p>
<p>Everyone has a right to charge whatever they choose for their work, but I don&#8217;t think you can extrapolate from one example to suggest that projects *must* charge usage fees to continue to produce high-quality work&#8230;unless you&#8217;re also arguing that there&#8217;s something fundamentally different about your chosen example. Otherwise, YUI, Dojo, TIBCO/GI, JQuery, Prototype and many others provide plenty of proof that you don&#8217;t need to charge, and that&#8217;s just in the JavaScript space. Taking a look at the larger world of Open Source makes the point even more plain.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Foushee</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263177</link>
		<dc:creator>Sean Foushee</dc:creator>
		<pubDate>Sun, 27 Apr 2008 01:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263177</guid>
		<description>A more commercial license is not only fair but well within the rights of Jack and Co. to demand.  While I love the open source community, without it I would never have learned most of what I know now, its quite impractical for major developers and software engineers to continue to create these terrific products and frameworks without expecting major commercial projects to compensate them for their use of the framework.</description>
		<content:encoded><![CDATA[<p>A more commercial license is not only fair but well within the rights of Jack and Co. to demand.  While I love the open source community, without it I would never have learned most of what I know now, its quite impractical for major developers and software engineers to continue to create these terrific products and frameworks without expecting major commercial projects to compensate them for their use of the framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyriakos</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263176</link>
		<dc:creator>Kyriakos</dc:creator>
		<pubDate>Sun, 27 Apr 2008 00:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263176</guid>
		<description>I dont mind the license change. The actual cost to buy the commercial license is low for the quality of the library. I&#039;m building a CMS on my spare time and a lot of it is based on ExtJS, even though for the time being i have no profit out of it i would gladly pay the commercial license fee once i&#039;m going commercial with my software. If i&#039;m getting money out of something i think its only fair to pay for every piece of code i used that&#039;s licensed to someone else.</description>
		<content:encoded><![CDATA[<p>I dont mind the license change. The actual cost to buy the commercial license is low for the quality of the library. I&#8217;m building a CMS on my spare time and a lot of it is based on ExtJS, even though for the time being i have no profit out of it i would gladly pay the commercial license fee once i&#8217;m going commercial with my software. If i&#8217;m getting money out of something i think its only fair to pay for every piece of code i used that&#8217;s licensed to someone else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: polterguy</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263175</link>
		<dc:creator>polterguy</dc:creator>
		<pubDate>Sat, 26 Apr 2008 23:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263175</guid>
		<description>Sorry, I can&#039;t help myself on this...
If we should &quot;help grow the open web&quot; why do you write so much about Flex and even have ADDS for it...?
Do you (Dion) consider Adobe Flex for being a member of the &quot;Open Web&quot;?</description>
		<content:encoded><![CDATA[<p>Sorry, I can&#8217;t help myself on this&#8230;<br />
If we should &#8220;help grow the open web&#8221; why do you write so much about Flex and even have ADDS for it&#8230;?<br />
Do you (Dion) consider Adobe Flex for being a member of the &#8220;Open Web&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263174</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Sat, 26 Apr 2008 23:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263174</guid>
		<description>&quot;I am sure these debates have taken way too much time and energy.&quot;

This is ridiculous. Being a social creature means being responsible to those you affect. People aren&#039;t entitled to his work, but they certainly are entitled to question his actions and to express how they&#039;re negatively impacted by the change. While the new license fits proprietary and GPL work, it has stunted an upgrade path for other open source licensed software that is incompatible with the GPL, and that came somewhat unexpectedly.

Controversy and debate shouldn&#039;t be bad words. Those are the things that help us improve how we relate to one another, which is far more important than being &quot;professional&quot;.</description>
		<content:encoded><![CDATA[<p>&#8220;I am sure these debates have taken way too much time and energy.&#8221;</p>
<p>This is ridiculous. Being a social creature means being responsible to those you affect. People aren&#8217;t entitled to his work, but they certainly are entitled to question his actions and to express how they&#8217;re negatively impacted by the change. While the new license fits proprietary and GPL work, it has stunted an upgrade path for other open source licensed software that is incompatible with the GPL, and that came somewhat unexpectedly.</p>
<p>Controversy and debate shouldn&#8217;t be bad words. Those are the things that help us improve how we relate to one another, which is far more important than being &#8220;professional&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: digitalIchi</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263173</link>
		<dc:creator>digitalIchi</dc:creator>
		<pubDate>Sat, 26 Apr 2008 23:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263173</guid>
		<description>One thing that would be a great service to the community and help with whole... &quot;Letâ€™s grow the Open Web. The bigger we grow it. The bigger the pie. And, then we all succeed.&quot; ... thing, is for Ajaxian with its power to get someone that actually knows something about the GPL license and it&#039;s application to an Ajax library to give their thought&#039;s on this subject.  There are many question people including myself have questions about it.</description>
		<content:encoded><![CDATA[<p>One thing that would be a great service to the community and help with whole&#8230; &#8220;Letâ€™s grow the Open Web. The bigger we grow it. The bigger the pie. And, then we all succeed.&#8221; &#8230; thing, is for Ajaxian with its power to get someone that actually knows something about the GPL license and it&#8217;s application to an Ajax library to give their thought&#8217;s on this subject.  There are many question people including myself have questions about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Schmucker</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263172</link>
		<dc:creator>Hans Schmucker</dc:creator>
		<pubDate>Sat, 26 Apr 2008 23:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263172</guid>
		<description>Well, that&#039;s OpenSource for you... but one by one.
1. If you want to publish your work as OpenSource, you&#039;ll have to play by OpenSource rules... you can choose to play by any other set of rules, but if you want to claim to be an OpenSource project, then you&#039;ve got to play by their rules, there&#039;s no way around that. Playing by your own rules is fine, just don&#039;t advertise as OS, but use a term reserved for these limited licenses like &quot;Shared Source&quot;, &quot;Free&quot; or &quot;Community-Driven&quot;.
2. I absolutely agree on the &quot;Asset&quot; system. OpenSource is about improving a project&#039;s sourcecode and while you should provide necessary components (such as an example theme), there&#039;s no need for content that does nothing for people that want to fork to be released as OpenSource as well. This is absolutely in line with what OpenSource is about.
3. If you don&#039;t want people to fork into legit projects, with or without your help, then OpenSource is not for you.

I know these rules are sometimes tough, but you&#039;ve got to see it like this: &quot;Open Source&quot; is like a seal of quality that you can use to advertise if you follow the rules.</description>
		<content:encoded><![CDATA[<p>Well, that&#8217;s OpenSource for you&#8230; but one by one.<br />
1. If you want to publish your work as OpenSource, you&#8217;ll have to play by OpenSource rules&#8230; you can choose to play by any other set of rules, but if you want to claim to be an OpenSource project, then you&#8217;ve got to play by their rules, there&#8217;s no way around that. Playing by your own rules is fine, just don&#8217;t advertise as OS, but use a term reserved for these limited licenses like &#8220;Shared Source&#8221;, &#8220;Free&#8221; or &#8220;Community-Driven&#8221;.<br />
2. I absolutely agree on the &#8220;Asset&#8221; system. OpenSource is about improving a project&#8217;s sourcecode and while you should provide necessary components (such as an example theme), there&#8217;s no need for content that does nothing for people that want to fork to be released as OpenSource as well. This is absolutely in line with what OpenSource is about.<br />
3. If you don&#8217;t want people to fork into legit projects, with or without your help, then OpenSource is not for you.</p>
<p>I know these rules are sometimes tough, but you&#8217;ve got to see it like this: &#8220;Open Source&#8221; is like a seal of quality that you can use to advertise if you follow the rules.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SchizoDuckie</title>
		<link>http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses/comment-page-1#comment-263170</link>
		<dc:creator>SchizoDuckie</dc:creator>
		<pubDate>Sat, 26 Apr 2008 20:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ext-js-and-the-fun-with-open-source-licenses#comment-263170</guid>
		<description>I can really understand that people need to make money, but the&#039;re no license whatsoever keeping people who care shit about that from just grabbing your JS and copying/altering it. That&#039;s the hard facts, but please, let these three or four people pet themselves on the back for pirating someone&#039;s stuff and hope that revenue will come from selling licenses.

One tip though. Stay professional whatever happens. Google knows all and this will stab you in the back when people do research about your license.</description>
		<content:encoded><![CDATA[<p>I can really understand that people need to make money, but the&#8217;re no license whatsoever keeping people who care shit about that from just grabbing your JS and copying/altering it. That&#8217;s the hard facts, but please, let these three or four people pet themselves on the back for pirating someone&#8217;s stuff and hope that revenue will come from selling licenses.</p>
<p>One tip though. Stay professional whatever happens. Google knows all and this will stab you in the back when people do research about your license.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

