Open Stack

Hi amrith,

I can see the patches got merged against that bug with similar changes:

[python-cinderclient] https://review.openstack.org/#/c/47453/2/cinderclient/base.py
[ironic] https://review.openstack.org/#/c/47451/2/ironic/common/image_service.py

Do you think these changes needs to be reverted ?

Thank you,
Dinesh Bhor

-----Original Message-----
From: Amrith Kumar [mailto:amrith at tesora.com] 
Sent: Monday, July 25, 2016 4:30 PM
To: legal-discuss at lists.openstack.org
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [keystone][murano][trove][imm] Changing OpenStack LLC to OpenStack Foundation

Bug 1214176 seeks to "Fix copyright headers to be compliant with Foundation policies" and one of the changes being made is to substitute "OpenStack Foundation" in places where the code said "OpenStack LLC".

Someone just pushed changes to Keystone, Murano and Trove today and I have some concerns about this change.

Consider the following changes, [2], [3], [4], and [5].

They assert a copyright in 2011 or 2010 of an entity called "OpenStack Foundation" that was only established in 2012 [6].

Are these changes legally accurate?

-amrith

[1] https://bugs.launchpad.net/bugs/1214176
[2] https://review.openstack.org/#/c/346675/1/keystone/policy/backends/rules.py
[3] https://review.openstack.org/#/c/346673/1/tools/install_venv.py
[4] https://review.openstack.org/#/c/346669/1/murano/common/cf_config.py
[5] https://review.openstack.org/#/c/346669/1/murano/common/config.py
[6] http://www.businesswire.com/news/home/20120919005997/en/OpenStack-Launches-Independent-Foundation-Begins-Work-Protecting


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.