Matthew, ColdSpring (and Spring) uses the Apache 2.0 License, which is probably the most commercial-friendly open-source license out there. Because the code is licensed that way TODAY means that the code as it stands TODAY will always be free to use in any project. I'm not saying that there's any plans to change the license, I'm just saying it's impossible to retroactively change the license of distributed code.
http://www.apache.org/licenses/LICENSE-2.0 "Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form." That pretty much says it - you can do whatever you want with ColdSpring. The license prevent me from suing you for using code I wrote, and the license prevents you from suing me if you think the code I wrote caused you harm. The only thing I'm allowed to point to that uses ColdSpring (because the project itself is opensource), is something called FMDRL, which you can read about here: http://www.fmdrl.org thanks, Dave On 8/25/06, Matthew Lesko <[EMAIL PROTECTED]> wrote:
The risk, or management concern if you will, I am trying to address is liability. Think SCO & Unix. The thought process here is: how do we know it's truly open source and we won't be sued at some point down the line for infringing someone's commercial copyright? This would make our exposure large because we're looking at Coldsrping for inclusion within a commercial product. So what I was hoping to see from posting to the Coldspring list is several larger players step forward to say they're using them. Then if the legality came into question, there is safety in larg(er) numbers. At least so goes the thinking here. As far as quality and functionality are concerned, I've implemented consulting projects with both Reactor and Coldspring without issue. So that is not a concern for me nor others here I think. In that case, the liability question is not a concern, because the projects are one-offs. So I need to justify Coldspring specifically, not Spring, in order to implement in my environment. Regards, Matthew Lesko Scott Arbeitman wrote: > First, I am using Spring in a very high-traffic banking site in > Australia. The results have been pretty good. I use it to handle > pluggable bits of a small framework I wrote: basically for XML-based > configuration. > > I think more of an argument comes from who is using Spring for Java. > There you'll find heaps of big players in the enterprise space. A > quick search on a major employment site will no doubt turn up many > positions with Spring, Struts, and or Hibernate as a required skill. > > Kind Regards, > Scott Arbeitman > > On 25/08/2006, at 12:10 AM, Matt Williams wrote: > >> Search through Sean Corfield's blog (corfield.org). I'm pretty sure >> he's made mention of some apps he uses MG, ColdSpring and Reactor in >> there. Mostly internal stuff at adobe I think. >> >> On 8/24/06, Matthew Lesko <[EMAIL PROTECTED]> wrote: >>> I am trying to convince my manager to use Coldspring in our product. >>> Toward that end I am attempting to identify other commercial >>> services or >>> products that use Coldspring. Can anyone on the list tell me about what >>> they're doing along these lines or point to people who are? >>> >>> Regards, >>> Matthew Lesko >>> >>> >>> >>> >> >> >> --Matt Williams >> "It's the question that drives us." >> > > >
