News for hackers. Stuff that matters.
Re:Wine 2.0 released by a3_nm on Wednesday January 25, 2017 @07:06PM (#13487467)
Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeWeaver's fork of Wine was proprietary.

(Sources: https://en.wikipedia.org/wiki/Wine_(software)#History https://www.winehq.org/pipermail/wine-devel/2002-February/00...)

CodeWeaver's Wine variant still seems to be proprietary according to Wikipedia -- I wonder what made the relationship between CodeWeavers and Wine evolve.

Re:Wine 2.0 released by coldpie on Thursday January 26, 2017 @08:31AM (#13491111)
CodeWeavers's usage of Wine and other open-source projects has always been open-source. You can download our Wine fork source from our website[1]. We do use a small amount of closed-source glue to provide our installation magic and desktop integration.

Wine switched to LGPL due to other proprietary forks.

[1] https://www.codeweavers.com/products/more-information/source

Re:Wine 2.0 released by Fnoord on Thursday January 26, 2017 @01:43PM (#13494010)
> Wine switched to LGPL due to other proprietary forks.

Specifically, WineX aka Cedega

Re:Wine 2.0 released by bonzini on Wednesday January 25, 2017 @07:31PM (#13487639)
While there is some proprietary glue, all changes to the Wine code are (as they have to be) open source.
Re:Wine 2.0 released by mook on Wednesday January 25, 2017 @08:48PM (#13488057)
I believe it was actually that a different fork of Wine was not contributing back which caused the license change. I want to say it was Cedega but memories are hazy at this point (since I'm an outside observer).