WINE May Change To LGPL

isolation wrote to us about the proposal to change the Wine license to LGPL. Jeremey's got his ideas and reasons in the e-mail there, and it makes sense - Jeremy's a smart guy. There's a call for opinions on this as well, so read through it, and offer commentary.

Comments

A needed change to a standard licence

[papo]

I believe open source projects must try to use the standard and most used licences like xGPl ones or from FSF. This will help the ouside world view our community as a whole body and not a big mess(like I heard one day from a CEO).

Thank you.
José Paulo Papo, from Brazil

Good for wine.

[CDWert]

I think its important to know what "with some recent events I cannot disclose" is exactly. Wine is great stuff and its been getting better. I have not contributed to wine publically because of its current liscence. And for once, knowing the windows world as well as the linux I think I could actuallly make a decent contribution, but I dont want code I freely provide ending up in LinDows, or Transgamings WineX9I know it is different, for the moment but how long ?)

Any liscence change could not suoperceede the liscence under which the existing code tree was obtained, so development into a proprietary product could contine on those note, is a smart guy he knows this, thats what scares me, what does he know or see in the future of Wine that could endanger it at this point, Corel trying to say its all their code now because he is their employee (this is an example, dont spaz)

Its funny how most of the people wanting to "commercialize Wine, have ended up with their code avaiable, WHY ? Its just not ready for prime time as a proprietay product on its own they still NEED developemt beyoned their internal capabilities, Jeremy must know this too......

Once agaian what looms on the horizon for Wine ?

LGPL information

[cr@ckwhore]

For those unfamiliar, you can read the LGPL at the following URL:

http://www.opensource.org/licenses/lgpl-license.ht ml