Re: Upcoming Podling report, due July 1st

gt; >> > Please review and share any thoughts before June 1. >> > -s >> > >> > On Wed, May 25, 2016 at 7:09 PM, siddharth anand <r39...@gmail.com> >> wrote: >> > >> >> I can. >> >> >> >> Sent from Sid's iP

Upcoming Podling report, due July 1st

Just a reminder that the second Podling report is imminent. After three monthly reports (this is our second), we move to quarterly reporting. Anyone want to volunteer? http://wiki.apache.org/incubator/June2016 -Jakob

Re: S3 connection

Hey Tyrone- I just set this up on 1.7.1.2 and found the documentation confusing too. Been meaning to improve the documentation. To get S3 logging configured I: (a) Set up an S3Connection (let's call it foo) with only the extra param set to the following json: { "s3_config_file":

Re: [DISCUSS] Review-then-commit (RTC) vs Commit-then-review (CTR)

t; given our different daily work schedules. > > -s > > On Thu, May 19, 2016 at 5:56 PM, Jakob Homan <jgho...@gmail.com> wrote: > >> On 18 May 2016 at 16:06, siddharth anand <r39...@gmail.com> wrote: >> > Is there an automation we can use to ensure/enforce

Re: [DISCUSS] Review-then-commit (RTC) vs Commit-then-review (CTR)

Hey- The consensus approval link is referring to votes (e.g. releases, new committers, new PMCers, etc) rather than code changes. A single +1 is standard for code changes, as Chris describes. However, projects are welcome to provide more fine-grained requirements as well. For example, Hadoop

Re: Airflow Developers Meeting - 08/03 Notes

ASF provides per-projects blog infrastructure: http://www.apache.org/dev/project-blogs -Jakob On 23 August 2016 at 15:07, Maxime Beauchemin wrote: > I'm planning on working on a minimal apache release this week. If someone > can point to the commit or PRs I can add

Private channel being used for discussion on gitter

Hey all- Apparently there is a private channel being used for project discussion on gitter (the archive would be here: https://gitter.im/apache/incubator-airflow/Airflow_committers/archives/all, similar to the public archive of the regular gitter channel:

Re: Private channel being used for discussion on gitter

>> (INFRA?) can set it to public? Logs will be public then by default. >> >> Wasn't there some discussion on a more relaxed requirement of this >> happening on ASF infrastructure? >> >> Bolke. >> >> Sent from my iPhone >> >> >

Re: Custom (mongodb) hook as a plugin

On 23 September 2016 at 15:06, Rob Goretsky wrote: > More generally, would it make sense to create an enhancement to the plugin > architecture that allows the developer of a new hook to also specify the > name of a new 'connection type' along with what fields would be

Re: Okta Authentication

Yes! We were just about to start writing one of our own. -Jakob On 17 November 2016 at 14:30, Brian Yang wrote: > Good Afternoon, > > I have implemented an authentication backend for Airflow to authenticate > against an Okta server. Would this be something that

Re: Next release?

I'm going to set aside some time early next week to see where we are in the process and make sure nothing's blocking us. (Jakob announces it publicly so he can be shamed if he doesn't follow through) On 11 November 2016 at 14:50, siddharth anand wrote: > Chris, > I have

Re: +1 on PRs!

Be sure to distinguish between +1 == I want this, and +1 == I approve this change to be merged into the codebase. Non-committers are welcome and encouraged to review patches, including providing +1s. The patch can't be merged on the basis of that non-committer +1 only (a committer's +1 is still

Re: Podling Report Reminder - April 2017

On 5 April 2017 at 10:33, Bolke de Bruin wrote: > If you can please include our intention to graduate after the 1.8.1 release > (no more reports ;-). Did I miss this discussion on the mailing list? If so, can you point me to it? If it was discussed there; there may be some

Re: 1.10.0beta1 now available for download

Hey all- With my Mentor hat on, I need to point out that ASF doesn't really have beta releases. This work is awesome, but really needs to go through the proper steps. The Release Candidate process is pretty well described: https://incubator.apache.org/policy/incubation.html#releases. This is

Re: 1.10.0beta1 now available for download

lease)? Ie. is the issue > in calling it a ‘release’ which in this case is just meta for a tarball? In > the original email in never mentioned the word release in conjunction with > the beta I think. > > Cheers > Bolke > > >> On 1 May 2018, at 22:01, Jakob Homan <jgho..

Re: 1.10.0beta1 now available for download

t -> acc -> prod release process > together with the community? The release process you seem to be referring is > only part of the last state imho. Or > do we need to call a vote on every state change? > > Cheers > Bolke > > >> On 1 May 2018, at 22:47, Jakob Ho

Re: 1.10.0beta1 now available for download

t; (also from the wider community here :) ). > > Cheers > Bolke > > * dont misunderstand me here please, for Releases (e.g. 1.10.0 with no extra > label) I’m quite okay. > >> On 1 May 2018, at 23:51, Jakob Homan <jgho...@gmail.com> wrote: >> >> Hey-

Re: 1.10.0beta1 now available for download

dbr...@gmail.com> wrote: > Hi Jakob, > > I’m having the feeling we are on different wave lengths and we are not > getting closer :-(. > > Remarks inline. > >> On 2 May 2018, at 22:56, Jakob Homan <jgho...@gmail.com> wrote: >> >> Hey Bolke- >> Stab

[RESULT][VOTE] Release Airflow 1.9.0

The vote to release Airflow 1.9.0-incubating, having been open for 11 days is now closed. There were three binding +1s and no -1 votes. +1 (binding): Chris Douglas Justin Mclean Jakob Homan The release is approved. Thanks to all those who voted. -Jakob On 29 December 2017 at 12:18, Chris

Re: Airflow thshirts

pparently the link didn't work either. I'll do a second try soon > and add a feather! > > Max > > On Wed, Jan 24, 2018 at 11:45 PM, Sid Anand <san...@apache.org> wrote: > >> I couldn't agree more.. >> >> add the feather :_) >> >> -s >> >

Re: Airflow thshirts

*Apache* Airflow... ... -jg On 24 January 2018 at 14:42, Trent Robbins wrote: > Thanks Max! > > Trent > > > > > > Best, > > Trent Robbins > Strategic Consultant for Open Source Software > Tau Informatics LLC > desk: 415-404-9452 > cell: 513-233-5651 >

Re: [RESULT][VOTE] Airflow 1.9.0rc8

Sent out a call to arms... -jg On 27 December 2017 at 10:22, Sid Anand wrote: > Ugh... you're right. Hmn... what about our other 2 mentors? > > -s > > On Wed, Dec 27, 2017 at 4:14 AM, Bolke de Bruin wrote: > >> Did you count 3? I only counted 2? >> >>

Re: PR Review Dashboard?

Spark is an order of magnitude larger in terms of contributors, codebase, issues, etc. I don't think adding an layer of complexity into the review process would be helpful right now. Not everything that works for one ASF project works for another. I'd vote against this. -Jakob On 28 August

Seattle Apache Airflow Meetup ready for members; planning its first get together

Hey all- For those in the Puget Sound area, I'm happy to announce we've formed the Seattle Apache Airflow Meetup and hope to schedule our first get together for mid October. Please reach out if you're interested in submitting a talk. https://www.meetup.com/Seattle-Apache-Airflow-Users-Group/

Re: [VOTE][RESULT] Replace with Gitter with Slack?

So, binding VOTEs are generally only called on releases, where PMC members get those binding votes (and on electing new committers or PMC members, and those votes happen in private on the private list). Communities often call VOTEs on other things, like logos, questions of sponsorship, large scale

[DISCUSS] AIP - Time for Airflow Improvement Proposals?

Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to document and gather consensus on large changes to the code base. Some examples: * Kafka Improvement Proposals (KIP) - https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals * Flink Improvement

Re: [VOTE] Airflow 1.10.0rc1

+1 (binding) * Sigs look good * Artifact has incubating in name * LICENSE/NOTICE/DISCLAIMER look good - nit: DISCLAIMER is not word wrapped to 80 chars as I've seen in other projects. * Nit: Last release Sebb called out "Copyright 2016 and onwards" in NOTICE as being imprecise. This language

Re: [VOTE] Airflow 1.10.0rc1

@Bolke - I didn't raise the concern, so I can't speak to whether or not Sebb will be ok with that. He tends to be pretty fastidious on this stuff and 'but some other TLP does it' hasn't gone over well before (trust me... I've tried). Totally up to you if you'd rather discuss it as part of the

Re: [VOTE] Migrate to Github as primary repo (a.k.a. Gitbox)

> +1 (binding) > > For future reference, is this vote for anyone on the mailing list, or for > those with some kind of status in the project? Matthew - yeah, binding votes are reserved for committers or PMC members (depending on the vote). Everyone in the community is encouraged to vote, and

Re: Apache Spark Interfering with Airflow Jira/PRs ??

Open a ticket against infra@. Either a misconfiguration or spam. > On Sep 2, 2018, at 12:48 PM, Kaxil Naik wrote: > > I am getting that too. Tons of emails as well about the same. Not sure the > reason. > >> On Sun, 2 Sep 2018, 20:45 Sid Anand, wrote: >> >> Fellow committers... what

Re: Airflow: Apache Graduation

The big list that *has* to be filled out and correct is here: http://incubator.apache.org/projects/airflow.html This is usually done by the Champion, Chris Riccomini. Chris - are you still interested to do this? After that and the maturity questionnaire are in good shape, it's: 1) Graduation

Re: Fundamental change - Separate DAG name and id.

Sounds like this may be a good candidate for an Airflow Improvement Plan... On 20 September 2018 at 22:45, Brian Greene wrote: > Prior to using airflow for much, on first inspection, I think I may have > agreed with you. > > After a bit of use I’d agree with Fokko and others - this isn’t really

Graduation resolution passed - Airflow is a TLP

Hey all- The Board minutes haven't been published yet (probably due to Holiday-related slowness), but I can see through the admin tool that our Graduation resolution was approved yesterday at the meeting. Airflow is the 199th current active Top Level Project in Apache. Congrats all. -Jakob

[VOTE] Graduate the Apache Airflow as a TLP

* Fokko Driesprong * Hitesh Shah * Jakob Homan * Jeremiah Lowin * Joy Gao * Kaxil Naik * Maxime Beauchemin * Siddharth Anand * Sumit Maheshwari * Tao Feng NOW, THEREFORE, BE IT FURTHER RESOLVED, that Bolke de Bruin be appointed to the office of Vice President, Apache Airflow, to

Re: [DISCUSS] Apache Airflow graduation from the incubator

I'll finish up the template at http://incubator.apache.org/projects/airflow.html tomorrow or Friday (I *think* you have to be an IPMC member to update it since it lives in the Incubator SVN). Looks like there's no actual work to do, just marking stuff that has been done but not yet recorded, and

[RESULT] Graduate Apache Airflow as a TLP

inding) > >> > >> Excited to see this happenning. > >> > >> On Sat 1 Dec, 2018, 20:35 >> > >>> +1 (binding)! > >>> > >>> On 30 November 2018 21:33:14 GMT, Jakob Homan wrote: > >>>> Hey all! > >&

Re: [RESULT] Graduate Apache Airflow as a TLP

t; On Tue, Dec 4, 2018, 20:04 Ash Berlin-Taylor > >> Missed my vote off that list :) >> >> > On 4 Dec 2018, at 18:17, Jakob Homan wrote: >> > >> > I neglected to add my binding +1, so I'll do so now. >> > >> > With three days havin

Re: [DISCUSS] Apache Airflow graduation from the incubator

With my Mentor hat on, I'm entirely confident that Airflow is ready to graduate. The community broadly gets the Apache Way and operates within it. The community is healthy and engaged. The last couple releases went well, with no hitches whatsoever for the last one. The graduation process is

Re: Guidelines on Contrib vs Non-contrib

> My understanding as a contributor is that if a hook/operator is in core, it > means that a committer is willing to take personal responsibility to > maintain it (or at least help maintain it), and everything else goes in > contrib. That's not correct. All of the code is owned by the entire

Re: [RESULT] Graduate Apache Airflow as a TLP

The VOTE passed in Incubator. I'll add it the resolution to the Board agenda, who meet this month on the 19th. They'll approve and Airflow will be a TLP. -Jakob On Wed, Dec 5, 2018 at 3:31 PM Jakob Homan wrote: > > Been traveling today. Just started the VOTE over in the g

Re: [DISCUSS] Apache Airflow graduation from the incubator

I've finished the paperwork. I don't seem to have karma to trigger the build on Jenkins, so we'll just wait for the daily rebuild. With that, I've opened the VOTE thread as well. Thanks everybody. On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan wrote: > > I'll finish up the template at