Re: [License-discuss] Strong and weak copyleft

2015-04-09 Thread Jim Jagielski
Well, the FSF itself uses the concept of weak: For example, when describing WxWidgets: Like the LGPL it is a weak copyleft license, so we recommend it only in special circumstances. So, at least according to https://www.gnu.org/philosophy/license-list.html, the FSF considers LGPL as weak

Re: [License-discuss] Strong and weak copyleft

2015-04-09 Thread Gervase Markham
On 09/04/15 15:27, Jim Jagielski wrote: Well, the FSF itself uses the concept of weak: For example, when describing WxWidgets: Like the LGPL it is a weak copyleft license, so we recommend it only in special circumstances. So, at least according to

Re: [License-discuss] Strong and weak copyleft

2015-04-09 Thread Rick Moen
Quoting Gervase Markham (g...@mozilla.org): The normal definition of weak that I have seen is a copyleft whose scope applies only to the code specifically licensed under it, e.g. the MPLv2. The LGPL rather falls in between this definition of weak, and the strong copyleft of the GPL. This

Re: [License-discuss] Strong and weak copyleft

2015-04-09 Thread Lawrence Rosen
Maybe we can summarize so far: ULTRA-STRONG(AGPL) STRONG (GPL) MORE THAN WEAK (LGPL) ALMOST WEAK (EPL) WEAK(MPL) VERY WEAK (APACHE) ULTRA-WEAK (CC0) This rather simple scale is not reflected in copyright law or any

Re: [License-discuss] Strong and weak copyleft

2015-04-09 Thread cowan
Jim Jagielski scripsit: So, at least according to https://www.gnu.org/philosophy/license-list.html, the FSF considers LGPL as weak copyleft. Looking at the uses of 'weak' on that page suggests that to the FSF, at least, a weak copyleft license is one that permits the licensed work to be

Re: [License-discuss] Strong and weak copyleft

2015-04-08 Thread Maximilian
Interesting - I always thought that the distinction between strong and weak copyleft was in respect of how the code is linked. Are there any/many examples however of weak copyleft given that definition? I would have thought that weak copyleft under that definition would be largely ineffective, as

Re: [License-discuss] Strong and weak copyleft

2015-04-07 Thread Ben Tilly
I believe that the legal key is distribution of the licensed code, not linking to it. The LGPL defines a Combined Work and has requirements on what is required when you distribute a combined work together. The intent is clearly that if you distribute the combined work together and DO NOT meet

Re: [License-discuss] Strong and weak copyleft

2015-04-07 Thread Simon Phipps
It looks like you may consider LGPL to be a weak copyleft license; my apologies if you don't! But if you do... I do not believe the LGPL to be a weak copyleft license. Strong copyleft implies that the scope of the required reciprocity is the source needed to create the distributed binary, while