Apache Toree had a similar issue, and we have discussed this in
legal-discuss, and here is the feedback from Jim, VP of Legal

http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201602.mbox/%3C2A8B931C-1AD6-4230-B2DE-0B33361B3A2B%40jaguNET.com%3E



On Sat, Feb 13, 2016 at 8:46 PM, Greg Stein <gst...@gmail.com> wrote:

> Speaking as an IPMC Member, and a Mynewt Mentor … yes, this is fine with a
> disclaimer in the release notes. The Incubator process is about tracking
> these down, and getting them fixed. Incubation releases are not expected to
> be *fully* conformant to all ASF policies, especially if there is a known
> path to remedy the issue. For example, I'm pretty sure we've seen
> Incubation releases still dependent upon Hibernate, until the podling gets
> the work down to make that dependency optional.
>
> IMO, it is more important to get the podling turning the crank of a
> release, to learn these things, and prep the future release processes, than
> to clear out that (disclosed!) dependency upon an LGPL library.
>
> Cheers,
> -g
>
>
> On Sat, Feb 13, 2016 at 9:17 PM, Justin Mclean <justinmcl...@me.com>
> wrote:
>
> > Hi,
> >
> > Apache Mynewt [1] is moving towards making it’s first release.
> >
> > We found that one of the libraries we depend on, viper which is MIT
> > licensed [2], in turn depends on a library that is LGPLv3 licensed
> > (go-yaml) [3].
> >
> > It is intended to replace the viper/yaml libraries with ones comparable
> > with the Apache license and/or enquire if we can obtain the yaml code
> under
> > a different license. So this will be fixed in a future incubating
> release.
> >
> > Would it be acceptable to make an incubating release with this LGPL
> > dependancy intact? No LGPL code would be contained in the release.
> >
> > Thanks,
> > Justin
> >
> > 1. http://mynewt.incubator.apache.org
> > 2. https://github.com/spf13/viper/blob/master/LICENSE
> > 3. https://github.com/go-yaml/yaml/blob/v2/LICENSE
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Reply via email to