July 2014 - legal-discuss - lists.openstack.org

Licensing of documentation
by Richard Fontana 17 Mar '15

17 Mar '15

Hi, Certain manuals available at docs.openstack.org contain this legal notice: Copyright © 2013 OpenStack Foundation Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. followed immdiately by a box that says: Except where otherwise noted, this document is licensed under Creative Commons Attribution ShareAlike 3.0 License http://creativecommons.org/licenses/by-sa/3.0/legalcode This github repository suggests at quickest glance that Apache License 2.0 is the license: https://github.com/openstack/openstack-manuals Some docs writers at Red Hat were previously under the impression that CC BY was the license of OpenStack documentation, which I assume is incorrect except for material specifically on wiki.openstack.org. Can anyone clarify? We'd like to adapt some portions of the upstream documentation in our product documentation and we want to make sure we get the licensing right. Thanks! Richard Fontana Legal Red Hat, Inc.

4 6

Invitation to working group on FLOSS entities
by Radcliffe, Mark 20 Jul '14

20 Jul '14

If you are interested in attending, you can attend in person at: Mozilla Portland Office Brewery Block 2 1120 NW Couch St Suite 320 Portland, OR 97209 Or you can attend by phone at the Mozilla conference line. There are several options for different US and international numbers and VOIP, full details are here: https://wiki.mozilla.org/Teleconferencing The local option is: US/Oregon/Portland: +1 971 544 8000, extension 92 Once you've dialed in (through any number), the conference number is 271. 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(a)dlapiper.com. Thank you.

1 1

Fwd: need some advise on publicizing a translated version of openstack document.
by Anne Gentle 17 Jul '14

17 Jul '14

Hi legal discussioners, Can you comment on this question? ---------- Forwarded message ---------- From: Jaesuk Ahn <bluejay.ahn(a)gmail.com> Date: Tue, Jul 15, 2014 at 9:45 PM Subject: need some advise on publicizing a translated version of openstack document. To: Anne Gentle <anne(a)openstack.org>, Tom Fifield <tom(a)openstack.org>, Openstack Users <openstack(a)lists.openstack.org> HI Anne and Tom, and everyone here in this mailing list, I do have one question, actually I am relaying a question from someone else in Korea regarding publication of documents. A professor in Korea did translate the entire openstack security-guide document, and he wants to publish translated version as a book with some price tag. He wants to know if he can talk with OpenStack Foundation regarding this commercial publication of OpenStack Document. I told him Document has Creative Common License, and he just needs to follow whatever CC license says. However, if possible, we would like to have some help from you guys =. First, we are not open source license experts. It is a bit tricky to know what CC license exactly means when someone wants to publish “translated version” of a openstack document. Second, he wants to have an opinion form openstack foundation about publication. If you have experienced a similar situation with this one, could you give us some hints or advise? Thank you. Jaesuk Ahn | Ph.D. Senior Director | Co-Founder cloud4u, Inc. *… active member of openstack community *

5 4

Appropriate use of OpenStack CCLA Schedule B...
by McCullough, Theodore 08 Jul '14

08 Jul '14

Hi Folks: I am interested in using the CCLA Schedule B as a vehicle to make contributions as per the OpenStack CCLA- "Contribution" shall mean the code, documentation or other original works of authorship expressly identified in Schedule B..." Currently, my thought is to post in the GIT Commit Message accompanying the contribution, "Per the terms of the CCLA, this is a CCLA Schedule B Submission" or "CCLA Schedule B Submission". I would like some feedback regarding using the Schedule B to make contributions. Thank you in advance for your thoughts. Best regards, -T. Ted McCullough Senior IP Counsel, EMC Corporation 2831 Mission College Blvd. Santa Clara, CA 95054 Email- Theodore.mccullough(a)emc.com<mailto:Theodore.mccullough@emc.com> Direct- 408.566.7936 Mobile- 206.595.2502 **THIS EMAIL MAY CONTAIN ATTORNEY-CLIENT PRIVILEGED COMMUNICATIONS AND/OR ATTORNEY WORK PRODUCT** [cid:image001.png@01CF9A0F.684D7F50]

2 1

Appropriate use of OpenStack CCLA Schedule B...
by McCullough, Theodore 08 Jul '14

08 Jul '14

Hi Folks: I am interested in using the CCLA Schedule B as a vehicle to make contributions as per the OpenStack CCLA- "Contribution" shall mean the code, documentation or other original works of authorship expressly identified in Schedule B..." Currently, my thought is to post in the GIT Commit Message accompanying the contribution, "Per the terms of the CCLA, this is a CCLA Schedule B Submission" or "CCLA Schedule B Submission". I would like some feedback regarding using the Schedule B to make contributions. Thank you in advance for your thoughts. Best regards, -T.

2 1

Orange SA : Openstack contribution's process for a supplier of Orange
by christophe.martinez＠orange.com 07 Jul '14

07 Jul '14

Dear Mr/Mrs/Ms, Your address was giving to me by Stefano Maffulli (OpenStack Foundation). Pleased find, attached to this email, my exchange with Stefano. I'm writing because we signed a CCLA in July or August 2013 with OpenStack (see the documents signed attached to this email) in order to contribute to the community and we are working with a supplier which will be a contributor in the OpenStack community. So we would this supplier contributes directly and on behalf of Orange to your Community. Therefore, Orange has done everything with its supplier in order to give it the rights to contribute on behalf of Orange SA. By the way, we have read within the CCLA (item 4 in the CCLA signed by Orange, pleased find my attached file on this email) this sentence : "You represent further that each employee of the Corporation designated on Schedule A below (or in a subsequent written modification to that Schedule) is authorized to submit Contributions on behalf of the Corporation." You talk about "employees of the Corporation" but what does it means about an employee of a supplier of Orange SA? Supposing that supplier has all the rights by Orange to contribute on behalf of Orange within OpenStack community. Is it possible to add directly the name and the address (email, phone etc.) of the employee(s) of the supplier in the Orange SA's contributors CLA list? Thank you for your help and do not hesitate to ask us if you require any further informations. Regards, Christophe Martinez. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1