[legal-discuss] Licensing options for new project (Kolla) entering big tent
Mark.Radcliffe at dlapiper.com
Fri Jul 10 01:19:59 UTC 2015
If we can get all of the code under a CLA we are fine but existing projects (which are not under ASLv2) would need to be carefully vetted.
From: Jeremy Stanley [mailto:fungi at yuggoth.org]
Sent: Thursday, July 09, 2015 2:08 PM
To: legal-discuss at lists.openstack.org
Subject: Re: [legal-discuss] Licensing options for new project (Kolla) entering big tent
On 2015-07-09 16:34:47 -0400 (-0400), Richard Fontana wrote:
> Or is the concern that a (say) GPL-licensed project might have had a
> pre-OpenStack history including contributions from individuals or
> entities that are not CLA signatories?
Perhaps a slight variation on this. One work can be a derivative of another copyleft-licensed work and (at least if the copylefted work's authors can't be found or don't all agree to dual-licensing/explicit exceptions) may be bound to the same license or some license whose terms are a superset of the inherited license.
We don't want to discourage people within our community from properly leveraging and extending existing free software whose provenance was not within our community. We create enough NIH/reinvented-wheel problems throughout the greater free software landscape as it is, and telling a team that they need to rewrite some base framework from scratch (because their work might be considered a derivative and therefore not Apache licensed) is just that.
[DISCLAIMER: I am most definitely not a lawyer!]
legal-discuss mailing list
legal-discuss at lists.openstack.org
Please consider the environment before printing this email.
The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you.
More information about the legal-discuss