Thanks,
-Tavares
I+1
It’s hard to be subscribed to both dev@ and users@ (so. much. email.), and
you’d need devs subscribed to both for users to have a good experience, to
get their questions well-answered.
I unsubscribed from users@ and now that is invisible to me - good for my
focus, bad for the users.
A majori
Hi all,
I have created a document to summarize the discussion from our dev call for
Airflow 2.0 this Monday. Apologies for the delay in publishing the Meeting
Notes.
Thank you all who joined the call.
*Doc Link*:
https://cwiki.apache.org/confluence/display/AIRFLOW/Meeting+Notes#MeetingNotes-#5:2
I'm with Aizhamal, though slightly stronger at -0.5.
-ash
On Sep 25 2020, at 7:37 pm, Aizhamal Nurmamat kyzy wrote:
> -0 binding, because we never really promoted the user list in airflow (it was
> set up relatively late) and never made a clear distinction between user/dev
> lists. But I see th
-0 binding, because we never really promoted the user list in airflow (it
was set up relatively late) and never made a clear distinction between
user/dev lists. But I see the convenience it brings to developers, though
there is a potential to lock out users who are not familiar with GitHub.
Also,
+1 (binding)
On Tue, Sep 22, 2020 at 12:40 PM Kaxil Naik wrote:
> @tomek - Yup we could do that
>
> On Tue, Sep 22, 2020 at 8:35 PM Tomasz Urbaszek
> wrote:
>
>> +1 binding
>>
>> Should we change "Ask a question or get support" issue type to point
>> to GH discussion?
>>
>> T.
>>
>>
>> On Tue,
