Open Stack

I agree with Allison's approach. Most importantly, we need to have the license in the file since currently they appear not to have a license.

-----Original Message-----
From: Allison Randal [mailto:allison at lohutok.net] 
Sent: Thursday, July 19, 2018 9:21 AM
To: mail at clusums.eu; legal-discuss at lists.openstack.org
Subject: Re: [legal-discuss] Third party file inclusion in Openstack sushy project

[EXTERNAL MESSAGE]

On 07/18/2018 02:15 PM, mail at clusums.eu wrote:
> 
> 1) Can I include these files in sushy project as they are?

A clarification would be useful here: do you really need to commit a
copy of the files into the sushy git repository? Most external
dependencies in OpenStack projects are installed from remote sources
during the build process (like, Python dependencies are installed from
Python's normal archive for Python packages).

Jeremy is right that the BSD licenses are generally considered
compatible for use in Apache 2.0 projects. I'm guessing what Mark wants
to review has more to due with copyright, since DMTF hasn't signed a
contributor agreement with OpenStack Foundation. But, that wouldn't be a
problem if you were just installing those files as an external
dependency, instead of committing them into the git repository.


It's also worth asking DMTF if they would mind putting a license notice
somewhere in the software. A simple file named LICENSE containing a copy
of the license text (located in
http://redfish.dmtf.org/schemas/registries/) would be a good start. In
future versions they could add a mention of the license to their README
files, and might consider adding a License tag into the Copyright block
of the JSON files.

Allison

_______________________________________________
legal-discuss mailing list
legal-discuss at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss

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.