My original posting was meant to elicit specific responses, for example, "we don't use xxx because...".
Or "we use xxx because" Google "open source license comparison" for info on the various licenses. Anyway, I'm kind of intriqued by the CPL, because it looks like the licensee must contribute and distribute any improvements. -- Bill ---------- Original Message ----------- From: "Alan Wolfe" <[EMAIL PROTECTED]> To: [email protected] Sent: Mon, 29 Jan 2007 11:29:06 -0800 Subject: Re: Witango-Talk: Open source license > How I understand the GPL is that people can use your code, but the > end user should be able to re-link it with a different version of > the GPL'd code. > > For instance... > > I make a software library under the GPL and Jeff uses my library to > make an awesome program. > > Jeff can sell that program, keep it closed source, whatever he wants > but the end user must be able to re-link that program to a different > version of my library (in case i put out an update, or they want to > use an older version of my library, or they want to use their own > modified version of the library). > > generally with desktop software this is satisfied in 1 of 2 ways. > > 1) Jeff makes his software open sourced > > or > > 2) Jeff links to my library using DLL's and keeps his software closed > source. People can build new DLL's and drop them in and the code > re-links to the new GPL'd code since DLLs are linked at run time. > > I'm really not sure how GPL works in the web world...who is the end > user, how can they relink etc. > > This probly makes more questions than it answers but hope it helps a > little bit :P > > On 1/29/07, Jeff Bohmer <[EMAIL PROTECTED]> wrote: > > >I want to release a component to the community. > > > > > >Does anyone have strong feelings about any of the various licenses: > > >GPL, LGPL, copyleft, etc.? > > > > IANAL, and you should really check with one before choosing a license. But > > here's some notes based on my limited understanding... > > > > Be aware that GPL might restrict people from using your component as part > > of a closed-source application. If this is the case, LGPL is the closest thing that may be used instead without imposing such a restriction. If you want a simple license that lifts all restrictions and only contains a 'do whatever you like with this as long as you keep this message in the source, and no warranty is provided' message, check out BSD. > > > > There are a lot of other licenses out there to choose from and it's worth > > investigating to choose one you'll be happy with for a long while. As the copyright holder, you can change the license down the road. But such a change may be disruptive to people who had been using the code under the old license. > > > > - Jeff > > -- > > > > Jeff Bohmer > > VisionLink, Inc. > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ------- End of Original Message ------- ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
