<?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: Funding the Next Round of Software at Puppet Labs</title>
	<atom:link href="http://puppetlabs.com/blog/funding-the-next-round-of-software-at-puppet-labs/feed/" rel="self" type="application/rss+xml" />
	<link>http://puppetlabs.com/blog/funding-the-next-round-of-software-at-puppet-labs/</link>
	<description>Puppet Labs: The Leading IT Automation Software Solution</description>
	<lastBuildDate>Fri, 10 Feb 2012 00:01:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: luke</title>
		<link>http://puppetlabs.com/blog/funding-the-next-round-of-software-at-puppet-labs/comment-page-1/#comment-911</link>
		<dc:creator>luke</dc:creator>
		<pubDate>Sat, 28 Aug 2010 00:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.puppetlabs.com/?p=2581#comment-911</guid>
		<description>Hi,

I&#039;m personally still struggling with how to describe the different ways of distributing what will eventually be a completely free version of Puppet and a non-free version, but the reality is that marketing has a real purpose, which is to help us describe what we&#039;re doing in terms the audience understands.  This often entails us being forced to use terms that we&#039;re unhappy with (like CMDB) but that our audience knows and likes.

At this point the whole open source/free thing has gotten silly.  I had Richard Stallman yell at me in an ice cream shop because I personally don&#039;t care about this political fight so I used the term he doesn&#039;t like, even though I was trying to say I supported his work.

I&#039;m just trying to build a business producing great software, and the reality is that engineers are bloody expensive, and it&#039;s tough to build a great business producing great software without somehow paying your engineers.  I expect I&#039;ll continue to make mistakes and struggle through what to do, what to call it, and how to make money until the heat death of the universe, or at least my own expiration.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;m personally still struggling with how to describe the different ways of distributing what will eventually be a completely free version of Puppet and a non-free version, but the reality is that marketing has a real purpose, which is to help us describe what we&#8217;re doing in terms the audience understands.  This often entails us being forced to use terms that we&#8217;re unhappy with (like CMDB) but that our audience knows and likes.</p>
<p>At this point the whole open source/free thing has gotten silly.  I had Richard Stallman yell at me in an ice cream shop because I personally don&#8217;t care about this political fight so I used the term he doesn&#8217;t like, even though I was trying to say I supported his work.</p>
<p>I&#8217;m just trying to build a business producing great software, and the reality is that engineers are bloody expensive, and it&#8217;s tough to build a great business producing great software without somehow paying your engineers.  I expect I&#8217;ll continue to make mistakes and struggle through what to do, what to call it, and how to make money until the heat death of the universe, or at least my own expiration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: windowsrefund</title>
		<link>http://puppetlabs.com/blog/funding-the-next-round-of-software-at-puppet-labs/comment-page-1/#comment-903</link>
		<dc:creator>windowsrefund</dc:creator>
		<pubDate>Wed, 25 Aug 2010 13:39:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.puppetlabs.com/?p=2581#comment-903</guid>
		<description>Luke,

Attempting to describe &quot;open source&quot; vs. &quot;commercial&quot; software is a common mistake many people make. For starters, code that is &quot;open&quot; can certainly be sold commercially. In other words, the terms are not at odds with each other. By using this comparison when attempting to describe a piece of software, we end up implying that the only distinguishing quality of a particular group of bits is the final sticker price. As a brilliant programmer and long time sys-admin, you of all people know that this is the furthest thing from the truth. Also, by using words like &quot;open&quot; and &quot;closed&quot; to describe software, we essentially promote the agenda of the Open Source community which has all but abandoned the fundamental principles involving software freedoms 0-3 in favor of the pragmatic side-effects that usually can (and are) achieved as a result of those freedoms. In other words, it is foolish to value the functionality and/or perceived security of a piece of software over the freedoms to modify the software in order to improve either aspect. The former celebrates something static that is mostly based on perception while the latter celebrates endless potential.

A far better approach would be to just avoid all the market created terminology and simply stick to distinguishing software based on the freedoms provided by the license. The free software community achieves this by simply identifying software as either &quot;free&quot; or &quot;non-free&quot;. This of course, has nothing to do with the commercial feasibility of the software. The description simply calls attention to the most important qualities a particular piece of software offers to its user base; the freedom (or not) to use for any purpose, modify, and/or redistribute.

http://www.gnu.org/philosophy/open-source-misses-the-point.html

Many thanks ,

 A puppet user who values Free Software and its community.</description>
		<content:encoded><![CDATA[<p>Luke,</p>
<p>Attempting to describe &#8220;open source&#8221; vs. &#8220;commercial&#8221; software is a common mistake many people make. For starters, code that is &#8220;open&#8221; can certainly be sold commercially. In other words, the terms are not at odds with each other. By using this comparison when attempting to describe a piece of software, we end up implying that the only distinguishing quality of a particular group of bits is the final sticker price. As a brilliant programmer and long time sys-admin, you of all people know that this is the furthest thing from the truth. Also, by using words like &#8220;open&#8221; and &#8220;closed&#8221; to describe software, we essentially promote the agenda of the Open Source community which has all but abandoned the fundamental principles involving software freedoms 0-3 in favor of the pragmatic side-effects that usually can (and are) achieved as a result of those freedoms. In other words, it is foolish to value the functionality and/or perceived security of a piece of software over the freedoms to modify the software in order to improve either aspect. The former celebrates something static that is mostly based on perception while the latter celebrates endless potential.</p>
<p>A far better approach would be to just avoid all the market created terminology and simply stick to distinguishing software based on the freedoms provided by the license. The free software community achieves this by simply identifying software as either &#8220;free&#8221; or &#8220;non-free&#8221;. This of course, has nothing to do with the commercial feasibility of the software. The description simply calls attention to the most important qualities a particular piece of software offers to its user base; the freedom (or not) to use for any purpose, modify, and/or redistribute.</p>
<p><a href="http://www.gnu.org/philosophy/open-source-misses-the-point.html" rel="nofollow">http://www.gnu.org/philosophy/open-source-misses-the-point.html</a></p>
<p>Many thanks ,</p>
<p> A puppet user who values Free Software and its community.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

