Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-05-17 Thread Ash Berlin-Taylor
Sorry to resurrect an old vote thread, but to follow up on this:

In Airflow 2.1 we have removed _our_ cat-X core dep, but that doesn't help the 
Liminal project as they need the Docker and Kubernetes client libraries for 
their core.

I have opened https://github.com/psf/requests/pull/5797 and Jarek has done a 
lot of the testing work, and it looks likely that the "requests" maintainers 
will accept this PR.

And the other LGPL dep from the python Kubernetes client is in the process of 
changing to Apache2 license 
https://github.com/websocket-client/websocket-client/issues/665

On 2021/04/21 14:55:14, Ash Berlin-Taylor  wrote: 
> Hi Aviem,
> 
> Hi everyone, Airflow PMC here.
> 
> First off, eek. Not sure how this happened, it's been like this for a while.
> 
> I agree -- we could possibly fix the direct dependency on requests/chardet in 
> Airflow, but as you have already discovered there are many more python 
> libraries that depend upon requests - docker and kubernetes being the two 
> that are hard to work around!.
> 
> (Kubernetes has a _direct_ dep on a lgpl'd dep too) 
> 
> I'm writing a post to le...@apache.org, as _my_ reading is that depending 
> upon LGPLd library at runtime only, but not shipping it is "work that uses 
> the Library", and as per clause 5 of the LGPL 2.1 license should be fine 
> https://opensource.org/licenses/LGPL-2.1
> 
> > A program that contains no derivative of any portion of the Library, but is 
> > designed to work with the Library by being compiled or linked with it, is 
> > called a "work that uses the Library". Such a work, in isolation, is not a 
> > derivative work of the Library, and therefore falls outside the scope of 
> > this License.
> 
> (There are a few caveats to this, so be careful about what else you might do 
> with the code, such as creating)
> 
> We'll see what Legal say about this. 
> 
> Thanks,
> Ash
> 
> On 2021/04/21 10:39:58, Aviem Zur  wrote: 
> > We can try to reach out. It looks like `chardet` can't change their license
> > and `requests` have a won't fix / no time to fix attitude towards it.
> > 
> > Meanwhile what do we do regarding releases of our artifacts?
> > I don't see how we can develop a python project without having an indirect
> > dependency on `requests` package as detailed above.
> > 
> > On Wed, Apr 21, 2021 at 12:51 PM Justin Mclean 
> > wrote:
> > 
> > > Hi,
> > >
> > > Sorry I’m not sure what to suggest. Normally I’d say contact the project
> > > and ask if they would be willing to distribute the library under another
> > > license e.g. dual license it under LGPL and ALv2 but this seem unlikely
> > > [1]. I guess it wouldn't hurt to ask again.
> > >
> > > Kind Regards,
> > > Justin
> > >
> > >
> > > 1. https://github.com/chardet/chardet/issues/36
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> > 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Ash Berlin-Taylor
Hi Aviem,

Hi everyone, Airflow PMC here.

First off, eek. Not sure how this happened, it's been like this for a while.

I agree -- we could possibly fix the direct dependency on requests/chardet in 
Airflow, but as you have already discovered there are many more python 
libraries that depend upon requests - docker and kubernetes being the two that 
are hard to work around!.

(Kubernetes has a _direct_ dep on a lgpl'd dep too) 

I'm writing a post to le...@apache.org, as _my_ reading is that depending upon 
LGPLd library at runtime only, but not shipping it is "work that uses the 
Library", and as per clause 5 of the LGPL 2.1 license should be fine 
https://opensource.org/licenses/LGPL-2.1

> A program that contains no derivative of any portion of the Library, but is 
> designed to work with the Library by being compiled or linked with it, is 
> called a "work that uses the Library". Such a work, in isolation, is not a 
> derivative work of the Library, and therefore falls outside the scope of this 
> License.

(There are a few caveats to this, so be careful about what else you might do 
with the code, such as creating)

We'll see what Legal say about this. 

Thanks,
Ash

On 2021/04/21 10:39:58, Aviem Zur  wrote: 
> We can try to reach out. It looks like `chardet` can't change their license
> and `requests` have a won't fix / no time to fix attitude towards it.
> 
> Meanwhile what do we do regarding releases of our artifacts?
> I don't see how we can develop a python project without having an indirect
> dependency on `requests` package as detailed above.
> 
> On Wed, Apr 21, 2021 at 12:51 PM Justin Mclean 
> wrote:
> 
> > Hi,
> >
> > Sorry I’m not sure what to suggest. Normally I’d say contact the project
> > and ask if they would be willing to distribute the library under another
> > license e.g. dual license it under LGPL and ALv2 but this seem unlikely
> > [1]. I guess it wouldn't hurt to ask again.
> >
> > Kind Regards,
> > Justin
> >
> >
> > 1. https://github.com/chardet/chardet/issues/36
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [EXTERNAL] Graduated from the Incubator but Releases remain in Incubator Dist SVN

2019-03-15 Thread Ash Berlin-Taylor
Hi Dave,

Why is it a problem to keep those official release artefacts available at that 
URL that they were first published at? Yes Airflow has now graduated, but by 
removing those URLs anyone who want's to view older releases will get 404s. 

-ash

> On 15 Mar 2019, at 13:45, Kaxil Naik  wrote:
> 
> Hi Dave,
> 
> I have removed *Airflow *from incubator repo.
> 
> Regards,
> Kaxil
> 
> On Fri, Mar 15, 2019 at 2:26 AM takako shimamoto 
> wrote:
> 
>> Hi Dave,
>> 
>> I have removed predictionio from incubator repo.
>> Thanks!
>> 
>> On Fri, Mar 15, 2019 at 3:15 AM Gelinas, Derek
>>  wrote:
>>> 
>>> Dave,
>>> 
>>> I have removed the releases.  Thank you!
>>> 
>>> Derek
>>> 
>>> On 3/14/19, 2:01 PM, "Dave Fisher"  wrote:
>>> 
>>>Hi -
>>> 
>>>You still have releases in the Incubator’s area of SVN -
>> https://dist.apache.org/repos/dist/release/incubator/ <
>> https://dist.apache.org/repos/dist/release/incubator/>
>>> 
>>>Please plan to move or remove these soon.
>>> 
>>>Thank you!
>>> 
>>>Regards,
>>>Dave
>>> 
>> 
> 
> 
> -- 
> *Kaxil Naik*
> *Big Data Consultant *@ *Data Reply UK*
> *Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
> Developer
> *LinkedIn*: https://www.linkedin.com/in/kaxil


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[RESULT][VOTE] Release Airflow 1.10.1 (incubating)

2018-11-21 Thread Ash Berlin-Taylor
The vote to release Airflow 1.10.1-incubating, having been open for 3
days is now closed.
 
There were three binding +1s and no -1 votes.

+1 (binding):
Hitesh Shah
Jakob Homan
Justin Mclean
 
The release is approved.
 
Thanks to all those who voted.
 
Cheers,
Ash

> On 21 Nov 2018, at 04:44, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE and NOTICE correct
> - No unexpected binary files
> - All ASF source code has ASF headers
> 
> I don’t have the setup to test if it compiles.
> 
> One minor thing I’d remove the "Apache Airflow contains subcomponents …” and 
> "See the LICENSE file …” from teh NOTICE file as I don’t think they are 
> needed.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [VOTE] Release Airflow 1.10.1 (incubating)

2018-11-19 Thread Ash Berlin-Taylor
Done, (and updated our project scripts to not create them anymore.)

Thanks,
Ash

> On 19 Nov 2018, at 07:32, Henk P. Penning  wrote:
> 
> On Sun, 18 Nov 2018, Ash Berlin-Taylor wrote:
> 
>> Date: Sun, 18 Nov 2018 22:06:42 +0100
>> From: Ash Berlin-Taylor 
>> To: general@incubator.apache.org
>> Subject: [VOTE] Release Airflow 1.10.1 (incubating)
>> Hello Incubator PMC’ers,
>> 
>> The Apache Airflow community has voted and approved the proposal to release
>> Apache Airflow 1.10.1 (incubating) based on 1.10.1 Release Candidate 2. We
>> now kindly request the Incubator PMC members to review and vote on this
>> incubator release.
> 
>> https://dist.apache.org/repos/dist/dev/incubator/airflow
> 
>  .md5 checksum files should not be published ; please remove.
>  The vote may continue.
> 
>  Regards,
> 
>  HPP
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[VOTE] Release Airflow 1.10.1 (incubating)

2018-11-18 Thread Ash Berlin-Taylor
Hello Incubator PMC’ers,
 
The Apache Airflow community has voted and approved the proposal to release
Apache Airflow 1.10.1 (incubating) based on 1.10.1 Release Candidate 2. We
now kindly request the Incubator PMC members to review and vote on this
incubator release.
 
Airflow is a platform to programmatically author, schedule, and monitor
workflows. Use Airflow to author workflows as directed acyclic graphs
(DAGs) of tasks. The airflow scheduler executes your tasks on an array of
workers while following the specified dependencies. Rich command line
utilities make performing complex surgeries on DAGs a snap. The rich user
interface makes it easy to visualize pipelines running in production,
monitor progress, and troubleshoot issues when needed. When workflows are
defined as code, they become more maintainable, versionable, testable, and
collaborative.

This release is a point release on 1.10.1 addressing some quirks found in 
1.10.0 and dealing with new versions of dependencies changing behaviour 
since we 1.10.0 was released.

We also fixed the minor nits pointed out in 1.10.0 and have added license
header to the documentation files, and specify the third party dependencies
version we based our license statement about.
 
After a successful IPMC vote Artifacts will be available at:
 
https://dist.apache.org/repos/dist/dev/incubator/airflow
 
Public keys are available at:
 
https://dist.apache.org/repos/dist/release/incubator/airflow
 
apache-airflow-1.10.1rc2+incubating-source.tar.gz


is a source release that comes with INSTALL instructions.

Along with it, for convenience, find the binary Python "sdist" as
apache-airflow-1.10.1rc2+incubating-bin.tar.gz


Vote thread:
https://lists.apache.org/thread.html/df6389b9f39ec872e1eb28a39acc889511cf7d436786208abadd3f30@%3Cdev.airflow.apache.org%3E
 

Git tag:
https://github.com/apache/incubator-airflow/releases/tag/1.10.1rc2
 
The vote will be open for at least 72 hours and until the necessary
number of votes are reached.
 
Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).
 
* Here is my +1 (non-binding) *
 
Cheers,
Ash

* WARNING: Due to licensing requirements you will need to set  
SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when installing or 
upgrading. We will try to remove this requirement for the  next major release.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org