<?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: The Trouble With &#8220;Free&#8221;: Open Source Woes</title>
	<atom:link href="http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/</link>
	<description>You dream it up, we code it to life.</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:14:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nick</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-2/#comment-4516</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 04 Jul 2009 19:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4516</guid>
		<description>One consideration may also be competitive advantage. If your money making blog has a feature or tool that others haven&#039;t, you have the advantage. Naming the free tool is just giving away secrets. It may have nothing to do with taking credit for your work.</description>
		<content:encoded><![CDATA[<p>One consideration may also be competitive advantage. If your money making blog has a feature or tool that others haven&#8217;t, you have the advantage. Naming the free tool is just giving away secrets. It may have nothing to do with taking credit for your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jesse.c</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-2/#comment-4255</link>
		<dc:creator>jesse.c</dc:creator>
		<pubDate>Wed, 27 May 2009 11:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4255</guid>
		<description>Guys ! you have really put wordpress on the iPhone. 
Credits to WPTouch are a must. Booo The People who Removed the credits...
 
We reach 100&#039;s of 1000&#039;s of folks through our Cydia repo for the iPhone  &amp; proudly display WPTouch since day one.

Many Thanks to you guys for the WPTouch, lifes much easier,we are able to present information and deliver packages much faster. 

Much Respect.
jesse.c</description>
		<content:encoded><![CDATA[<p>Guys ! you have really put wordpress on the iPhone.<br />
Credits to WPtouch are a must. Booo The People who Removed the credits&#8230;</p>
<p>We reach 100&#8242;s of 1000&#8242;s of folks through our Cydia repo for the iPhone  &amp; proudly display WPtouch since day one.</p>
<p>Many Thanks to you guys for the WPtouch, lifes much easier,we are able to present information and deliver packages much faster. </p>
<p>Much Respect.<br />
jesse.c</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Msrk Bossert</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-2/#comment-4190</link>
		<dc:creator>Msrk Bossert</dc:creator>
		<pubDate>Sun, 10 May 2009 21:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4190</guid>
		<description>Must be really frustrating to put in all the effort and time to create a very useful tool (now that I&#039;ve got it working properly, I love it!) and just ask for some credit... and have people not reciprocate.

Boo to them. 

A big &quot;thank you&quot; to you gents for your time and effort. I appreciate it and so do the users of our site.</description>
		<content:encoded><![CDATA[<p>Must be really frustrating to put in all the effort and time to create a very useful tool (now that I&#8217;ve got it working properly, I love it!) and just ask for some credit&#8230; and have people not reciprocate.</p>
<p>Boo to them. </p>
<p>A big &#8220;thank you&#8221; to you gents for your time and effort. I appreciate it and so do the users of our site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustav</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4181</link>
		<dc:creator>Gustav</dc:creator>
		<pubDate>Thu, 07 May 2009 17:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4181</guid>
		<description>Im just curious, i havent touched your plugin in anyway. But i cant see any credits at the bottom by default? :S Or is it only showed while surfing with a iPhone? Doesnt have a iPhone laying around so cant check. 

Just dont want to &quot;steal&quot; your work, because i appreciate the effort. All my iPhone buddies likes it :-)</description>
		<content:encoded><![CDATA[<p>Im just curious, i havent touched your plugin in anyway. But i cant see any credits at the bottom by default? :S Or is it only showed while surfing with a iPhone? Doesnt have a iPhone laying around so cant check. </p>
<p>Just dont want to &#8220;steal&#8221; your work, because i appreciate the effort. All my iPhone buddies likes it :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GPLguy</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4143</link>
		<dc:creator>GPLguy</dc:creator>
		<pubDate>Sat, 02 May 2009 00:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4143</guid>
		<description>@&lt;a href=&quot;#comment-4119&quot; rel=&quot;nofollow&quot;&gt;Dale Mugford&lt;/a&gt;: The point I was trying to make, was there isn&#039;t anything stopping me from legally taking WPTouch and creating WPFinger for instance.  The license allows this ability to &#039;fork&#039; provided they adhere to the GPL, ie maintain the license. I can&#039;t change the license to say BSD.

I have to say though I do appreciate all your hard work on WPtouch even if I haven&#039;t used it or WP yet.. stumbled across the site from WP while doing some recon ;)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4119" rel="nofollow">Dale Mugford</a>: The point I was trying to make, was there isn&#8217;t anything stopping me from legally taking WPtouch and creating WPFinger for instance.  The license allows this ability to &#8216;fork&#8217; provided they adhere to the GPL, ie maintain the license. I can&#8217;t change the license to say BSD.</p>
<p>I have to say though I do appreciate all your hard work on WPtouch even if I haven&#8217;t used it or WP yet.. stumbled across the site from WP while doing some recon ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4124</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Wed, 29 Apr 2009 00:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4124</guid>
		<description>Thanks, we certainly have put heart and soul, sweat and guts into it. At the end of the day more people appreciate and respect the work than use it for personal gain without a second thought- so we keep our heads up and continue to grow our works and contributions to the WordPress community.</description>
		<content:encoded><![CDATA[<p>Thanks, we certainly have put heart and soul, sweat and guts into it. At the end of the day more people appreciate and respect the work than use it for personal gain without a second thought- so we keep our heads up and continue to grow our works and contributions to the WordPress community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronnie Wayne Myers Jr.</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4122</link>
		<dc:creator>Ronnie Wayne Myers Jr.</dc:creator>
		<pubDate>Tue, 28 Apr 2009 21:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4122</guid>
		<description>First off Dale, I have to give you guys a huge thank you.  The work you guys do is so invaluable to me, I would feel stupid wasting the time it would take to remove your byline.

I do forget to include references and thank you notes for the developers that created the original scripts, and I am sure my own tweaky nature has moved or covered some up some by accident, but, I think the work you guys do warrants the application of a different license to ensure that you guys get the credit and the notoriety you all deserve.

I certainly understand your point, and I greatly appreciate the work you guys do.</description>
		<content:encoded><![CDATA[<p>First off Dale, I have to give you guys a huge thank you.  The work you guys do is so invaluable to me, I would feel stupid wasting the time it would take to remove your byline.</p>
<p>I do forget to include references and thank you notes for the developers that created the original scripts, and I am sure my own tweaky nature has moved or covered some up some by accident, but, I think the work you guys do warrants the application of a different license to ensure that you guys get the credit and the notoriety you all deserve.</p>
<p>I certainly understand your point, and I greatly appreciate the work you guys do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4119</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Tue, 28 Apr 2009 12:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4119</guid>
		<description>@GPLGuy: I understand that. Read my reply to Alex. We&#039;re not seeking to be protected under license as the plugin is free and open source, and GPL licensed. Even if we were, spending the cash to go after anyone who&#039;s doing what they&#039;re doing wouldn&#039;t be worth it, unless we were profiting from the work and it made sense to protect that.

I&#039;m simply whining a little about the problem of stolen works under the guise of &#039;GPL modifications&#039;. If you do nothing but remove a byline from another&#039;s work, that comes across as stealing to me, whether it&#039;s GPL or any other license, plain and simple.

Argue that, not whether the GPL forbids byline removal. I&#039;m saying &lt;em&gt;ethics should forbid it.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>@GPLGuy: I understand that. Read my reply to Alex. We&#8217;re not seeking to be protected under license as the plugin is free and open source, and GPL licensed. Even if we were, spending the cash to go after anyone who&#8217;s doing what they&#8217;re doing wouldn&#8217;t be worth it, unless we were profiting from the work and it made sense to protect that.</p>
<p>I&#8217;m simply whining a little about the problem of stolen works under the guise of &#8216;GPL modifications&#8217;. If you do nothing but remove a byline from another&#8217;s work, that comes across as stealing to me, whether it&#8217;s GPL or any other license, plain and simple.</p>
<p>Argue that, not whether the GPL forbids byline removal. I&#8217;m saying <em>ethics should forbid it.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GPLguy</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4118</link>
		<dc:creator>GPLguy</dc:creator>
		<pubDate>Tue, 28 Apr 2009 05:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4118</guid>
		<description>The GPL gives everyone the right to do what they like with the code, provided they release the source.

Bylines aren&#039;t remotely, in any shape or form, protected under the GPL, as AlexCurylo said above you should have released it under a different license.</description>
		<content:encoded><![CDATA[<p>The GPL gives everyone the right to do what they like with the code, provided they release the source.</p>
<p>Bylines aren&#8217;t remotely, in any shape or form, protected under the GPL, as AlexCurylo said above you should have released it under a different license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4110</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Sun, 26 Apr 2009 17:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4110</guid>
		<description>With themes it can be a common oversight- but in this case, we&#039;ve got the byline for WordPress and WPtouch and it gets ripped out by some.</description>
		<content:encoded><![CDATA[<p>With themes it can be a common oversight- but in this case, we&#8217;ve got the byline for WordPress and WPtouch and it gets ripped out by some.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Hoffman</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4109</link>
		<dc:creator>Bryan Hoffman</dc:creator>
		<pubDate>Sun, 26 Apr 2009 17:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4109</guid>
		<description>Good point Dale

I love Wordpress and spreading the good word about it. I&#039;m not sure why I don&#039;t have a footer link saying so. I&#039;ll be remedying that shortly.</description>
		<content:encoded><![CDATA[<p>Good point Dale</p>
<p>I love WordPress and spreading the good word about it. I&#8217;m not sure why I don&#8217;t have a footer link saying so. I&#8217;ll be remedying that shortly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4108</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Sun, 26 Apr 2009 14:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4108</guid>
		<description>I hear ya Alex- I&#039;m less talking explicitly about the terms of the GPL, but rather the unwritten, explicit nature of bylines, etc. Nowhere did I state that the GPL expressly forbids the removal of a byline. But simply removing the byline and doing nothing else to modify the work comes across as stealing to me.</description>
		<content:encoded><![CDATA[<p>I hear ya Alex- I&#8217;m less talking explicitly about the terms of the GPL, but rather the unwritten, explicit nature of bylines, etc. Nowhere did I state that the GPL expressly forbids the removal of a byline. But simply removing the byline and doing nothing else to modify the work comes across as stealing to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Curylo</title>
		<link>http://www.bravenewcode.com/2009/04/the-trouble-with-free-open-source-woes/comment-page-1/#comment-4107</link>
		<dc:creator>Alex Curylo</dc:creator>
		<pubDate>Sun, 26 Apr 2009 13:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bravenewcode.com/?p=1267#comment-4107</guid>
		<description>So what you guys want for a license isn&#039;t actually GPL then, it&#039;s something like the Attribution Assurance License, sounds like to me.

http://www.opensource.org/licenses/attribution.php</description>
		<content:encoded><![CDATA[<p>So what you guys want for a license isn&#8217;t actually GPL then, it&#8217;s something like the Attribution Assurance License, sounds like to me.</p>
<p><a href="http://www.opensource.org/licenses/attribution.php" rel="nofollow">http://www.opensource.org/licenses/attribution.php</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

