<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Competing with the &#8220;Open Source Way&#8221;</title>
	<atom:link href="http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/</link>
	<description>Dave Stephens on technology and business trends</description>
	<lastBuildDate>Wed, 08 Dec 2010 23:20:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Manoj Ranaweera&#8217;s Blog &#187; Blog Archive &#187; Who cares about ebdex&#8217;s API? You should if you want to make money!</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1124</link>
		<dc:creator><![CDATA[Manoj Ranaweera&#8217;s Blog &#187; Blog Archive &#187; Who cares about ebdex&#8217;s API? You should if you want to make money!]]></dc:creator>
		<pubDate>Fri, 11 Aug 2006 05:42:04 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1124</guid>
		<description><![CDATA[[...] Dave Stephens, CEO of Coupa commented on Competing with the “Open Source Way&quot; at his Procurement Central. Extracts from his comments (modified to suit): [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Dave Stephens, CEO of Coupa commented on Competing with the “Open Source Way&quot; at his Procurement Central. Extracts from his comments (modified to suit): [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah Eisner</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1089</link>
		<dc:creator><![CDATA[Noah Eisner]]></dc:creator>
		<pubDate>Wed, 09 Aug 2006 16:30:33 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1089</guid>
		<description><![CDATA[I&#039;m definitely not going to argue that Procurement is &quot;sexy&quot;.  Procurement isn&#039;t Linux.  But that&#039;s not what it takes to be successful in open source applications.  There are several examples of companies making headway (yes, it is early).  As an example, sales force automation isn&#039;t the most sexy thing either, but SugarCRM seems to be getting a community developed.  Same thing for other vendors in content management, business intellligence, etc.

On the LGPL issue, I&#039;m not a lawyer and maybe you are.    You&#039;ll see that enterprise application open source projects have gone with mostly GPL, LGPL and MPL (or derivates of MPL). We felt our license choice offers the best opportunity for our customers, our channel partners and ourselves to be successful.  Could someone fork our Open Source code...yes.  That&#039;s actually a fundamental aspect of open source.   That isn&#039;t necessarily bad from Coupa&#039;s standpoint...nor is it bad from a market standpoint.   We also think that some companies will want to go with our Enterprise Edition, which will include additional innovative features, enhanced support, product updates, certifications, etc.

In the end, we believe that the Coupa solution offers the best value for customers.  We&#039;re bringing innovation to a market that hasn&#039;t seen much lately.  We know this because that&#039;s what companies are telling us.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m definitely not going to argue that Procurement is &#8220;sexy&#8221;.  Procurement isn&#8217;t Linux.  But that&#8217;s not what it takes to be successful in open source applications.  There are several examples of companies making headway (yes, it is early).  As an example, sales force automation isn&#8217;t the most sexy thing either, but SugarCRM seems to be getting a community developed.  Same thing for other vendors in content management, business intellligence, etc.</p>
<p>On the LGPL issue, I&#8217;m not a lawyer and maybe you are.    You&#8217;ll see that enterprise application open source projects have gone with mostly GPL, LGPL and MPL (or derivates of MPL). We felt our license choice offers the best opportunity for our customers, our channel partners and ourselves to be successful.  Could someone fork our Open Source code&#8230;yes.  That&#8217;s actually a fundamental aspect of open source.   That isn&#8217;t necessarily bad from Coupa&#8217;s standpoint&#8230;nor is it bad from a market standpoint.   We also think that some companies will want to go with our Enterprise Edition, which will include additional innovative features, enhanced support, product updates, certifications, etc.</p>
<p>In the end, we believe that the Coupa solution offers the best value for customers.  We&#8217;re bringing innovation to a market that hasn&#8217;t seen much lately.  We know this because that&#8217;s what companies are telling us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnonymousCoward</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1074</link>
		<dc:creator><![CDATA[AnonymousCoward]]></dc:creator>
		<pubDate>Wed, 09 Aug 2006 05:14:09 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1074</guid>
		<description><![CDATA[To quote Manoj Ranaweera above, 

&gt;&gt;We will make our API “Open Source”. It does not make commercial sense to make “ebdex Document Exchange” “Open Source” given its a hub and spoke solution.

If I am a developer,

why would I care if your API is open source or closed source? If it is not standards based, what&#039;s the incentive for me to make use of your API? If it&#039;s not LGPL based, what&#039;s the incentive for me to evaluate it? If you are going to make money ultimately through your commercial entity, why would I contribute my time and effort for your cause, unless there is some benefit for me as well?

If it is based on some standards, if my interest is to implement the standard, I will probably write the API myself. But if I want to make use of your API into my own applicatation, the moment it&#039;s not LGPL, then I wouldn&#039;t care a bit.

Now, if I am a end user, 

why do I care if your software is open source, if it&#039;s java or COBOL as long as it can get my work done. The reason why your company&#039;s webserver is using Apache 1.3.26 with Frontpage 5.0.2.2510 on a Red-Hat Linux is probably not because Apache&#039;s code is available as an open source for you to look at the code, but because it&#039;s &quot;free&quot; to either your or your hosting company.

Great open source softwares linke Linux and Apache succeeded because these are applications that wets their appetite. How many college kids are interested in writing an Inventory Management or a Procurement software when there is so much cooler stuff like Flickr or MySpace type of stuff going on?

There is so much more I can keep writing on this subject. I am not saying that open source is not a good idea. Instead, I am saying that one can&#039;t expect to automatically survive in a competitve market by just making their code open source.

I was surprised to see Coupa being offered under LGPL! Not sure what made Dave and his guys choose this license but I haven&#039;t seen that many non-library type of solutions being offered as LGPLs. I mean, for all practical purposes nothing prevents me to repackage the entire software with my add-ons and if I some how make money, not pay a single dime to Coupa! Well, not that I have time and energy to do that :). I will wait and watch how this shapes up.]]></description>
		<content:encoded><![CDATA[<p>To quote Manoj Ranaweera above, </p>
<p>&gt;&gt;We will make our API “Open Source”. It does not make commercial sense to make “ebdex Document Exchange” “Open Source” given its a hub and spoke solution.</p>
<p>If I am a developer,</p>
<p>why would I care if your API is open source or closed source? If it is not standards based, what&#8217;s the incentive for me to make use of your API? If it&#8217;s not LGPL based, what&#8217;s the incentive for me to evaluate it? If you are going to make money ultimately through your commercial entity, why would I contribute my time and effort for your cause, unless there is some benefit for me as well?</p>
<p>If it is based on some standards, if my interest is to implement the standard, I will probably write the API myself. But if I want to make use of your API into my own applicatation, the moment it&#8217;s not LGPL, then I wouldn&#8217;t care a bit.</p>
<p>Now, if I am a end user, </p>
<p>why do I care if your software is open source, if it&#8217;s java or COBOL as long as it can get my work done. The reason why your company&#8217;s webserver is using Apache 1.3.26 with Frontpage 5.0.2.2510 on a Red-Hat Linux is probably not because Apache&#8217;s code is available as an open source for you to look at the code, but because it&#8217;s &#8220;free&#8221; to either your or your hosting company.</p>
<p>Great open source softwares linke Linux and Apache succeeded because these are applications that wets their appetite. How many college kids are interested in writing an Inventory Management or a Procurement software when there is so much cooler stuff like Flickr or MySpace type of stuff going on?</p>
<p>There is so much more I can keep writing on this subject. I am not saying that open source is not a good idea. Instead, I am saying that one can&#8217;t expect to automatically survive in a competitve market by just making their code open source.</p>
<p>I was surprised to see Coupa being offered under LGPL! Not sure what made Dave and his guys choose this license but I haven&#8217;t seen that many non-library type of solutions being offered as LGPLs. I mean, for all practical purposes nothing prevents me to repackage the entire software with my add-ons and if I some how make money, not pay a single dime to Coupa! Well, not that I have time and energy to do that :). I will wait and watch how this shapes up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Stephens</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1046</link>
		<dc:creator><![CDATA[Dave Stephens]]></dc:creator>
		<pubDate>Mon, 07 Aug 2006 17:43:44 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1046</guid>
		<description><![CDATA[biju, manoj, thx..  i&#039;ll need to post on how open source and commercial interests can align - there are a lot of open source commercial business models out there. but there&#039;s still a lot of experimentation going on in the space.]]></description>
		<content:encoded><![CDATA[<p>biju, manoj, thx..  i&#8217;ll need to post on how open source and commercial interests can align &#8211; there are a lot of open source commercial business models out there. but there&#8217;s still a lot of experimentation going on in the space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manoj Ranaweera</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1045</link>
		<dc:creator><![CDATA[Manoj Ranaweera]]></dc:creator>
		<pubDate>Mon, 07 Aug 2006 17:21:42 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1045</guid>
		<description><![CDATA[We will make our API &quot;Open Source&quot;. It does not make commercial sense to make &quot;ebdex Document Exchange&quot; &quot;Open Source&quot; given its a hub and spoke solution. 

Dave, as Biju wrote, I am also very much interested in knowing how you would make money! Whether we like it or not, we all need money!]]></description>
		<content:encoded><![CDATA[<p>We will make our API &#8220;Open Source&#8221;. It does not make commercial sense to make &#8220;ebdex Document Exchange&#8221; &#8220;Open Source&#8221; given its a hub and spoke solution. </p>
<p>Dave, as Biju wrote, I am also very much interested in knowing how you would make money! Whether we like it or not, we all need money!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biju</title>
		<link>http://stephensnexus.com/2006/08/06/competing-with-the-open-source-way/#comment-1044</link>
		<dc:creator><![CDATA[Biju]]></dc:creator>
		<pubDate>Mon, 07 Aug 2006 16:26:35 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/08/06/competing-with-the-open-source-way/#comment-1044</guid>
		<description><![CDATA[It is amazing to see so many open source solutions in the Enterprise App/CRM space.  How does giving away software make economic sense to these vendors?  How does Coupa plan to make money on it&#039;s software innovations?]]></description>
		<content:encoded><![CDATA[<p>It is amazing to see so many open source solutions in the Enterprise App/CRM space.  How does giving away software make economic sense to these vendors?  How does Coupa plan to make money on it&#8217;s software innovations?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

