[License-review] For Approval: Rewrite of License Zero Reciprocal Public License

Kyle Mitchell kyle at kemitchell.com
Tue Nov 7 20:05:14 UTC 2017


On 2017-11-06 14:11, Bruce Perens wrote:
> On Mon, Nov 6, 2017 at 2:49 PM, Smith, McCoy <mccoy.smith at intel.com> wrote:
> > >>4. If you include this software in a larger piece of
> > >>   software, you must release any source code for that
> > >>   larger piece of software that has not yet been released.
> >
> > Is "include" the meaning in everyday English (inter alia, "to take in or
> > comprise as a part of a whole or group"), or in everyday computer
> > programming?  If the latter, you should make that clear.  If the former, I
> > think you have a potential OSD 9 problem, since this would dictate the
> > licensing of software merely on the same medium.
>
> Good point. Simple aggregation should not trigger your license. Combination
> into a single program should, and I'd be happy to see that not be limited
> to creation of a derivative work, since copyright law is somewhat unhelpful
> in that regard and case law is insufficient.

Following GPL 3.0, section 5, trailing paragraph:

  4. If you combine this software with other software to
     make a larger program, you must release any source code
     for that larger program that has not yet been released.

Does that avoid the issue in your readings?

-- 
Kyle Mitchell, attorney // Oakland // (510) 712 - 0933



More information about the License-review mailing list