Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

+1, non-binding Awesome! (And Do i need to say finally? ;-)) B. Verstuurd vanaf mijn iPad > Op 19 aug. 2019 om 18:05 heeft Alan Gates het volgende > geschreven: > > Forwarding my +1 from the dev list. I checked the LICENSE, NOTICE, and > DISCLAIMER files, as well as looking over the

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

Hi, - okay :-) I'm a bit confused here but fine - they are not? I dont follow? How would you suggest making them binary then? And yes I agree there are more pressing issues. The roboto fonts are in fact ALv2 (https://github.com/apache/fineract-site/tree/master/font/roboto ), the glyphs fonts

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

Hi Justin, Can I assume that we are doing the right thing now for the CC-BY 4.0 in NOTICE and LICENSE. The license does ask for “something beyond” and referring to it in NOTICE seems to me a “reasonable manner”. On the GeoJSON, these are actually compiled from the shape files that Diva GIS makes

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

Hi Justin The CC-BY 4.0 is included in both NOTICE and LICENSE due to " Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

Also on [5] and [6] the license location is here https://github.com/syntagmatic/parallel-coordinates which includes divgrid.js in examples/lib as part of the package and from the same author. Cheers Bolke Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 15:14 heeft Bolke de Bruin

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

licenses are mentioned in LICENSE.txt Other items I leave up to the release manager to answer. Bolke. Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 10:03 heeft Bolke de Bruin het > volgende geschreven: > > Hi Justin, > > The GIS data is under CC BY 4.0 see here: > > h

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

Hi Justin, The GIS data is under CC BY 4.0 see here: https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 Hence the reference to this license. According to https://apache.org/legal/resolved.html it is fine to include this in binary form

Re: [VOTE] Graduate Apache Airflow to TLP

199 sounds pretty cool too :-) > On 6 Dec 2018, at 13:39, Bertrand Delacretaz > wrote: > > On Thu, Dec 6, 2018 at 11:39 AM Mark Thomas wrote: >> ...there is a resolution to >> terminate a project on this month's board agenda so you'll be (if >> nothing else changes) the 199th active

Re: [VOTE] Graduate Apache Airflow to TLP

Oh nice :-) something for the press release I guess  Op do 6 dec. 2018 04:20 schreef Justin Mclean HI, > > If you do graduate (and no project retires) you'll become the 200th active > project at the ASF :-) > > Thanks, > Justin >

Re: [VOTE] Graduate Apache Airflow to TLP

Apache Airflow" be > > and hereby is created, the person holding such office to > > serve at the direction of the Board of Directors as the chair > > of the Apache Airflow Project, and to have primary responsibility > > for management of the projects within the scop

[RESULT][VOTE] Release Airflow 1.10.0

message: > From: Bolke de Bruin > Date: 20 August 2018 at 19:56:23 CEST > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4) > > Appreciated Hitesh. Do you know how to add headers to .MD files? There seems > to be no tec

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

tesh > >> On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin wrote: >> >> Sorry Willem that should be of course. Apologies. >> >> Sent from my iPhone >> >>> On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: >>> >>> Hi William >>

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

Sorry Willem that should be of course. Apologies. Sent from my iPhone > On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: > > Hi William > > You seem to be missing a "4" at the end of the URL? Ah it seems that my > original email had a quirk. Would you mind

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

Jiang wrote: > > Hi, > > The Git tag cannot be accessed. I can only get the 404 error there. > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > >> On Sun, Au

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

Hi, We are 7 days into the vote and still lacking 2. Please help in reviewing it's much appreciated! Bolke Sent from my iPhone > On 15 Aug 2018, at 20:22, Bolke de Bruin wrote: > > Friendly ping. We are missing 2 votes. > > Cheers > Bolke > > Sent from my iPh

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

Friendly ping. We are missing 2 votes. Cheers Bolke Sent from my iPhone > On 14 Aug 2018, at 11:00, Justin Mclean wrote: > > Hi, > > +1 (binding) thanks for fixing up the GPL dependancy issue. > > I checked: > - incubating in name > - signatures and hashes good > - DISCLAIMER exists > - No

Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)

27a-4e12-96f1-b1767f162...@gmail.com%3E> Bolke > On 12 Aug 2018, at 14:25, Bolke de Bruin wrote: > > Hello Incubator PMC’ers, > > The Apache Airflow community has voted and approved the proposal to release > Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Cand

[VOTE] Release Airflow 1.10.0 (new vote based on rc4)

Hello Incubator PMC’ers, The Apache Airflow community has voted and approved the proposal to release Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 4. We now kindly request the Incubator PMC members to review and vote on this incubator release. Airflow is a platform to

[REVOKE][VOTE] Release Airflow 1.10.0

FYI, Revoking the vote to address (mostly) license issues. Cheers Bolke > Begin forwarded message: > > From: Bolke de Bruin > Subject: Re: [VOTE] Release Airflow 1.10.0 > Date: 28 July 2018 at 12:52:28 CEST > To: general@incubator.apache.org > > Hi Justin, >

Re: [VOTE] Release Airflow 1.10.0

Hi Justin, Thanks for the feedback. The holiday period seems to make gathering +1s a bit slow. We are going to address the issues you and Sebb mentioned and put it up for a revote at the PMC, which should be relatively quick as they don't consider functional changes. For the potential GPL

Re: [VOTE] Release Airflow 1.10.0

Friendly ping @justin Verstuurd vanaf mijn iPad > Op 21 jul. 2018 om 20:33 heeft Bolke de Bruin het > volgende geschreven: > > Hi Justin, > > Thank you for the thorough review! I have created AIRFLOW-2779 to track most > of the issues you have raised. > >

Re: [VOTE] Release Airflow 1.10.0

Hi Justin, Thank you for the thorough review! I have created AIRFLOW-2779 to track most of the issues you have raised. On the GPL dependency you mentioned. We are not distributing GPL sources, not in source or in binary form. This has never been the case. In the third degree there

Re: [VOTE] Release Airflow 1.10.0

It is just a convenience package and not part of the vote, but that argument seems mood. I will therefore remove the binary package. B. Verstuurd vanaf mijn iPad > Op 20 jul. 2018 om 16:58 heeft Bertrand Delacretaz > het volgende geschreven: > >> Le ven. 20 juil. 2018 à 16:15, sebb a écrit

Re: [VOTE] Release Airflow 1.10.0

hreven: > >> On 19 July 2018 at 11:16, Bolke de Bruin wrote: >> Hi Sebb, >> >> Gotcha. The vote considers the source package, but arguably the binary >> package is pretty close. The binary package does contain a LICENSE and >> NOTICE file, it misses the spe

Re: [VOTE] Release Airflow 1.10.0

19 Jul 2018, at 10:33, sebb wrote: > > On 19 July 2018 at 09:15, Bolke de Bruin wrote: >> Hi Yang, >> >> The source package is the one was voted upon with the PMC and is under vote >> now. >> The binary package is just a convenience package and not the arte

Re: [VOTE] Release Airflow 1.10.0

> Is te kerberos_auth.py from the flask-keberos or is it wrote by the airflow > dev team? If it's from the flask-keberos project, then the ASF header > should not be there. If it's developed by airflow devs, then it should not > be mentioned in the LICENSE file. > > > > On Thu, J

Re: [VOTE] Release Airflow 1.10.0

kage. > The licenses folder is missing and I can't find files relating to > elasticmock or flask-kerberos. > > On Thu, Jul 19, 2018 at 1:28 PM Bolke de Bruin wrote: > >> Hi Yang, >> >> Thanks for reviewing. To your points. >> >> 1. I verified the n

Re: [VOTE] Release Airflow 1.10.0

aries that are not bundled in the source release but >> are listed in the LICENSE file, e.g. ElasticMock, flask-kerberos etc. The >> LICENSE file should only contain what's actually bundled. >> 3. It's better to provide the version in the LICENSE for third parties >> because the

[VOTE] Release Airflow 1.10.0

Hello Incubator PMC’ers, The Apache Airflow community has voted and approved the proposal to release Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 2. We now kindly request the Incubator PMC members to review and vote on this incubator release. Airflow is a platform to

Re: [VOTE] Accept Druid into the Apache Incubator

+1 (non-binding) > On 26 Feb 2018, at 20:53, Ashutosh Chauhan wrote: > > +1 > > On Sun, Feb 25, 2018 at 11:51 PM, Hao Chen wrote: > >> +1 (non-binding) >> >> Hao Chen >> >> *PMC & Committer, Apache Eagle* >> >> On Mon, Feb 26, 2018 at 3:02 PM,

Re: [VOTE] Release Airflow 1.9.0

@sebb, @henk are you now able to vote +1 or is there anything else we need to pickup before? Cheers Bolke > On 20 Dec 2017, at 15:29, sebb wrote: > > On 19 December 2017 at 18:42, Chris Riccomini > wrote: >>> Please

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

Also the author replied and confirmed a BSD license: https://github.com/novus/nvd3/issues/2064#issuecomment-313718380 Kind regards Bolke Sent from my iPhone > On 7 Jul 2017, at 03:17, Justin Mclean wrote: > > Hi, > >> The patch that contains “bullet.js” was

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

tosca/0.1.0-incubating/ > > > Sorry if this wasn't relevant for your scenario. > > > > > >> On Thu, Jul 6, 2017 at 5:00 PM, Bolke de Bruin <bdbr...@gmail.com> wrote: >> >> Protovis became d3, which is BSD licensed. D3’s examples contain the same &g

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

Protovis became d3, which is BSD licensed. D3’s examples contain the same code. The author (Mike Bostock) is the same in both cases. I have just send him an email, I hope he responds. Cheers Bolke > On 6 Jul 2017, at 15:08, Justin Mclean wrote: > > HI, > >> [20]

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

Hi Justin, That’s for the whole project nvd3, which was then also dual licensed APL2. Next to that this file has existed only for two months in this repository: Bolkes-MacBook-Pro:nvd3 bolke$ git log --all --full-history -- GPL-LICENSE.v3.txt commit 8e52a5743e843015495da495f83153ac5552edf3

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

E. Should I include this analysis anywhere? Cheers Bolke > On 6 Jul 2017, at 14:31, Bolke de Bruin <bdbr...@gmail.com> wrote: > > Hi Justin, > > [20] “nv.d3.js” originates from http://nvd3.org <http://nvd3.org/> and its > license states it is Apache License 2, &

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

Hi Justin, [20] “nv.d3.js” originates from http://nvd3.org and its license states it is Apache License 2, https://github.com/novus/nvd3/blob/master/LICENSE.md . And as far as I understand it it should not need to be

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

The situation isn't that bad. It is due to the fact this is a "sdist" (not a bdist). Our git repo does contain the licenses and does pass RAT. I'll discuss with Max how we will fix this. Probably we create a real "source tarball" with build instructions to create a "sdist". Let's see. I'm just

Re: Airflow voting on release artifacts

" (instead of "mvn verify") then you need to clean it out > afterwards. There is no easy command for it in mvn, although you can > usually just rm -rf the corresponding folder in .m2/repository. > > > > On 1 May 2017 10:00 pm, "Bolke de Bruin" <

Re: Airflow voting on release artifacts

> On 1 May 2017, at 22:39, Alex Harui <aha...@adobe.com> wrote: > > > > On 5/1/17, 11:44 AM, "Bolke de Bruin" <bdbr...@gmail.com > <mailto:bdbr...@gmail.com>> wrote: > >> >>> On 1 May 2017, at 17:36, Alex Harui <aha...@ad

Re: Airflow voting on release artifacts

> On 1 May 2017, at 17:36, Alex Harui wrote: > > > > On 5/1/17, 7:44 AM, "Hitesh Shah" wrote: > >> Hi Justin, >> >> Currently, the podling has been modifying the contents and hence this >> discussion. > > I agree with Justin and others that

Re: Airflow voting on release artifacts

be.com> wrote: > > > > On 4/25/17, 1:43 AM, "Bolke de Bruin" <bdbr...@gmail.com > <mailto:bdbr...@gmail.com>> wrote: > >> Hi Bertrand, >> >>> On 25 Apr 2017, at 09:04, Bertrand Delacretaz >>> <bdelacre...@codeconsult.

Re: Airflow voting on release artifacts

> rename can happen. IF the RC doesn't happen, you can rebuild with new > content and same internal version. > > Cheers > Niclas > > On Tue, Apr 25, 2017 at 4:43 PM, Bolke de Bruin <bdbr...@gmail.com> wrote: > >> Hi Bertrand, >> >>> On

Re: Airflow voting on release artifacts

Hi Bertrand, > On 25 Apr 2017, at 09:04, Bertrand Delacretaz > wrote: > > Hi, > > On Mon, Apr 24, 2017 at 10:18 PM, Chris Riccomini > wrote: >> ...Hitesh recently raised the issue that the artifact that passes the vote >> MUST be the one

Re: Airflow voting on release artifacts

Hi John, Typically one handles a “release candidate” equal to a release, except for the fact that it hasn’t been fully tested and reviewed yet. In case everyone (all entities) is satisfied with the RC it is then just rebranded to Release. Unfortunately, in the python ecosystem the version

[RESULT][VOTE] Release Apache Airflow 1.8.0 (incubating)

Hi all, After being opened for over more than 72 hours, the vote for releasing Apache Airflow 1.8.0-incubating passed [1] with 4 binding +1s, and no 0 or -1. * Binding votes +1s: * Chris Douglas Jakob Homann Jitendra Pandey John D. Ament Thanks to everyone who reviewed, we really appreciate

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

! Bolke > On 16 Mar 2017, at 18:12, John D. Ament <johndam...@apache.org> wrote: > > Looks good. Here's my +1 > > As I've said before, the package name doesn't block the release. If you > can create a JIRA to track it, that would be great. > > On Thu, Mar 16, 2017 a

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

just airflow, and somehow mark the old airflow release as deprecated? > either way won't block this release. > > John > > On Thu, Mar 16, 2017 at 7:45 PM Bolke de Bruin <bdbr...@gmail.com > <mailto:bdbr...@gmail.com>> wrote: > >> Hey John, >>

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

rce release, is the naming of the source release > critical for consumers? Or do you leverage some kind of package manager > that understands it based on the archive name? Either way, the blocker is > the DISCLAIMER, not this. > > John > > On Thu, Mar 16, 2017 at 7:32 PM Bolke de

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

t > Jakob noted, the current artifact naming must be fixed (its a branding > issue from my POV). It should be apache-airflow (or something like that) > not simply airflow. > > John > > On Thu, Mar 16, 2017 at 12:40 PM Bolke de Bruin <bdbr...@gmail.com > <mailto:bdb

[VOTE] Release Apache Airflow 1.8.0 (incubating)

Hello Incubator PMC’ers, The Apache Airflow community has voted and approved the proposal to release Apache Airflow 1.8.0 (incubating) based on 1.8.0 Release Candidate 5. We now kindly request the Incubator PMC members to review and vote on this incubator release. If the vote is successful we

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

eb 22, 2017 at 2:38 PM, Chris Riccomini <criccom...@apache.org> >> wrote: >> >>> +1 non-binding >>> >>> On Mon, Feb 20, 2017 at 11:50 PM, Bolke de Bruin <bdbr...@gmail.com> >>> wrote: >>> >>>> Hello Incubator PMC’ers, >>

[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

Re: [VOTE] Release Apache Juneau 6.1.0-incubating-RC2

Jakob Are you voting on Juneau or Airflow? I’m assuming Airflow here due to the remarks. Can you respond to that thread so I can respond there? Bolke > On 23 Feb 2017, at 21:17, Jakob Homan wrote: > > * md5 and sig looks good > * Spot check on licensing looks good > * The

[VOTE] Release Apache Airflow 1.8.0 (incubating)

Hello Incubator PMC’ers, The Apache Airflow community has voted and approved the proposal to release Apache Airflow 1.8.0 (incubating) based on 1.8.0 Release Candidate 4. We now kindly request the Incubator PMC members to review and vote on this incubator release. If the vote is successful we