<?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: Part 2 of Making Money with FOSS</title>
	<atom:link href="http://doctormo.org/2009/10/29/property-rights-and-attribution/feed/" rel="self" type="application/rss+xml" />
	<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/</link>
	<description>Just this guy, you know.</description>
	<lastBuildDate>Mon, 07 May 2012 13:19:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Zee</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2087</link>
		<dc:creator>Zee</dc:creator>
		<pubDate>Wed, 11 Nov 2009 06:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2087</guid>
		<description>Maybe the money can come in with additional services to enhance the FOSS.</description>
		<content:encoded><![CDATA[<p>Maybe the money can come in with additional services to enhance the FOSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miles</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2086</link>
		<dc:creator>Miles</dc:creator>
		<pubDate>Tue, 03 Nov 2009 18:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2086</guid>
		<description>Count me as one that doesn&#039;t fully get it yet.  Your posts discussing the difference between creating and distributing software were helpful, but it still seems to me that being able to charge for something essentially means having a monopoly on that thing, whether that thing is your time or some piece of property (intellectual or otherwise).  When a potential customer can get what they need for free, why would they pay for it?  Perhaps what you envision is a purely service economy (outside of hard goods such as toasters, in which case replication and distribution would have costs).  If you have any references that would help me understand where you&#039;re headed that would be great.  I&#039;d love for a robust economic model to grow out of FOSS, but I don&#039;t see it yet.

A related question: If I&#039;m a software developer who wants to work in line with FOSS principles, can I charge for anything other than my time?</description>
		<content:encoded><![CDATA[<p>Count me as one that doesn&#8217;t fully get it yet.  Your posts discussing the difference between creating and distributing software were helpful, but it still seems to me that being able to charge for something essentially means having a monopoly on that thing, whether that thing is your time or some piece of property (intellectual or otherwise).  When a potential customer can get what they need for free, why would they pay for it?  Perhaps what you envision is a purely service economy (outside of hard goods such as toasters, in which case replication and distribution would have costs).  If you have any references that would help me understand where you&#8217;re headed that would be great.  I&#8217;d love for a robust economic model to grow out of FOSS, but I don&#8217;t see it yet.</p>
<p>A related question: If I&#8217;m a software developer who wants to work in line with FOSS principles, can I charge for anything other than my time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2085</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 03 Nov 2009 15:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2085</guid>
		<description>There is only one but major thing wrong with your business model DoctorMo.
Your model assumes that users know what they want and while that may sometimes be true, most of the time it is not. There is a big difference between what users THINK they want, and what they ACTUALLY want. You can see that in many forms in FOSS, for example, there are users wanting option A to be added to program Z, when what they actually want is a better application behavior (and that option A is not really necessary). There is another problem with this, say a part of the userbase wants to add option B and another part don&#039;t want it, they want option C instead. You can&#039;t please everyone, so you&#039;ll either have to make a part of the userbase angry or fork the project so that both parts are satisfied. Then you have a problem of distribution... This can go on indefinitely and you end up with a hundred forks to maintain.
More serious problem is creating a new application. People often don&#039;t know what they want or need until they see it. That&#039;s just human nature, and buying is an impulsive thing. What you suggest is not buying - it&#039;s investment, but ordinary users don&#039;t want to invest in new and non existent software. This is especially true for entertainment software or games if you will. Would people invest in World of Goo or Caster? I doubt it. Those are some original and cool games which I think would have never made it with the &quot;investment&quot; business model.
That said, I hope you prove me wrong or that there is another solution for these issues.</description>
		<content:encoded><![CDATA[<p>There is only one but major thing wrong with your business model DoctorMo.<br />
Your model assumes that users know what they want and while that may sometimes be true, most of the time it is not. There is a big difference between what users THINK they want, and what they ACTUALLY want. You can see that in many forms in FOSS, for example, there are users wanting option A to be added to program Z, when what they actually want is a better application behavior (and that option A is not really necessary). There is another problem with this, say a part of the userbase wants to add option B and another part don&#8217;t want it, they want option C instead. You can&#8217;t please everyone, so you&#8217;ll either have to make a part of the userbase angry or fork the project so that both parts are satisfied. Then you have a problem of distribution&#8230; This can go on indefinitely and you end up with a hundred forks to maintain.<br />
More serious problem is creating a new application. People often don&#8217;t know what they want or need until they see it. That&#8217;s just human nature, and buying is an impulsive thing. What you suggest is not buying &#8211; it&#8217;s investment, but ordinary users don&#8217;t want to invest in new and non existent software. This is especially true for entertainment software or games if you will. Would people invest in World of Goo or Caster? I doubt it. Those are some original and cool games which I think would have never made it with the &#8220;investment&#8221; business model.<br />
That said, I hope you prove me wrong or that there is another solution for these issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NickFox</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2084</link>
		<dc:creator>NickFox</dc:creator>
		<pubDate>Tue, 03 Nov 2009 04:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2084</guid>
		<description>Martin, this has been very thought provoking and an interesting travel into the less commonly viewed side of FOSS, I have a follow up part 3 I invite you to read and post your thoughts upon.

http://www.rubmyubuntu.com/LinuxSoftwareBusiness/Part3</description>
		<content:encoded><![CDATA[<p>Martin, this has been very thought provoking and an interesting travel into the less commonly viewed side of FOSS, I have a follow up part 3 I invite you to read and post your thoughts upon.</p>
<p><a href="http://www.rubmyubuntu.com/LinuxSoftwareBusiness/Part3" rel="nofollow">http://www.rubmyubuntu.com/LinuxSoftwareBusiness/Part3</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2083</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Fri, 30 Oct 2009 04:08:57 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2083</guid>
		<description>Thank you for writing this great series of articles! I&#039;m truly glad to see someone outside of the FSF itself writing about these topics who really gets it, and really believes in the model. I know I&#039;ll refer skeptics to these writings in the future.</description>
		<content:encoded><![CDATA[<p>Thank you for writing this great series of articles! I&#8217;m truly glad to see someone outside of the FSF itself writing about these topics who really gets it, and really believes in the model. I know I&#8217;ll refer skeptics to these writings in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Owens</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2082</link>
		<dc:creator>Martin Owens</dc:creator>
		<pubDate>Thu, 29 Oct 2009 16:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2082</guid>
		<description>This is what I&#039;ve been doing, but every time I talk about it people like yourself just skip right over the proposal and go &quot;But FOSS doesn&#039;t make money does it&quot;, it&#039;s like I&#039;m not putting it in words that make sense yet.

You get paid for WRITING software, not for DISTRIBUTING software. If someone wants something written, then it should be possible for them to pay for someone to do it. Sounds easy, at the moment in FOSS we discourage people from paying for development, even though it does happen.

Although most FOSS programmers for the big projects are paid employees anyway, so we&#039;re not really talking about things like Linux, but other FOSS projects.</description>
		<content:encoded><![CDATA[<p>This is what I&#8217;ve been doing, but every time I talk about it people like yourself just skip right over the proposal and go &#8220;But FOSS doesn&#8217;t make money does it&#8221;, it&#8217;s like I&#8217;m not putting it in words that make sense yet.</p>
<p>You get paid for WRITING software, not for DISTRIBUTING software. If someone wants something written, then it should be possible for them to pay for someone to do it. Sounds easy, at the moment in FOSS we discourage people from paying for development, even though it does happen.</p>
<p>Although most FOSS programmers for the big projects are paid employees anyway, so we&#8217;re not really talking about things like Linux, but other FOSS projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirrus</title>
		<link>http://doctormo.org/2009/10/29/property-rights-and-attribution/comment-page-1/#comment-2081</link>
		<dc:creator>Kirrus</dc:creator>
		<pubDate>Thu, 29 Oct 2009 16:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://doctormo.wordpress.com/?p=1397#comment-2081</guid>
		<description>I think we&#039;ll always have closed source, because we all need to eat, and supporting something small, and niche via people paying for support just won&#039;t work.

If you really want to get rid of all closed source, then find a model that will allow developers to be paid, whilst not charging for the software. And the people who market the software. And the people who deal with the paychecks. And the website. Etc, etc,</description>
		<content:encoded><![CDATA[<p>I think we&#8217;ll always have closed source, because we all need to eat, and supporting something small, and niche via people paying for support just won&#8217;t work.</p>
<p>If you really want to get rid of all closed source, then find a model that will allow developers to be paid, whilst not charging for the software. And the people who market the software. And the people who deal with the paychecks. And the website. Etc, etc,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

