Comments on: SpringSource will charge for updates to Spring, what comes next? http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/ no buzzwords allowed Wed, 01 Feb 2012 18:42:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Antoine http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/comment-page-1/#comment-2044 Antoine Wed, 01 Oct 2008 06:05:27 +0000 http://dow.ngra.de/?p=314#comment-2044 Hi, I think that SpringSource will shoot themselves in the foot if they decide to charge for simple things like documentation as you predict. However, it would be interesting to see how successful SpringSource's current training and consultancy is - if they out price themselves, then they have no one to blame if they don't have enough revenue. I doubt we'll see this information, of course ... A Hi,

I think that SpringSource will shoot themselves in the foot if they decide to charge for simple things like documentation as you predict.

However, it would be interesting to see how successful SpringSource’s current training and consultancy is – if they out price themselves, then they have no one to blame if they don’t have enough revenue. I doubt we’ll see this information, of course …

A

]]> By: Chris http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/comment-page-1/#comment-1912 Chris Tue, 23 Sep 2008 19:35:47 +0000 http://dow.ngra.de/?p=314#comment-1912 >They might also still mark the releases in the >tree, just not make the binaries available. -- No they won't. Rod Johnson confirmed on TSS that there will be NO tags in the SVN. Basically its just BS from Spring Source. What is bothering is that it has become a trend these days to have a friendly license in the beginning and once you have a loyal community, you go back and lay it on them. >They might also still mark the releases in the >tree, just not make the binaries available.

–

No they won’t. Rod Johnson confirmed on TSS that there will be NO tags in the SVN.

Basically its just BS from Spring Source.
What is bothering is that it has become a trend these days to have a friendly license in the beginning and once you have a loyal community, you go back and lay it on them.

]]> By: whaley http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/comment-page-1/#comment-1843 whaley Sun, 21 Sep 2008 15:33:11 +0000 http://dow.ngra.de/?p=314#comment-1843 " # Making access to the Spring forums and FAQ paid # Making full documentation available only for a fee " I don't forsee SpringSource (or any company that actually wants to make money) doing this. Doing those two things is a great way to peeve your development community and make entry into said community much more difficult. The other possible scenarios you gave do seem valid, however. ”
# Making access to the Spring forums and FAQ paid
# Making full documentation available only for a fee
”

I don’t forsee SpringSource (or any company that actually wants to make money) doing this. Doing those two things is a great way to peeve your development community and make entry into said community much more difficult. The other possible scenarios you gave do seem valid, however.

]]> By: Jevgeni Kabanov http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/comment-page-1/#comment-1836 Jevgeni Kabanov Sun, 21 Sep 2008 12:52:04 +0000 http://dow.ngra.de/?p=314#comment-1836 Yep, pretty much like that. I just meant that the patches are still open source and if you live on the trunk you will have them. They might also still mark the releases in the tree, just not make the binaries available. I guess we'll see. Yep, pretty much like that. I just meant that the patches are still open source and if you live on the trunk you will have them. They might also still mark the releases in the tree, just not make the binaries available.

I guess we’ll see.

]]> By: Tom Davies http://dow.ngra.de/2008/09/21/springsource-will-charge-for-updates-to-spring-what-comes-next/comment-page-1/#comment-1830 Tom Davies Sun, 21 Sep 2008 11:00:17 +0000 http://dow.ngra.de/?p=314#comment-1830 You say "the patches will still be available in the open source trunk, but you’ll have to compile them yourself". Isn't it worse than that? IIf I am using Spring x.y.z, and SpringSource release x.y.(z+1) which is not available under an open source license but contains bug fixes I need, I either need to backport the fixes from trunk to x.y.z, which might not be trivial, depending how much trunk has changed relative to x.y.z or upgrade to using a snapshot of trunk. Or have I misunderstood? You say “the patches will still be available in the open source trunk, but you’ll have to compile them yourself”.

Isn’t it worse than that? IIf I am using Spring x.y.z, and SpringSource release x.y.(z+1) which is not available under an open source license but contains bug fixes I need, I either need to backport the fixes from trunk to x.y.z, which might not be trivial, depending how much trunk has changed relative to x.y.z or upgrade to using a snapshot of trunk.

Or have I misunderstood?

]]>