Re: [IP CLEARANCE] Software grant for Ratis (incubating)

All, the Board approved Apache Zest (now Polygene) to go straight to TLP about 2 years ago. Part of the decision was the question; "What benefit will incubation have for the community?", and since we had exclusively Apache members on the initial project, operated with an ASF mindset before coming

Re: [IP CLEARANCE] Software grant for Ratis (incubating)

On 2/24/17, 4:40 PM, "Enis Söztutar" wrote: > >On a separate note, I wish there was a fast-track for these kind of >projects which can start internally in Apache without too much of a >hassle. Check the archives for "Straight to TLP" discussions. I thought it was possible

Re: [IP CLEARANCE] Software grant for Ratis (incubating)

> > > I'm pretty sure I brought this up on legal-discuss before. Its not > incorrect, but they are openly giving access to the code to the ASF. The > ASF can choose to ignore that license if they want. > All of the developers are coming from the Apache community (mainly Hadoop and related), so

Re: [CANCEL][VOTE] Release Apache Airflow 1.8.0

Good call Bolke. -s On Fri, Feb 24, 2017 at 12:30 AM, Bolke de Bruin wrote: > I am cancelling the vote fro Airflow 1.8.0 although 72h passed and we > received a conditional +1 (binding) from Jakob. This is because we feel the > license issues, packaging issues should be

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

Hi Jakob et al., Thanks for voting, based on your feedback we cancelled the vote to address the issues. The patch for this has been merged https://github.com/apache/incubator-airflow/pull/2098 (AIRFLOW-895). I am wondering how to deliver

[CANCEL][VOTE] Release Apache Airflow 1.8.0

I am cancelling the vote fro Airflow 1.8.0 although 72h passed and we received a conditional +1 (binding) from Jakob. This is because we feel the license issues, packaging issues should be addressed prior to release and that we found a blocker at the same time. We expect to raise a new vote