You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Kaxil Naik <ka...@gmail.com> on 2020/10/29 12:19:12 UTC

Re: [VOTE] Enable Github Discussions on Apache Airflow Github Repo

Github Discussions have now been enabled:
https://github.com/apache/airflow/discussions/.

I have created a PR to direct Users to Github Discussions instead of Slack
for asking questions so they are indexed:
https://github.com/apache/airflow/pull/11940

Regards,
Kaxil

On Fri, Sep 25, 2020 at 8:16 PM Ry Walker <ry...@rywalker.com> wrote:

> 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 majority of Airflow users would know GitHub and have an account, and it
> would be convenient to the devs if most questions were asked there, rather
> than on users@ or slack - because:
>
> - We’re already in GitHub reviewing PRs and issues
> - the q&a would have a permalink, and be indexed in search engines better
> (reduce repeated questions)
> - It’s be worthwhile to write better questions and write better answers
> there vs on an ephemeral mailing list or slack thread
>
> This change would enhance UX for both devs and users.
>
> -Ry
>
>
> On Fri, Sep 25, 2020 at 3:00 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>
>> I'm with Aizhamal, though slightly stronger at -0.5.
>>
>> -ash
>>
>> On Sep 25 2020, at 7:37 pm, Aizhamal Nurmamat kyzy <ai...@apache.org>
>> 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 the convenience it brings to developers, though
>> there is a potential to lock out users who are not familiar with GitHub.
>>
>> Also, we must add code of conduct with the PR and update the website with
>> the info of where user questions need to be directed.
>>
>> On Fri, Sep 25, 2020 at 9:34 AM Maxime Beauchemin <
>> maximebeauchemin@gmail.com> wrote:
>>
>> +1 (binding)
>>
>> On Tue, Sep 22, 2020 at 12:40 PM Kaxil Naik <ka...@gmail.com> wrote:
>>
>> @tomek - Yup we could do that
>>
>> On Tue, Sep 22, 2020 at 8:35 PM Tomasz Urbaszek <tu...@apache.org>
>> wrote:
>>
>> +1 binding
>>
>> Should we change "Ask a question or get support" issue type to point
>> to GH discussion?
>>
>> T.
>>
>>
>> On Tue, Sep 22, 2020 at 9:15 PM Austin Bennett
>> <wh...@gmail.com> wrote:
>> >
>> > +1
>> >
>> > just make sure to appropriate self-police, to keep use for intended
>> purposes.
>> >
>> > On Tue, Sep 22, 2020 at 12:05 PM Deng Xiaodong <xd...@gmail.com>
>> wrote:
>> >>
>> >> +1.
>> >>
>> >> I did share some concerns with folks, but I think mostly already
>> clarified well in the earlier discussion.
>> >>
>> >>
>> >> XD
>> >>
>> >> On 22 Sep 2020, at 9:00 PM, Daniel Imberman <da...@gmail.com>
>> wrote:
>> >>
>> >> +1
>> >>
>> >> via Newton Mail
>> >>
>> >> On Tue, Sep 22, 2020 at 11:59 AM, Kaxil Naik <ka...@apache.org>
>> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> This email calls for a vote to enable Github Discussion on Apache
>> Airflow repo.
>> >>
>> >> Intended Use:
>> >> A forum for users, you might consider it as a replacement of
>> users@airflow.apache.org.
>> >>
>> >> Caveats:
>> >>
>> >> GitHub discussion is NOT to be used for anything other than user help.
>> As is the policy of the ASF Foundation, all code-related discussions and
>> project management activities MUST be reflected to an ASF mailing list (
>> dev@airflow.apache.org).
>> >>
>> >>
>> >> Discussion Thread:
>> >>
>> https://lists.apache.org/thread.html/rfb8c12f0a9f2be43eeab8036104c4799eb645ebed3920b390dc61b76%40%3Cdev.airflow.apache.org%3E
>> >>
>> >> Consider this my +1 binding
>> >>
>> >> Regards,
>> >> Kaxil
>> >>
>> >>
>>
>> --
> Sent from Gmail Mobile
>

Re: [VOTE] Enable Github Discussions on Apache Airflow Github Repo

Posted by Jarek Potiuk <Ja...@polidea.com>.
Nice!

On Thu, Oct 29, 2020 at 1:19 PM Kaxil Naik <ka...@gmail.com> wrote:

> Github Discussions have now been enabled:
> https://github.com/apache/airflow/discussions/.
>
> I have created a PR to direct Users to Github Discussions instead of Slack
> for asking questions so they are indexed:
> https://github.com/apache/airflow/pull/11940
>
> Regards,
> Kaxil
>
> On Fri, Sep 25, 2020 at 8:16 PM Ry Walker <ry...@rywalker.com> wrote:
>
>> 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 majority of Airflow users would know GitHub and have an account, and it
>> would be convenient to the devs if most questions were asked there, rather
>> than on users@ or slack - because:
>>
>> - We’re already in GitHub reviewing PRs and issues
>> - the q&a would have a permalink, and be indexed in search engines better
>> (reduce repeated questions)
>> - It’s be worthwhile to write better questions and write better answers
>> there vs on an ephemeral mailing list or slack thread
>>
>> This change would enhance UX for both devs and users.
>>
>> -Ry
>>
>>
>> On Fri, Sep 25, 2020 at 3:00 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>>
>>> I'm with Aizhamal, though slightly stronger at -0.5.
>>>
>>> -ash
>>>
>>> On Sep 25 2020, at 7:37 pm, Aizhamal Nurmamat kyzy <ai...@apache.org>
>>> 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 the convenience it brings to developers, though
>>> there is a potential to lock out users who are not familiar with GitHub.
>>>
>>> Also, we must add code of conduct with the PR and update the website
>>> with the info of where user questions need to be directed.
>>>
>>> On Fri, Sep 25, 2020 at 9:34 AM Maxime Beauchemin <
>>> maximebeauchemin@gmail.com> wrote:
>>>
>>> +1 (binding)
>>>
>>> On Tue, Sep 22, 2020 at 12:40 PM Kaxil Naik <ka...@gmail.com> wrote:
>>>
>>> @tomek - Yup we could do that
>>>
>>> On Tue, Sep 22, 2020 at 8:35 PM Tomasz Urbaszek <tu...@apache.org>
>>> wrote:
>>>
>>> +1 binding
>>>
>>> Should we change "Ask a question or get support" issue type to point
>>> to GH discussion?
>>>
>>> T.
>>>
>>>
>>> On Tue, Sep 22, 2020 at 9:15 PM Austin Bennett
>>> <wh...@gmail.com> wrote:
>>> >
>>> > +1
>>> >
>>> > just make sure to appropriate self-police, to keep use for intended
>>> purposes.
>>> >
>>> > On Tue, Sep 22, 2020 at 12:05 PM Deng Xiaodong <xd...@gmail.com>
>>> wrote:
>>> >>
>>> >> +1.
>>> >>
>>> >> I did share some concerns with folks, but I think mostly already
>>> clarified well in the earlier discussion.
>>> >>
>>> >>
>>> >> XD
>>> >>
>>> >> On 22 Sep 2020, at 9:00 PM, Daniel Imberman <
>>> daniel.imberman@gmail.com> wrote:
>>> >>
>>> >> +1
>>> >>
>>> >> via Newton Mail
>>> >>
>>> >> On Tue, Sep 22, 2020 at 11:59 AM, Kaxil Naik <ka...@apache.org>
>>> wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> This email calls for a vote to enable Github Discussion on Apache
>>> Airflow repo.
>>> >>
>>> >> Intended Use:
>>> >> A forum for users, you might consider it as a replacement of
>>> users@airflow.apache.org.
>>> >>
>>> >> Caveats:
>>> >>
>>> >> GitHub discussion is NOT to be used for anything other than user
>>> help. As is the policy of the ASF Foundation, all code-related discussions
>>> and project management activities MUST be reflected to an ASF mailing list (
>>> dev@airflow.apache.org).
>>> >>
>>> >>
>>> >> Discussion Thread:
>>> >>
>>> https://lists.apache.org/thread.html/rfb8c12f0a9f2be43eeab8036104c4799eb645ebed3920b390dc61b76%40%3Cdev.airflow.apache.org%3E
>>> >>
>>> >> Consider this my +1 binding
>>> >>
>>> >> Regards,
>>> >> Kaxil
>>> >>
>>> >>
>>>
>>> --
>> Sent from Gmail Mobile
>>
>

-- 

Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer

M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>