Open Stack

On 2017-07-24 11:56:36 -0400 (-0400), David Moreau Simard wrote:
[...]
> For me, ARA falls in the same category of software that was
> created by the OpenStack community as Jenkins Job Builder [2] and
> git-review [3]. From the licensing requirements documentation [4]:
> 
> > Projects run as part of the OpenStack Infrastructure (in order
> > to produce OpenStack software) may be licensed under any
> > OSI-approved license. This includes tools that are run with or
> > on OpenStack projects only during validation or testing phases
> > of development (e.g., a source code linter).
[...]

That document is specifically about deliverables of official
OpenStack project teams. It does not apply to unofficial teams,
whose license choices are not particularly regulated (though if we
found out someone was hosting development of non-libre software on
our infrastructure I'm certain we'd force them to move elsewhere).

> While ARA is currently labelled with an Apache 2.0 license, some
> components of it are coupled to Ansible which is GPLv3.
[...]

We even have an official (Infra team) deliverable in the exact same
situation today:

<URL: http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/README.rst?id=0c47c43#n258 >

> Would this re-licensing mean that ARA could no longer be hosted by
> the OpenStack community infrastructure ?
[...]

There's plenty of unofficial software being developed and hosted by
our community infrastructure which doesn't meet our community's
various licensing and CLA requirements for official OpenStack
deliverables. As long as you're okay with the choice of license and
the logistics of getting relicensing approval from your prior
contributors, I don't see a problem with it.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: Digital signature
URL: <http://lists.openstack.org/pipermail/legal-discuss/attachments/20170724/3b67431b/attachment.sig>