Hi David,

One of the libraries we were using pulled in a dependency which itself
depended on code licensed under the GPL.

The issue is discussed here:
https://issues.apache.org/jira/browse/LEGAL-362
And tracked in the Apache Airflow (incubating) project here:
https://issues.apache.org/jira/browse/AIRFLOW-1430

Bolke provided a PR against the upstream library to enable the use of an
alternative non-GPL dependency :
https://github.com/un33k/python-slugify/pull/53

The issue is now resolved in master, we just need to create a release with
which uses the latest releases of those upstream libraries.

Best regards,
Arthur

On Thu, Apr 5, 2018 at 9:37 AM, David Fisher <w...@apache.org> wrote:

> Hi -
>
> >  1. We are working through the last few remaining hurdles to graduate
> (e.g. cleaning up licenses)
>
> What is the licensing issue that is blocking graduation?
>
> Regards,
> Dave
>
> On 2018/03/29 18:05:14, Sid Anand <san...@apache.org> wrote:
> > And thx to the mentors (Hitesh and Jakob) for signing off so quickly!
> > -s
> >
> > On Thu, Mar 29, 2018 at 10:39 AM, Chris Riccomini <criccom...@apache.org
> >
> > wrote:
> >
> > > Thanks, Sid!
> > >
> > > On Wed, Mar 28, 2018 at 11:08 PM, Sid Anand <san...@apache.org> wrote:
> > >
> > > > FYI!
> > > > I filled out the podling report due in April.
> > > >
> > > > https://wiki.apache.org/incubator/April2018
> > > >
> > > > Mentors, please don't forget to sign-off!!
> > > >
> > > > -s
> > > >
> > > > On Wed, Mar 28, 2018 at 3:19 AM, <johndam...@apache.org> wrote:
> > > >
> > > > > Dear podling,
> > > > >
> > > > > This email was sent by an automated system on behalf of the Apache
> > > > > Incubator PMC. It is an initial reminder to give you plenty of
> time to
> > > > > prepare your quarterly board report.
> > > > >
> > > > > The board meeting is scheduled for Wed, 18 April 2018, 10:30 am
> PDT.
> > > > > The report for your podling will form a part of the Incubator PMC
> > > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > > > before the board meeting, to allow sufficient time for review and
> > > > > submission (Wed, April 04).
> > > > >
> > > > > Please submit your report with sufficient time to allow the
> Incubator
> > > > > PMC, and subsequently board members to review and digest. Again,
> the
> > > > > very latest you should submit your report is 2 weeks prior to the
> board
> > > > > meeting.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > The Apache Incubator PMC
> > > > >
> > > > > Submitting your Report
> > > > >
> > > > > ----------------------
> > > > >
> > > > > Your report should contain the following:
> > > > >
> > > > > *   Your project name
> > > > > *   A brief description of your project, which assumes no
> knowledge of
> > > > >     the project or necessarily of its field
> > > > > *   A list of the three most important issues to address in the
> move
> > > > >     towards graduation.
> > > > > *   Any issues that the Incubator PMC or ASF Board might wish/need
> to
> > > be
> > > > >     aware of
> > > > > *   How has the community developed since the last report
> > > > > *   How has the project developed since the last report.
> > > > > *   How does the podling rate their own maturity.
> > > > >
> > > > > This should be appended to the Incubator Wiki page at:
> > > > >
> > > > > https://wiki.apache.org/incubator/April2018
> > > > >
> > > > > Note: This is manually populated. You may need to wait a little
> before
> > > > > this page is created from a template.
> > > > >
> > > > > Mentors
> > > > > -------
> > > > >
> > > > > Mentors should review reports for their project(s) and sign them
> off on
> > > > > the Incubator wiki page. Signing off reports shows that you are
> > > > > following the project - projects that are not signed may raise
> alarms
> > > > > for the Incubator PMC.
> > > > >
> > > > > Incubator PMC
> > > > >
> > > >
> > >
> >
>

Reply via email to