monasca team mailing list archive

["Tomasz.Trebski@xxxxxxxxxxxxxx" <Tomasz.Trebski@xxxxxxxxxxxxxx>]

Hi Roland,

I just briefly checked on Nova and they have on LGPL license among requirements.
Also I managed to find this topic here => https://wiki.openstack.org/wiki/LegalIssuesFAQ, which clearly states
That LGPL and AGPL are license that are not considered problematic but that rule does not apply, at least not clearly, to GPL license.

Basically I looked there and there starting from the link posted above and it looks like, in most the cases, GPL license is a subject to 
discussion. I will try to find some time at home to check more OS projects to see if there is any occurrence of pure GPL so as to have
Someone to ask about steps they've been taking to ensure that everything is fine.

Tomasz Trębski

R&D Development Engineer / EST
Łódź GDC


-----Original Message-----
From: Hochmuth, Roland M [mailto:roland.hochmuth@xxxxxxx] 
Sent: Tuesday, November 17, 2015 2:43 PM
To: Trębski, Tomasz; monasca@xxxxxxxxxxxxxxxxxxx
Cc: Hodzic, Zawisza
Subject: Re: [Monasca] GPL in monasca-common

Hi Tomasz, This is an issue that we've discussed in the past. We extensively reviewed the use of the MySQL-Python library with HP legal and they felt in the case of Python, that this was acceptable.

However, even though this isn't an HP issue, I think we need to resolve it.

Do you know how the OpenStack projects, like nova neutron, are handling this?

Regards --Roland


From: "Tomasz.Trebski@xxxxxxxxxxxxxx<mailto:Tomasz.Trebski@xxxxxxxxxxxxxx>" <Tomasz.Trebski@xxxxxxxxxxxxxx<mailto:Tomasz.Trebski@xxxxxxxxxxxxxx>>
Date: Monday, November 16, 2015 at 11:58 PM
To: "monasca@xxxxxxxxxxxxxxxxxxx<mailto:monasca@xxxxxxxxxxxxxxxxxxx>" <monasca@xxxxxxxxxxxxxxxxxxx<mailto:monasca@xxxxxxxxxxxxxxxxxxx>>
Cc: "Zawisza.Hodzic@xxxxxxxxxxxxxx<mailto:Zawisza.Hodzic@xxxxxxxxxxxxxx>" <Zawisza.Hodzic@xxxxxxxxxxxxxx<mailto:Zawisza.Hodzic@xxxxxxxxxxxxxx>>
Subject: [Monasca] GPL in monasca-common

Hi there,

Recently, we (Fujitsu) started to use monasca-common (python implementation) and encountered two problems:


1.       monasca-common requires MySQL-Python library which is GPL2 license

a.       Apache2 (not only license for some of dependencies but also for monasca-common) is incompatible with GPL2

2.       monasca-common is, as the name suggests, common part for multiple components and for that reason

a.       it should not introduce hard dependencies to components which do not event use SQL related functionality

b.      it should not require specific SQL implementation


We would like to propose removing MySQL-Python library from the list of requirements. Currently we are investigating what would be the best course to take and achieve so that would be acceptable by all parties. We will come up with a proposal soon and appropriate change will be available at Gerrit.

Do you share our concerns?
Perhaps you have your own ideas to improve the situation here?

Best regards,
Tomasz and Fujitsu team


Tomasz Trębski

R&D Development Engineer / EST
Łódź GDC
[cid:image001.gif@01CF78FC.4ACD6460]
FUJITSU
Textorial Park, ul. Fabryczna 17
90-344 Łódź, Poland
Mob.: +48 789 231 312
E-mail: tomasz.trebski@xxxxxxxxxxxxxx<mailto:tomasz.trebski@xxxxxxxxxxxxxx>
Web: ts.fujitsu.com<http://ts.fujitsu.com/>
Company details: pl.ts.fujitsu.com/imprint<http://pl.ts.fujitsu.com/imprint.html>
This communication contains information that is confidential, proprietary in nature and/or privileged.  It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation.
Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission.