Hello,

Following a suggestion from Jeremy Stanley (below), I'm contacting this list. If I understand Jeremy correctly, checking code in to StackForge does not transfer any IP, or grant any rights, other than those granted in the license declaration that we make in our code (in this case, the Apache 2.0 license).  Is that correct?

Many thanks,

Joe Marshall.

-----Original Message-----

From: Emma Gordon

Sent: 06 May 2015 13:06

To: Joe Marshall

Subject: FW: [openstack-dev] [Fuel][Plugin] Contributor license agreement for fuel plugin code?

-----Original Message-----

From: Jeremy Stanley [mailto:fungi@yuggoth.org]

Sent: 06 May 2015 12:58

To: OpenStack Development Mailing List (not for usage questions)

Subject: Re: [openstack-dev] [Fuel][Plugin] Contributor license agreement for fuel plugin code?

On 2015-05-06 11:02:42 +0000 (+0000), Emma Gordon (projectcalico.org) wrote:

> If fuel plugin code is checked into a stackforge repository (as

> suggested in the fuel plugin wiki

> https://wiki.openstack.org/wiki/Fuel/Plugins#Repo), who owns that

> code?

I am not a lawyer, but my understanding is that the individual copyright holders mentioned in comments at the tops of various files, listed in an AUTHORS file (if included) and indicated within the repository's Git commit history retain rights over their contributions in a project relying on the Apache License (or those rights may belong to their individual respective employers in a work-for-hire situation as well).

> Is there a contributor license agreement to sign? (For example,

> contributors to OpenStack would sign this

> https://review.openstack.org/static/cla.html)

If Fuel is planning to apply for inclusion in OpenStack, then it may make sense to get all current and former contributors to its source repositories to agree to the OpenStack Individual Contributor License Agreement. Note that it does _not_ change the ownership of the software (copyrights), it's intended to simply reinforce the OpenStack Foundation's ability to continue to redistribute the software under the Apache License by affirming that the terms of the license are applied correctly and intentionally.

More detailed questions are probably best posed to the legal-discuss@lists.openstack.org mailing list, or to your own private legal representation.

--

Jeremy Stanley