Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <5690263C-A3A4-402E-BC78-B43EB9365277@gmail.com>
References: <1957A4FA-5D60-426A-A4EE-4D37A3D9471D@blue-yonder.com> <5690263C-A3A4-402E-BC78-B43EB9365277@gmail.com>
From: Maxime Beauchemin <maximebeauchemin@gmail.com>
Date: Thu, 3 Aug 2017 16:36:24 -0700
Message-ID: <CAHEEp7XzjWPHY8YDVOCgrwjF3eu8x0cSEMc=cyfc4pOTEN9+_A@mail.gmail.com>
Subject: Re: Resolving the GPL Licensing issues with Unidecode
To: dev@airflow.incubator.apache.org
Content-Type: multipart/alternative; boundary="f403045e745247ba9c0555e1d96e"
archived-at: Thu, 03 Aug 2017 23:36:44 -0000

--f403045e745247ba9c0555e1d96e
Content-Type: text/plain; charset="UTF-8"

Hey, how does this affect the current release(s) taking place?

Max

On Thu, Aug 3, 2017 at 8:57 AM, Bolke de Bruin <bdbruin@gmail.com> wrote:

> Oh that is a nice catch. Obviously option 3 is the easiest to get this
> resolved so it might be worth a try. This could be done by stating that the
> Apache Foundation and its lawyers disagree with the assessment the author
> makes. I even think, but ianal, that python-slugify is not compliant (you
> would need a LGPL version of unidecode for that).
>
> Another option is to convince the author of unidecode to release under a
> dual license as was the case with the original Perl module (perl artistic
> and gpl). This might be difficult though: https://github.com/avian2/
> unidecode/issues/9
>
> Probably the best option is 1. We should move to a webpack/yarn/npm setup
> anyway. However this might be a bigger effort than you are up to.
>
> Bolke
>
> Sent from my iPhone
>
> > On 3 Aug 2017, at 13:48, Heistermann, Till <
> Till.Heistermann@blue-yonder.com> wrote:
> >
> > Hey all,
> >
> > At Blue Yonder, we would love to upgrade to Airflow 1.8+,
> > but licensing issues with the dependencies currently prevent us from
> doing so.
> > (see https://issues.apache.org/jira/browse/AIRFLOW-1430 )
> >
> > To sum it up, airflow 1.8+ pulls in the GPL-Licensed dependency
> `Unidecode`
> > via `python-slugify` and `python-nvd3`.
> >
> > We would like to help resolving this.
> >
> > We see three possible options here:
> >
> > 1) Replace `python-nvd3` in airflow
> >
> > 2) Replace the slugify implementation used in `python-nvd3`
> >
> > 3) Replace the Unicode tables used in `python-slugify` with a
> licence-compatible version (e.g. https://github.com/kmike/text-unidecode).
> > The main developer of `python-slugify` did not seem to be open to this
> in back in 2014 though, but it might be worth a new try (see
> https://github.com/un33k/python-slugify/issues/7)
> >
> > What is your opinion about this?
> > Which approach would be the most feasible?
> > Are you aware of libraries that could act as drop-in replacements?
> >
> > Cheers, Till
> >
> >
> >
> >
> >
>

--f403045e745247ba9c0555e1d96e--