Jump to: navigation, search


Revision as of 20:45, 29 April 2013 by Markmc (talk | contribs) (Created page with "= Legal Issues FAQ = The [http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss legal-discuss@lists.openstack.org] mailing list is a forum for questions that have...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Legal Issues FAQ

The legal-discuss@lists.openstack.org mailing list is a forum for questions that have a legal aspect to them. These questions may concern (for example) licensing, third party packages, contributor agreement questions and trademark issues. The list will be used to build into an ad-hoc knowledge base in the form of this FAQ about those thorny legal issues that most commonly effect the OpenStack project.

Opinions documented here do not constitute legal advice from the OpenStack Foundation or the Legal Affairs Committee.


Q: Should we include NOTICE files in OpenStack projects?

A: If a NOTICE file exists in a project, the Apache License requires that that derivative works include the attribution notices from the file. This could be helpful for a number of purposes - (a) ensuring an attribution to the OpenStack project gets included in derivative works and (b) helping distributors of derivative works to include any required attribution notices for third party code included in the project. However, neither of these issues are deemed significant or important enough to warrant the cost of maintaining the files or requiring distributors to include an OpenStack project attribution notice.

For the full background, see this thread

Incorporating BSD Licensed Code

Q: If we include BSD licensed code in an OpenStack project, how best should we comply with the terms of the license?

A: The 2 core clauses in the BSD license make some demands about the retention of copyright notices, the license and disclaimers in both source and binary distributions of the code. Probably the easiest thing to do when incorporating BSD code is to copy the copyright/license header from the source file into the destination file, as well as copying the copyright notice, license and disclaimer into the toplevel LICENSE file with a brief explanation of which code is under that license.

For the full background, see this email.

OpenStack Foundation Copyright Headers

Q: Should I Include an OpenStack Foundation copyright header in my code?

A: Most existing OpenStack Foundation copyright headers you see in OpenStack code are likely relate to code from Rackspace developers before the OpenStack Foundation existed when OpenStack LLC was a wholly owned subsidiary of Rackspace. Once the foundation was formed, all OpenStack LLC assets (including copyrights) were transferred to the foundation and the copyright headers were updated. It's likely the only valid reason for OpenStack Foundation copyright notices on new code these days is where the code was authored by an employee or contractor of the foundation.

For the full background, see this thread.