Just sharing Steve Winslow’s response with the discuss list. Best Regards, -kenny
> Begin forwarded message: > > From: Steve Winslow <swins...@linuxfoundation.org> > Subject: Re: FW: Why Lombok not allowed in LF? > Date: March 7, 2018 at 8:14:31 AM PST > To: Vitaliy Emporopulo <vitaliy.emporop...@amdocs.com> > Cc: Phil Robb <pr...@linuxfoundation.org>, Gildas Lanilis > <gildas.lani...@huawei.com>, Kenny Paul <kp...@linuxfoundation.org> > > (+Gildas and Kenny) > > Hello Vitaly, > > Thank you for reaching out on this. Some versions of Lombok being used in > ONAP repositories are being flagged as a result of our license scans for > dependencies. > > Although Lombok as a project has declared itself to be an MIT-licensed > project, from scans we have found that some versions of Lombok contain at > least one source code file stating that it is licensed under the GPL. This > file appears to have been replaced by version 1.16.8 of Lombok, so updating > to that version or later should address this. > > Just to clarify, the LF does not impose restrictions on which open source > licenses may be used. Under the ONAP charter's IP policy, the ONAP TSC has > the ability to approve exceptions to the project's Apache-2.0 license policy. > So they may approve components under alternate licenses (there are many other > licenses in ONAP's dependencies). The reason Lombok and certain other ones > are flagged is because GPL-style licenses may be harder for the TSC to > approve for use in an Apache-licensed project. > > I hope this is helpful. Please feel free to let me know if you have other > questions. > > Best, > Steve Winslow > > On Wed, Mar 7, 2018 at 5:34 AM, Vitaliy Emporopulo > <vitaliy.emporop...@amdocs.com <mailto:vitaliy.emporop...@amdocs.com>> wrote: > Hi, > > > > I am a technical architect with SDC at Amdocs. > > > > Could you please help me understand what is wrong with Lombok licensing? It > is released under MIT license, and its Java artifact does not include and > does not depend on any external libraries. Moreover, in Lombok Git > repository, I could not find any reference to other external materials that > might have a problematic license. > > > > Best regards, > > Vitaliy Emporopulo > > > > From: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Vitaliy Emporopulo > Sent: Wednesday, March 7, 2018 12:00 > To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> > Subject: [onap-discuss] Why Lombok not allowed in LF? > > > > Hello, > > > > Could someone please shed some light on why Lombok > (https://projectlombok.org/ <https://projectlombok.org/>) is not allowed in > LF for licensing reasons? > > > > Where can I find guidelines or tools to help me filter out unsuitable > libraries? > > > > Thanks in advance, > > Vitaliy Emporopulo > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at https://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> > > > -- > Steve Winslow > Director of Strategic Programs > The Linux Foundation > Cell: +1.202.641.3047 Skype: 12026413047 > swins...@linuxfoundation.org <mailto:swins...@linuxfoundation.org>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
