Fwd: need some advise on publicizing a translated version of openstack document.
Hi legal discussioners, Can you comment on this question? ---------- Forwarded message ---------- From: Jaesuk Ahn <bluejay.ahn@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@openstack.org>, Tom Fifield <tom@openstack.org>, Openstack Users <openstack@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 *
For reference, the book has the following on the inner page: """ Copyright © 2013 OpenStack Foundation Some rights reserved. Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License http://creativecommons.org/licenses/by/3.0/legalcode """ I suspect the intention here was to open the content, but retain the rights over the OpenStack logo/name/other marks. Regards, Tom On 16/07/14 07:00, Anne Gentle wrote:
Hi legal discussioners, Can you comment on this question?
---------- Forwarded message ---------- From: *Jaesuk Ahn* <bluejay.ahn@gmail.com <mailto:bluejay.ahn@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@openstack.org <mailto:anne@openstack.org>>, Tom Fifield <tom@openstack.org <mailto:tom@openstack.org>>, Openstack Users <openstack@lists.openstack.org <mailto:openstack@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 /
_______________________________________________ legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
The content is available under creative commons (which allows re-use and repurposing), however if it’s going to be marketed and sold commercially and make use of the OpenStack trademarks (name or logos), then he needs to work with the Foundation to get approval for that use. If he wants to reach out to Lauren Sell, we can help him go through that process. Jonathan On Jul 16, 2014, at 2:08 PM, Tom Fifield <tom@openstack.org> wrote:
For reference, the book has the following on the inner page:
""" Copyright © 2013 OpenStack Foundation Some rights reserved.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/legalcode """
I suspect the intention here was to open the content, but retain the rights over the OpenStack logo/name/other marks.
Regards,
Tom
On 16/07/14 07:00, Anne Gentle wrote:
Hi legal discussioners, Can you comment on this question?
---------- Forwarded message ---------- From: *Jaesuk Ahn* <bluejay.ahn@gmail.com <mailto:bluejay.ahn@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@openstack.org <mailto:anne@openstack.org>>, Tom Fifield <tom@openstack.org <mailto:tom@openstack.org>>, Openstack Users <openstack@lists.openstack.org <mailto:openstack@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 /
_______________________________________________ legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
_______________________________________________ legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
Tom, Thanks for helping here. Just curious about your reference. If we use a word “some”, should there be somewhere that has a definition of “some”? For example, something like.. a scope of “some” in this statement refer to “trademark agreement on using openstack logo”. Jaesuk Ahn | Ph.D. … active member of openstack community On Jul 17, 2014, 4:08:30 AM, Tom Fifield <tom@openstack.org> wrote: For reference, the book has the following on the inner page: """ Copyright © 2013 OpenStack Foundation Some rights reserved. Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License http://creativecommons.org/licenses/by/3.0/legalcode From: *Jaesuk Ahn* <mailto:bluejay.ahn@gmail.com <mailto:bluejay.ahn@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 <mailto:anne@openstack.org <mailto:anne@openstack.org>>, Tom Fifield <mailto:tom@openstack.org <mailto:tom@openstack.org>>, Openstack Users <mailto:openstack@lists.openstack.org <mailto:openstack@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 /
_______________________________________________ legal-discuss mailing list mailto:legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
On Thu, Jul 17, 2014 at 02:29:33PM +0900, Jaesuk Ahn wrote:
Tom,
Thanks for helping here. Just curious about your reference. If we use a word “some”, should there be somewhere that has a definition of “some”?
For example, something like.. a scope of “some” in this statement refer to “trademark agreement on using openstack logo”.
The phrase "Some rights reserved" is a catchphrase of Creative Commons, a play on the ancient "All rights reserved" which is still commonly seen in copyright notices today. (I don't think I've seen "Some rights reserved" in a legal notice before, apart from use of Creative Commons 'license buttons'.) Creative Commons has used "Some rights reserved" to signify that Creative Commons licenses grant a degree of permission traditionally not granted by most content copyright holders. If the "some" means anything there it refers to the specific text of CC BY 3.0, which actually doesn't mention trademarks at all other than those of Creative Commons. CC BY 4.0 actually specifies that trademark rights are not licensed under the Creative Commons license, which is a useful clarification. RF
participants (5)
-
Anne Gentle
-
Jaesuk Ahn
-
Jonathan Bryce
-
Richard Fontana
-
Tom Fifield