Could Airbnb maintain their own release branch for their internal Airflow sites? This would insulate you from wild changes :)
On Sat, May 14, 2016 at 8:52 AM, Jeremiah Lowin <[email protected]> wrote: > Hi all, > > I've been out of email/phone range for a few days (and will be for a few > more, just have brief access now) so I'm just catching up on all the > activity. > > I think this proposal has its heart in the right place. There's a lot of > effort that goes in to the Apache transition and for the Airbnb team in > particular (though truly for everyone) it introduces a regime change in > terms of process and workflow. As a result, I think it feels like we are > stretched a little thin and there's a legitimate concern that major changes > could slip by with unintended consequences (I've been on both sides of that > already :) ) > > However, I believe that the good work we are doing to formalize procedures > and documentation and make development discussion more open will counteract > that in the near future and eliminate it shortly thereafter. Therefore, I > do trust the "Apache way" and I think after a few growing pains it will > really work smoothly. I agree that we should just all recognize when we are > touching "sensitive areas" of Airflow and allow those changes to bake a > little longer to ensure that many eyes get on them. > > As a concrete example, I know I'm on Bolke's list because of my perceived > knowledge of the scheduler's inner workings. And while I wont necessarily > dispel those rumors, the truth is that I acquired that knowledge simply by > being tasked with certain deep-rooted bug reports and PRs. There could be a > commit tomorrow that renders a lot of that obsolete and produces a new > "scheduler guru". My point is that knowledge is fluid, especially at this > stage, and I believe the best (and most robust) thing we can do is share > and democratize it as much as possible. > > So that's just a long way of saying: we know what a "big" change looks > like, and let's just make sure we have lots of talented committers > evaluating them :) > > J > > On Fri, May 13, 2016 at 10:08 AM Bolke de Bruin <[email protected]> wrote: > > > > > > > Sent from my iPhone > > > > > On 13 mei 2016, at 19:02, Jakob Homan <[email protected]> wrote: > > > > > >> On 13 May 2016 at 00:40, Bolke de Bruin <[email protected]> wrote: > > >> The question is how to keep the trust of that first group - they are > > vital to the work - while growing the community. > > > > > > Another perspective is for the first group to trust the Apache Way. > > > The procedures, norms, votes, requirements, whole Incubator process, > > > etc. is designed to build a functioning community that addresses all > > > these issues. It doesn't always work (not all incubations succeed), > > > but it does the vast majority of the time. > > > > > > This is just the first couple of weeks of Airflow's incubation and the > > > culture shock is definitely setting in, but we'll get past this pretty > > > quickly. I do thnk Airflow will be very successful at Apache. > > > > > > > Hear hear! :-) > > > > > Best, > > > Jakob > > > -- Lance Norskog [email protected] Redwood City, CA
