commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: [DISCUSS] Brining clirr to the ASF?
Date Tue, 14 Jun 2016 18:31:28 GMT
Thank you for the clarification, Dennis!

Dennis E. Hamilton <dennis.hamilton@acm.org> schrieb am Di., 14. Juni 2016
um 19:57:

> [Chiming in lest those on the Commons PMC who know the answer don't and
> leave the LGPL question dangling.]
>
> > -----Original Message-----
> > From: Gary Gregory [mailto:garydgregory@gmail.com]
> > Sent: Monday, June 13, 2016 23:23
> > To: Commons Developers List <dev@commons.apache.org>
> > Subject: Re: [DISCUSS] Brining clirr to the ASF?
> >
> > On Mon, Jun 13, 2016 at 11:19 PM, Benedikt Ritter <britter@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > as Jochen has pointed out, Clirr seems to be unmaintained. However we
> > build
> > > a good part of our release strategy upon clirr. So I wonder whether we
> > > should foster bringing clirr to the ASF (for example by going through
> > > incubation). We're probably not the only ASF project using Clirr.
> > >
> >
> > +1. Can we bring in code that's under GNU Lesser General Public and make
> > it
> > ASL 2?
> [orcmid]
>
> Short answer: No.
>
> Does not the exception for build dependencies apply for clirr though, so
> long as it is not in releases and in the project repository?
>
> TL;DR Longer answer, to bring clirr into the project.  If those who hold
> copyright in the Clirr code agree to license it to the ASF under terms that
> empower the ASF to provide a different license, this would work.  It is not
> otherwise possible for parties who are not the original copyright holders
> or so-empowered licensees to alter the license on anything (and that
> applies to ASLv2-licensed works too).  Generally, one can't even get *into*
> incubation without a cure in hand before the subject code is imported for
> IP cleanup.  Please consult
> <http://apache.org/legal/resolved.html>,
> <http://incubator.apache.org/guides/mentor.html#initial-ip-clearance>,
> and <http://www.apache.org/legal/src-headers.html> for related
> considerations.
>
> And then there are the dependencies of clirr to pay attention to.
>
> >
> > Could fit under a new Commons Build or Clirr component since it is a
> > "common" build requirement.
> >
> > Gary
> >
> >
> > > Benedikt
> > >
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition
> > <http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message