<?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: A Question of Balance: Tuning the Maintenance Policy</title>
	<atom:link href="http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Tue, 16 Mar 2010 22:24:39 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JSolutions.se &#187; Klokt om Open Source</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-2/#comment-171243</link>
		<dc:creator>JSolutions.se &#187; Klokt om Open Source</dc:creator>
		<pubDate>Fri, 05 Feb 2010 09:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-171243</guid>
		<description>[...] En av personerna bakom Jetty, Greg Wilkins, skrev nyss något som jag tyckte var läsvärt om Open Source och kommersialisering &#8211; ett ämne som bl a är aktuellt inför Springs &#8221;Maintenance Policy&#8221;. [...]</description>
		<content:encoded><![CDATA[<p>[...] En av personerna bakom Jetty, Greg Wilkins, skrev nyss något som jag tyckte var läsvärt om Open Source och kommersialisering &#8211; ett ämne som bl a är aktuellt inför Springs &#034;Maintenance Policy&#034;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Changement de politique de &#171; Jawher&#39;s Blog</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-2/#comment-168800</link>
		<dc:creator>Changement de politique de &#171; Jawher&#39;s Blog</dc:creator>
		<pubDate>Tue, 13 Oct 2009 22:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-168800</guid>
		<description>[...] : L&#8217;annonce officielle en Anglais. Billet original publi&#233; sur les blogs de [...]</description>
		<content:encoded><![CDATA[<p>[...] : L&#039;annonce officielle en Anglais. Billet original publi&eacute; sur les blogs de [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krishnan</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-2/#comment-163495</link>
		<dc:creator>Krishnan</dc:creator>
		<pubDate>Wed, 15 Apr 2009 17:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-163495</guid>
		<description>Just saw this post. I apologize if this is late in coming. I use various Spring modules (jdbc, orm, mvc, core) in my projects. When I have issues, I try to look in to the source code (my and spring) first. If I still can not resolve them, I look in the forums for resolution or post my question there. 

By just skimming through the forums, you can find that there are many questions that go unanswered. If the questions are answered, it is often not by SpringSource experts involved in the issues, but by people who have encountered the same issues but just logged into the forum because they have issues of their own.

I understand that you have to support your enterprise customers to keep SpringSource viable but greater support and help to the (free) Spring forums would be greatly appreciated.</description>
		<content:encoded><![CDATA[<p>Just saw this post. I apologize if this is late in coming. I use various Spring modules (jdbc, orm, mvc, core) in my projects. When I have issues, I try to look in to the source code (my and spring) first. If I still can not resolve them, I look in the forums for resolution or post my question there. </p>
<p>By just skimming through the forums, you can find that there are many questions that go unanswered. If the questions are answered, it is often not by SpringSource experts involved in the issues, but by people who have encountered the same issues but just logged into the forum because they have issues of their own.</p>
<p>I understand that you have to support your enterprise customers to keep SpringSource viable but greater support and help to the (free) Spring forums would be greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fawefw</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-149251</link>
		<dc:creator>fawefw</dc:creator>
		<pubDate>Wed, 11 Mar 2009 23:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-149251</guid>
		<description>spring mvc and related technologies suck. end of story.</description>
		<content:encoded><![CDATA[<p>spring mvc and related technologies suck. end of story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rasmus Lund</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-138788</link>
		<dc:creator>Rasmus Lund</dc:creator>
		<pubDate>Thu, 08 Jan 2009 16:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-138788</guid>
		<description>I think the title &quot;A Question of Balance&quot; of Rods post is very well chosen.

On one hand SpringSource must have an income, so that they can invest in new development and keep the owners / investors happy.

On the other hand, SpringSource must not harm the godwill they have amongst the people, who choose technologies like Spring for their projects. I have not done any development on the Spring code - but I like to think, that I have contributed by &quot;spreading the word&quot; (I&#039;m one of those people listen to, when they choose which technologies to use). Having an open source product provides a company with a lot of very effective &quot;free marketing&quot;. If Spring had been a commercial product, it would never have gotten much attention (I guess).

Thus SpringSource must strike a balance between earning money and at the same time:
* must not offend the people that help spread Spring (and people don&#039;t want to help what the see as greedy companies)
* must not &quot;force&quot; the open source purists to do a fork of the Spring code
* must ensure developers/companies can try out / learn how to us Spring for free in small projects before they decide to use Spring in large projects

I think SpringSource has to be very careful not to harm their image. Spring is not that unique anymore, EJB has gotten a lot better and Seam might be challenger as well. Actually I think it is a lot easier to get started using EJB 3 than it is to get started using Spring (which wasn&#039;t the case with EJB 2.x).</description>
		<content:encoded><![CDATA[<p>I think the title &#034;A Question of Balance&#034; of Rods post is very well chosen.</p>
<p>On one hand SpringSource must have an income, so that they can invest in new development and keep the owners / investors happy.</p>
<p>On the other hand, SpringSource must not harm the godwill they have amongst the people, who choose technologies like Spring for their projects. I have not done any development on the Spring code &#8211; but I like to think, that I have contributed by &#034;spreading the word&#034; (I&#039;m one of those people listen to, when they choose which technologies to use). Having an open source product provides a company with a lot of very effective &#034;free marketing&#034;. If Spring had been a commercial product, it would never have gotten much attention (I guess).</p>
<p>Thus SpringSource must strike a balance between earning money and at the same time:<br />
* must not offend the people that help spread Spring (and people don&#039;t want to help what the see as greedy companies)<br />
* must not &#034;force&#034; the open source purists to do a fork of the Spring code<br />
* must ensure developers/companies can try out / learn how to us Spring for free in small projects before they decide to use Spring in large projects</p>
<p>I think SpringSource has to be very careful not to harm their image. Spring is not that unique anymore, EJB has gotten a lot better and Seam might be challenger as well. Actually I think it is a lot easier to get started using EJB 3 than it is to get started using Spring (which wasn&#039;t the case with EJB 2.x).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Campbell&#8217;s Blog &#187; Blog Archive &#187; Reaction to the Spring Source Maintenance Policy</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-127847</link>
		<dc:creator>Matt Campbell&#8217;s Blog &#187; Blog Archive &#187; Reaction to the Spring Source Maintenance Policy</dc:creator>
		<pubDate>Thu, 06 Nov 2008 15:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-127847</guid>
		<description>[...] rather behind in my news reader, I was relieved to read Rod Johnson&#8217;s post detailing an updated maintenance policy. The biggest deal to mean is that the current version of spring will see maintenance releases until [...]</description>
		<content:encoded><![CDATA[<p>[...] rather behind in my news reader, I was relieved to read Rod Johnson&#039;s post detailing an updated maintenance policy. The biggest deal to mean is that the current version of spring will see maintenance releases until [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rod Johnson</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-125180</link>
		<dc:creator>Rod Johnson</dc:creator>
		<pubDate>Wed, 15 Oct 2008 17:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-125180</guid>
		<description>Bill

I&#039;m sorry if I offended anyone. I didn&#039;t mean to. I certainly didn&#039;t mean to classify &quot;every single developer who has ever downloaded a Spring binary release without contributing code&quot; as a &quot;freeloader&quot;, and apologize if any of my posts gave that impression. (Btw, I&#039;m pretty sure I didn&#039;t use the term &quot;freeloader&quot;.) I agree that an army of developers contributes to the spread of open source and helps it to succeed--and that&#039;s great. I was thinking more of large *companies* and their relationship with the software they use. I believe that that is a very real issue and it&#039;s important to raise it.

If I am one of the voices of open source (thanks for the compliment, btw), I think that talking about the sustainability of open source--where it comes from and how it can be depended on in the long term--is an important contribution. It&#039;s an issue I&#039;ve felt strongly about for years. I realize that my position does offend those who believe that open source is &quot;free software&quot;: I just don&#039;t believe the data is on their side, and there&#039;s not much point being a &quot;voice of open source&quot; and not honestly expressing my opinions. I don&#039;t believe that open source can escape economics, and I think it&#039;s dangerously short-sighted to think that it can.

The end result is that we have a policy that is fair for developers (taking nothing away from them, and offering the potential for more features, faster, through concentration of effort), but which incents large enterprises to pay. I think that&#039;s a perfect solution.

Rgds
Rod</description>
		<content:encoded><![CDATA[<p>Bill</p>
<p>I&#039;m sorry if I offended anyone. I didn&#039;t mean to. I certainly didn&#039;t mean to classify &#034;every single developer who has ever downloaded a Spring binary release without contributing code&#034; as a &#034;freeloader&#034;, and apologize if any of my posts gave that impression. (Btw, I&#039;m pretty sure I didn&#039;t use the term &#034;freeloader&#034;.) I agree that an army of developers contributes to the spread of open source and helps it to succeed&#8211;and that&#039;s great. I was thinking more of large *companies* and their relationship with the software they use. I believe that that is a very real issue and it&#039;s important to raise it.</p>
<p>If I am one of the voices of open source (thanks for the compliment, btw), I think that talking about the sustainability of open source&#8211;where it comes from and how it can be depended on in the long term&#8211;is an important contribution. It&#039;s an issue I&#039;ve felt strongly about for years. I realize that my position does offend those who believe that open source is &#034;free software&#034;: I just don&#039;t believe the data is on their side, and there&#039;s not much point being a &#034;voice of open source&#034; and not honestly expressing my opinions. I don&#039;t believe that open source can escape economics, and I think it&#039;s dangerously short-sighted to think that it can.</p>
<p>The end result is that we have a policy that is fair for developers (taking nothing away from them, and offering the potential for more features, faster, through concentration of effort), but which incents large enterprises to pay. I think that&#039;s a perfect solution.</p>
<p>Rgds<br />
Rod</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill VanHorne</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-125172</link>
		<dc:creator>Bill VanHorne</dc:creator>
		<pubDate>Wed, 15 Oct 2008 16:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-125172</guid>
		<description>Rod,

A big &quot;thank you&quot; for listening to the concerns of Spring adopters/supporters; well done. If only other software houses were so attentive to their users ...

Now, some constructive criticism. When Rod Johnson speaks, like it or not, the whole open-source world is listening. Your initial announcement of the maintenance policy change was confusing and you know that. However the *real* damage you have done to SI and Spring in general was caused by your initial attempts at clarifying the situation.

You managed to classify every single developer who has ever downloaded a Spring binary release without contributing code to the project as a free-loader whose opinion and business you do not value. 
I don&#039;t think that was what you meant to do, but I&#039;m willing to be proven wrong. I think you&#039;re aware of the fact that your Enterprise sales come from the initial adoption and evangelizing by developers. These same developers don&#039;t have the time to contribute to OSS projects but do drive OSS adoption in their companies from the trenches of software development.
 
Your comments, especially in the TSS forums, infuriated a good many of them, several of whom I manage. Insulting the very people evangelizing the use of your software stack in a large corporation doesn&#039;t make much sense. I know from experience that there was an initial rush to Guice and Tapestry just after your first attempts at clarification.

You&#039;re no longer &quot;Rod Johnson, developer&quot; or even &quot;Rod Johnson, consultant&quot;. You are now &quot;Rod Johnson, CEO of SI and voice of open source&quot;. Be very, very careful about what you say and how you say it.

Locally, I have put out this fire but there&#039;s now a level of distrust of Spring and of *you* that is not going to go away any time soon.</description>
		<content:encoded><![CDATA[<p>Rod,</p>
<p>A big &#034;thank you&#034; for listening to the concerns of Spring adopters/supporters; well done. If only other software houses were so attentive to their users &#8230;</p>
<p>Now, some constructive criticism. When Rod Johnson speaks, like it or not, the whole open-source world is listening. Your initial announcement of the maintenance policy change was confusing and you know that. However the *real* damage you have done to SI and Spring in general was caused by your initial attempts at clarifying the situation.</p>
<p>You managed to classify every single developer who has ever downloaded a Spring binary release without contributing code to the project as a free-loader whose opinion and business you do not value.<br />
I don&#039;t think that was what you meant to do, but I&#039;m willing to be proven wrong. I think you&#039;re aware of the fact that your Enterprise sales come from the initial adoption and evangelizing by developers. These same developers don&#039;t have the time to contribute to OSS projects but do drive OSS adoption in their companies from the trenches of software development.</p>
<p>Your comments, especially in the TSS forums, infuriated a good many of them, several of whom I manage. Insulting the very people evangelizing the use of your software stack in a large corporation doesn&#039;t make much sense. I know from experience that there was an initial rush to Guice and Tapestry just after your first attempts at clarification.</p>
<p>You&#039;re no longer &#034;Rod Johnson, developer&#034; or even &#034;Rod Johnson, consultant&#034;. You are now &#034;Rod Johnson, CEO of SI and voice of open source&#034;. Be very, very careful about what you say and how you say it.</p>
<p>Locally, I have put out this fire but there&#039;s now a level of distrust of Spring and of *you* that is not going to go away any time soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Wilkins</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-125099</link>
		<dc:creator>Greg Wilkins</dc:creator>
		<pubDate>Wed, 15 Oct 2008 05:36:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-125099</guid>
		<description>Rod,
firstly let me say that I think that this issue has mostly been one of style over substance.  I think people have taken exception more to the words used than any actual deeds done by SpringSoft.

However, I do have some concern over the open source business model that you wish you could implement. It&#039;s a meme that I&#039;ve seen a few times now, which I think is a little contrary to the spirit of open source.   I&#039;ve blog about this here: http://blogs.webtide.com/gregw/entry/open_source_is_free_software</description>
		<content:encoded><![CDATA[<p>Rod,<br />
firstly let me say that I think that this issue has mostly been one of style over substance.  I think people have taken exception more to the words used than any actual deeds done by SpringSoft.</p>
<p>However, I do have some concern over the open source business model that you wish you could implement. It&#039;s a meme that I&#039;ve seen a few times now, which I think is a little contrary to the spirit of open source.   I&#039;ve blog about this here: <a href="http://blogs.webtide.com/gregw/entry/open_source_is_free_software" rel="nofollow">http://blogs.webtide.com/gregw/entry/open_source_is_free_software</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Changing open source terms bad move in a recession &#124; Programming Archive</title>
		<link>http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/comment-page-1/#comment-125003</link>
		<dc:creator>Changing open source terms bad move in a recession &#124; Programming Archive</dc:creator>
		<pubDate>Tue, 14 Oct 2008 14:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=431#comment-125003</guid>
		<description>[...] updates for its community version.  Now it has reversed course, CEO Rod Johnson explaining things in this blog post. Some have stated concerns that Spring would cease to be open source. The phrase “license [...]</description>
		<content:encoded><![CDATA[<p>[...] updates for its community version.  Now it has reversed course, CEO Rod Johnson explaining things in this blog post. Some have stated concerns that Spring would cease to be open source. The phrase “license [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
