Re: [DISCUSS] Rename channels on slack

[Aritra Basu]

Hmm, I'm not a big fan of dev support since I would see it as support for a
developer using airflow vs a developer developing airflow. I much prefer
contributing since it makes it clear it's for someone contributing to
airflow.

--
Regards,
Aritra Basu

On Fri, Feb 9, 2024, 10:42 AM Amogh Desai  wrote:

> Good discussions going on. Personally I align with what Jed, Vincent and
> Jarek had to say.
>
> My choices would be:
> #dev-support -> from #development
> #troubleshooting
> #best-practices
> #random
> #first-pr-support
>
> But yes, maybe we can change it to something better as well? Any ideas?
>
> Why not just #first-pr
>
> Or maybe someone can propose a better name for #contributing that is less
> > ambiguous?
> >
> What do you all think of #dev-support? This reason the confusion arises is
> because #contributing can translate to many
> meanings.
>
> Thanks & Regards,
> Amogh Desai
>
>
>
>
> On Fri, Feb 9, 2024 at 4:45 AM Jarek Potiuk  wrote:
>
> > #learn-contributing maybe ?
> >
> > On Fri, Feb 9, 2024 at 12:14 AM Jarek Potiuk  wrote:
> >
> > > Vincent:
> > >
> > > > I think we can modify that after we renamed the channels.
> > >
> > > Yes, definitely.
> > >
> > > Alexander:
> > >
> > > > Why a special channel for the first PR?
> > >
> > > Yeah. I do not particularly like this name either. It used to be called
> > > #newbie-questions - which was a bit intimidating (especially for
> > > experienced programmers who wanted to do their first contributions)
> > > But yes, maybe we can change it to something better as well? Any ideas?
> > >
> > > J.
> > >
> > >
> > >
> > >
> > > On Thu, Feb 8, 2024 at 11:43 PM Vincent Beck 
> > wrote:
> > >
> > >> I like #contributing. Also, I just realized that the confusion around
> > >> #development might come from https://airflow.apache.org/community/
> > where
> > >> #development should be listed under "Want to contribute?" and not "Are
> > you
> > >> a user?". I think we can modify that after we renamed the channels.
> > >>
> > >> On 2024/02/08 22:35:20 Jarek Potiuk wrote:
> > >> > Speaking of which (#development-first-pr-support) - it indeed
> creates
> > >> > potential confusion,. because #contributing might be ambiguous. But
> > >> likely
> > >> > this will be far less of a problem and we can do just that (shorter
> is
> > >> > better):
> > >> >
> > >> > #contributing
> > >> > #troubleshooting
> > >> > #best-practices
> > >> > #random
> > >> > #first-pr-support
> > >> >
> > >> > Or maybe someone can propose a better name for #contributing that is
> > >> less
> > >> > ambiguous?
> > >> >
> > >> > J.
> > >> >
> > >> >
> > >> >
> > >> > On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
> > >> >  wrote:
> > >> >
> > >> > > I was +1 to Jarek first but reading the counter proposal from
> > Vicent I
> > >> > > change to +1 like Vincent proposes. Also not against Jarek but
> > >> shorter is
> > >> > > better.
> > >> > >
> > >> > > Sent from Outlook for iOS
> > >> > > 
> > >> > > From: Vincent Beck 
> > >> > > Sent: Thursday, February 8, 2024 3:29:24 PM
> > >> > > To: dev@airflow.apache.org 
> > >> > > Subject: Re: [DISCUSS] Rename channels on slack
> > >> > >
> > >> > > I am +1 in renaming these channels because, as said, most of
> > messages
> > >> in
> > >> > > @development are nothing to do there.
> > >> > >
> > >> > > Though, I would just rename #development to #contributing. To me,
> > >> > > #troubleshooting is already a good name and clear. But this is
> only
> > my
> > >> > > personal opinion. I am not against the names Jarek suggested.
> > >> > >
> > >> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > >> > > > Hey here,
> > >> > > >
> > >> > > > The number of "troubleshooting/best-practices" questions we have
> > in
> > >> > > > #development channel on Slack reached the level where we have
> more
> > >> of
> > >> > > those
> > >> > > > than discussion about airflow development.
> > >> > > >
> > >> > > > There were few slack proposals, that we should change the names,
> > >> but it's
> > >> > > > quite a significant change for everyone, so we need to discuss
> and
> > >> have
> > >> > > > [LAZY CONSENSUS] here.
> > >> > > >
> > >> > > > My proposal is to rename them like that (but I am totally open
> to
> > >> other
> > >> > > > ideas):
> > >> > > >
> > >> > > > #development -> #contriuting-to-airflow
> > >> > > > #troubleshooting -> #troubleshooting-questions
> > >> > > >
> > >> > > > And I propose to create a new channel:
> > >> > > >
> > >> > > > #best-practices
> > >> > > >
> > >> > > > There users will be able to discuss best-practices on how to use
> > >> airflow
> > >> > > > (it's not troubleshooting, it's more "please advise how I should
> > do
> > >> > > that).
> > >> > > > We should make some announcements there, update our community
> > pages
> > >> and
> > >> > > > welcome messages on slack to mention this channel.
> > >> > > >
> > >> > > > WDYT?
> > >> > > >
> > >> > >
> > >> > >

Re: [DISCUSS] Rename channels on slack

[Amogh Desai]

Good discussions going on. Personally I align with what Jed, Vincent and
Jarek had to say.

My choices would be:
#dev-support -> from #development
#troubleshooting
#best-practices
#random
#first-pr-support

But yes, maybe we can change it to something better as well? Any ideas?

Why not just #first-pr

Or maybe someone can propose a better name for #contributing that is less
> ambiguous?
>
What do you all think of #dev-support? This reason the confusion arises is
because #contributing can translate to many
meanings.

Thanks & Regards,
Amogh Desai




On Fri, Feb 9, 2024 at 4:45 AM Jarek Potiuk  wrote:

> #learn-contributing maybe ?
>
> On Fri, Feb 9, 2024 at 12:14 AM Jarek Potiuk  wrote:
>
> > Vincent:
> >
> > > I think we can modify that after we renamed the channels.
> >
> > Yes, definitely.
> >
> > Alexander:
> >
> > > Why a special channel for the first PR?
> >
> > Yeah. I do not particularly like this name either. It used to be called
> > #newbie-questions - which was a bit intimidating (especially for
> > experienced programmers who wanted to do their first contributions)
> > But yes, maybe we can change it to something better as well? Any ideas?
> >
> > J.
> >
> >
> >
> >
> > On Thu, Feb 8, 2024 at 11:43 PM Vincent Beck 
> wrote:
> >
> >> I like #contributing. Also, I just realized that the confusion around
> >> #development might come from https://airflow.apache.org/community/
> where
> >> #development should be listed under "Want to contribute?" and not "Are
> you
> >> a user?". I think we can modify that after we renamed the channels.
> >>
> >> On 2024/02/08 22:35:20 Jarek Potiuk wrote:
> >> > Speaking of which (#development-first-pr-support) - it indeed creates
> >> > potential confusion,. because #contributing might be ambiguous. But
> >> likely
> >> > this will be far less of a problem and we can do just that (shorter is
> >> > better):
> >> >
> >> > #contributing
> >> > #troubleshooting
> >> > #best-practices
> >> > #random
> >> > #first-pr-support
> >> >
> >> > Or maybe someone can propose a better name for #contributing that is
> >> less
> >> > ambiguous?
> >> >
> >> > J.
> >> >
> >> >
> >> >
> >> > On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
> >> >  wrote:
> >> >
> >> > > I was +1 to Jarek first but reading the counter proposal from
> Vicent I
> >> > > change to +1 like Vincent proposes. Also not against Jarek but
> >> shorter is
> >> > > better.
> >> > >
> >> > > Sent from Outlook for iOS
> >> > > 
> >> > > From: Vincent Beck 
> >> > > Sent: Thursday, February 8, 2024 3:29:24 PM
> >> > > To: dev@airflow.apache.org 
> >> > > Subject: Re: [DISCUSS] Rename channels on slack
> >> > >
> >> > > I am +1 in renaming these channels because, as said, most of
> messages
> >> in
> >> > > @development are nothing to do there.
> >> > >
> >> > > Though, I would just rename #development to #contributing. To me,
> >> > > #troubleshooting is already a good name and clear. But this is only
> my
> >> > > personal opinion. I am not against the names Jarek suggested.
> >> > >
> >> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> >> > > > Hey here,
> >> > > >
> >> > > > The number of "troubleshooting/best-practices" questions we have
> in
> >> > > > #development channel on Slack reached the level where we have more
> >> of
> >> > > those
> >> > > > than discussion about airflow development.
> >> > > >
> >> > > > There were few slack proposals, that we should change the names,
> >> but it's
> >> > > > quite a significant change for everyone, so we need to discuss and
> >> have
> >> > > > [LAZY CONSENSUS] here.
> >> > > >
> >> > > > My proposal is to rename them like that (but I am totally open to
> >> other
> >> > > > ideas):
> >> > > >
> >> > > > #development -> #contriuting-to-airflow
> >> > > > #troubleshooting -> #troubleshooting-questions
> >> > > >
> >> > > > And I propose to create a new channel:
> >> > > >
> >> > > > #best-practices
> >> > > >
> >> > > > There users will be able to discuss best-practices on how to use
> >> airflow
> >> > > > (it's not troubleshooting, it's more "please advise how I should
> do
> >> > > that).
> >> > > > We should make some announcements there, update our community
> pages
> >> and
> >> > > > welcome messages on slack to mention this channel.
> >> > > >
> >> > > > WDYT?
> >> > > >
> >> > >
> >> > >
> -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> >> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> >> > >
> >> > >
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> >> For additional commands, e-mail: dev-h...@airflow.apache.org
> >>
> >>
>

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

[Wei Lee]

+0 (non-binding)

Best,
Wei

> On Feb 8, 2024, at 11:15 PM, Elad Kalif  wrote:
> 
> I'm -0 (binding)
> 
> 
> On Thu, Feb 8, 2024 at 10:51 AM Akash Sharma <2akash111...@gmail.com> wrote:
> 
>> +1 (non binding)
>> 
>> On Thu, 8 Feb 2024, 13:30 Jarek Potiuk,  wrote:
>> 
>>> Since this is a controversial topic, just a kind reminder - the voting
>> ends
>>> today in ~ 8 hrs. If you feel (even somewhat) strongly about either
>>> direction - that's the last time to cast the vote.
>>> 
>>> And yes - fractional votes are possible :) - see
>>> 
>>> 
>> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
>>> For Jed's case it **might** mean:  "-0.5: 'I don't like this idea, but I
>>> can't find any rational justification for my feelings.'"
>>> 
>>> J.
>>> 
>>> On Wed, Feb 7, 2024 at 5:12 AM Amogh Desai 
>>> wrote:
>>> 
 Love the vote from @Jed Cunningham  here!
 
 On Wed, Feb 7, 2024 at 3:05 AM Jed Cunningham <
>> jedcunning...@apache.org>
 wrote:
 
> -0.5
> 
 
>>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

Vincent:

> I think we can modify that after we renamed the channels.

Yes, definitely.

Alexander:

> Why a special channel for the first PR?

Yeah. I do not particularly like this name either. It used to be called
#newbie-questions - which was a bit intimidating (especially for
experienced programmers who wanted to do their first contributions)
But yes, maybe we can change it to something better as well? Any ideas?

J.




On Thu, Feb 8, 2024 at 11:43 PM Vincent Beck  wrote:

> I like #contributing. Also, I just realized that the confusion around
> #development might come from https://airflow.apache.org/community/ where
> #development should be listed under "Want to contribute?" and not "Are you
> a user?". I think we can modify that after we renamed the channels.
>
> On 2024/02/08 22:35:20 Jarek Potiuk wrote:
> > Speaking of which (#development-first-pr-support) - it indeed creates
> > potential confusion,. because #contributing might be ambiguous. But
> likely
> > this will be far less of a problem and we can do just that (shorter is
> > better):
> >
> > #contributing
> > #troubleshooting
> > #best-practices
> > #random
> > #first-pr-support
> >
> > Or maybe someone can propose a better name for #contributing that is less
> > ambiguous?
> >
> > J.
> >
> >
> >
> > On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
> >  wrote:
> >
> > > I was +1 to Jarek first but reading the counter proposal from Vicent I
> > > change to +1 like Vincent proposes. Also not against Jarek but shorter
> is
> > > better.
> > >
> > > Sent from Outlook for iOS
> > > 
> > > From: Vincent Beck 
> > > Sent: Thursday, February 8, 2024 3:29:24 PM
> > > To: dev@airflow.apache.org 
> > > Subject: Re: [DISCUSS] Rename channels on slack
> > >
> > > I am +1 in renaming these channels because, as said, most of messages
> in
> > > @development are nothing to do there.
> > >
> > > Though, I would just rename #development to #contributing. To me,
> > > #troubleshooting is already a good name and clear. But this is only my
> > > personal opinion. I am not against the names Jarek suggested.
> > >
> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > > Hey here,
> > > >
> > > > The number of "troubleshooting/best-practices" questions we have in
> > > > #development channel on Slack reached the level where we have more of
> > > those
> > > > than discussion about airflow development.
> > > >
> > > > There were few slack proposals, that we should change the names, but
> it's
> > > > quite a significant change for everyone, so we need to discuss and
> have
> > > > [LAZY CONSENSUS] here.
> > > >
> > > > My proposal is to rename them like that (but I am totally open to
> other
> > > > ideas):
> > > >
> > > > #development -> #contriuting-to-airflow
> > > > #troubleshooting -> #troubleshooting-questions
> > > >
> > > > And I propose to create a new channel:
> > > >
> > > > #best-practices
> > > >
> > > > There users will be able to discuss best-practices on how to use
> airflow
> > > > (it's not troubleshooting, it's more "please advise how I should do
> > > that).
> > > > We should make some announcements there, update our community pages
> and
> > > > welcome messages on slack to mention this channel.
> > > >
> > > > WDYT?
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> For additional commands, e-mail: dev-h...@airflow.apache.org
>
>

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

#learn-contributing maybe ?

On Fri, Feb 9, 2024 at 12:14 AM Jarek Potiuk  wrote:

> Vincent:
>
> > I think we can modify that after we renamed the channels.
>
> Yes, definitely.
>
> Alexander:
>
> > Why a special channel for the first PR?
>
> Yeah. I do not particularly like this name either. It used to be called
> #newbie-questions - which was a bit intimidating (especially for
> experienced programmers who wanted to do their first contributions)
> But yes, maybe we can change it to something better as well? Any ideas?
>
> J.
>
>
>
>
> On Thu, Feb 8, 2024 at 11:43 PM Vincent Beck  wrote:
>
>> I like #contributing. Also, I just realized that the confusion around
>> #development might come from https://airflow.apache.org/community/ where
>> #development should be listed under "Want to contribute?" and not "Are you
>> a user?". I think we can modify that after we renamed the channels.
>>
>> On 2024/02/08 22:35:20 Jarek Potiuk wrote:
>> > Speaking of which (#development-first-pr-support) - it indeed creates
>> > potential confusion,. because #contributing might be ambiguous. But
>> likely
>> > this will be far less of a problem and we can do just that (shorter is
>> > better):
>> >
>> > #contributing
>> > #troubleshooting
>> > #best-practices
>> > #random
>> > #first-pr-support
>> >
>> > Or maybe someone can propose a better name for #contributing that is
>> less
>> > ambiguous?
>> >
>> > J.
>> >
>> >
>> >
>> > On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
>> >  wrote:
>> >
>> > > I was +1 to Jarek first but reading the counter proposal from Vicent I
>> > > change to +1 like Vincent proposes. Also not against Jarek but
>> shorter is
>> > > better.
>> > >
>> > > Sent from Outlook for iOS
>> > > 
>> > > From: Vincent Beck 
>> > > Sent: Thursday, February 8, 2024 3:29:24 PM
>> > > To: dev@airflow.apache.org 
>> > > Subject: Re: [DISCUSS] Rename channels on slack
>> > >
>> > > I am +1 in renaming these channels because, as said, most of messages
>> in
>> > > @development are nothing to do there.
>> > >
>> > > Though, I would just rename #development to #contributing. To me,
>> > > #troubleshooting is already a good name and clear. But this is only my
>> > > personal opinion. I am not against the names Jarek suggested.
>> > >
>> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
>> > > > Hey here,
>> > > >
>> > > > The number of "troubleshooting/best-practices" questions we have in
>> > > > #development channel on Slack reached the level where we have more
>> of
>> > > those
>> > > > than discussion about airflow development.
>> > > >
>> > > > There were few slack proposals, that we should change the names,
>> but it's
>> > > > quite a significant change for everyone, so we need to discuss and
>> have
>> > > > [LAZY CONSENSUS] here.
>> > > >
>> > > > My proposal is to rename them like that (but I am totally open to
>> other
>> > > > ideas):
>> > > >
>> > > > #development -> #contriuting-to-airflow
>> > > > #troubleshooting -> #troubleshooting-questions
>> > > >
>> > > > And I propose to create a new channel:
>> > > >
>> > > > #best-practices
>> > > >
>> > > > There users will be able to discuss best-practices on how to use
>> airflow
>> > > > (it's not troubleshooting, it's more "please advise how I should do
>> > > that).
>> > > > We should make some announcements there, update our community pages
>> and
>> > > > welcome messages on slack to mention this channel.
>> > > >
>> > > > WDYT?
>> > > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
>> > > For additional commands, e-mail: dev-h...@airflow.apache.org
>> > >
>> > >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
>> For additional commands, e-mail: dev-h...@airflow.apache.org
>>
>>

Re: [DISCUSS] Rename channels on slack

[Vincent Beck]

I like #contributing. Also, I just realized that the confusion around 
#development might come from https://airflow.apache.org/community/ where 
#development should be listed under "Want to contribute?" and not "Are you a 
user?". I think we can modify that after we renamed the channels.

On 2024/02/08 22:35:20 Jarek Potiuk wrote:
> Speaking of which (#development-first-pr-support) - it indeed creates
> potential confusion,. because #contributing might be ambiguous. But likely
> this will be far less of a problem and we can do just that (shorter is
> better):
> 
> #contributing
> #troubleshooting
> #best-practices
> #random
> #first-pr-support
> 
> Or maybe someone can propose a better name for #contributing that is less
> ambiguous?
> 
> J.
> 
> 
> 
> On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
>  wrote:
> 
> > I was +1 to Jarek first but reading the counter proposal from Vicent I
> > change to +1 like Vincent proposes. Also not against Jarek but shorter is
> > better.
> >
> > Sent from Outlook for iOS
> > 
> > From: Vincent Beck 
> > Sent: Thursday, February 8, 2024 3:29:24 PM
> > To: dev@airflow.apache.org 
> > Subject: Re: [DISCUSS] Rename channels on slack
> >
> > I am +1 in renaming these channels because, as said, most of messages in
> > @development are nothing to do there.
> >
> > Though, I would just rename #development to #contributing. To me,
> > #troubleshooting is already a good name and clear. But this is only my
> > personal opinion. I am not against the names Jarek suggested.
> >
> > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > Hey here,
> > >
> > > The number of "troubleshooting/best-practices" questions we have in
> > > #development channel on Slack reached the level where we have more of
> > those
> > > than discussion about airflow development.
> > >
> > > There were few slack proposals, that we should change the names, but it's
> > > quite a significant change for everyone, so we need to discuss and have
> > > [LAZY CONSENSUS] here.
> > >
> > > My proposal is to rename them like that (but I am totally open to other
> > > ideas):
> > >
> > > #development -> #contriuting-to-airflow
> > > #troubleshooting -> #troubleshooting-questions
> > >
> > > And I propose to create a new channel:
> > >
> > > #best-practices
> > >
> > > There users will be able to discuss best-practices on how to use airflow
> > > (it's not troubleshooting, it's more "please advise how I should do
> > that).
> > > We should make some announcements there, update our community pages and
> > > welcome messages on slack to mention this channel.
> > >
> > > WDYT?
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > For additional commands, e-mail: dev-h...@airflow.apache.org
> >
> >
> 

-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Re: [DISCUSS] Rename channels on slack

[Alexander Shorin]

On Fri, Feb 9, 2024 at 1:35 AM Jarek Potiuk  wrote:

> ...
> #first-pr-support



Why a special channel for the first PR? Feels like I should move to another
channel if it's my second one while I still could be first-pr-mistakes just
because of different context. Maybe some better naming here?

--
,,,^..^,,,

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

Speaking of which (#development-first-pr-support) - it indeed creates
potential confusion,. because #contributing might be ambiguous. But likely
this will be far less of a problem and we can do just that (shorter is
better):

#contributing
#troubleshooting
#best-practices
#random
#first-pr-support

Or maybe someone can propose a better name for #contributing that is less
ambiguous?

J.



On Thu, Feb 8, 2024 at 10:35 PM Scheffler Jens (XC-AS/EAE-ADA-T)
 wrote:

> I was +1 to Jarek first but reading the counter proposal from Vicent I
> change to +1 like Vincent proposes. Also not against Jarek but shorter is
> better.
>
> Sent from Outlook for iOS
> 
> From: Vincent Beck 
> Sent: Thursday, February 8, 2024 3:29:24 PM
> To: dev@airflow.apache.org 
> Subject: Re: [DISCUSS] Rename channels on slack
>
> I am +1 in renaming these channels because, as said, most of messages in
> @development are nothing to do there.
>
> Though, I would just rename #development to #contributing. To me,
> #troubleshooting is already a good name and clear. But this is only my
> personal opinion. I am not against the names Jarek suggested.
>
> On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > Hey here,
> >
> > The number of "troubleshooting/best-practices" questions we have in
> > #development channel on Slack reached the level where we have more of
> those
> > than discussion about airflow development.
> >
> > There were few slack proposals, that we should change the names, but it's
> > quite a significant change for everyone, so we need to discuss and have
> > [LAZY CONSENSUS] here.
> >
> > My proposal is to rename them like that (but I am totally open to other
> > ideas):
> >
> > #development -> #contriuting-to-airflow
> > #troubleshooting -> #troubleshooting-questions
> >
> > And I propose to create a new channel:
> >
> > #best-practices
> >
> > There users will be able to discuss best-practices on how to use airflow
> > (it's not troubleshooting, it's more "please advise how I should do
> that).
> > We should make some announcements there, update our community pages and
> > welcome messages on slack to mention this channel.
> >
> > WDYT?
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> For additional commands, e-mail: dev-h...@airflow.apache.org
>
>

Re: [DISCUSS] Rename channels on slack

[Scheffler Jens (XC-AS/EAE-ADA-T)]

I was +1 to Jarek first but reading the counter proposal from Vicent I change 
to +1 like Vincent proposes. Also not against Jarek but shorter is better.

Sent from Outlook for iOS

From: Vincent Beck 
Sent: Thursday, February 8, 2024 3:29:24 PM
To: dev@airflow.apache.org 
Subject: Re: [DISCUSS] Rename channels on slack

I am +1 in renaming these channels because, as said, most of messages in 
@development are nothing to do there.

Though, I would just rename #development to #contributing. To me, 
#troubleshooting is already a good name and clear. But this is only my personal 
opinion. I am not against the names Jarek suggested.

On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> Hey here,
>
> The number of "troubleshooting/best-practices" questions we have in
> #development channel on Slack reached the level where we have more of those
> than discussion about airflow development.
>
> There were few slack proposals, that we should change the names, but it's
> quite a significant change for everyone, so we need to discuss and have
> [LAZY CONSENSUS] here.
>
> My proposal is to rename them like that (but I am totally open to other
> ideas):
>
> #development -> #contriuting-to-airflow
> #troubleshooting -> #troubleshooting-questions
>
> And I propose to create a new channel:
>
> #best-practices
>
> There users will be able to discuss best-practices on how to use airflow
> (it's not troubleshooting, it's more "please advise how I should do that).
> We should make some announcements there, update our community pages and
> welcome messages on slack to mention this channel.
>
> WDYT?
>

-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Re: [DISCUSS] Rename channels on slack

[Hussein Awala]

+1 for Jed's suggestion, we can archive the channel once the message is
sent.

Don't forget to mention #development-first-pr-support (or the new channel
name if we want to consolidate the names) for new contributors in the
message.

On Thu, Feb 8, 2024 at 8:07 PM Jarek Potiuk  wrote:

> I see... Hmm.. Fresh start . yeah might be a good idea.
>
> On Thu, Feb 8, 2024 at 7:59 PM Jed Cunningham 
> wrote:
>
> > That's not what I'm proposing. I should have been more verbose before,
> > sorry. Let me rephrase.
> >
> > Don't rename #development. Leave it where it is, restrict posting to
> admins
> > only. Create a new, fresh #contributing where everyone is still welcome.
> > One of us admins will post in #development with links to
> #troubleshooting,
> > #random, #contributing, etc. But #development is "dead" at that point for
> > everyone, just sticking around for a while so folks have time to
> > navigate/join the channels they care about going forward.
> >
> > Basically, don't just rename #development -> #contributing, and carry 14k
> > folks along with us. But leave a map in #development for folks.
> >
>

Re: [VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

[Jarek Potiuk]

+1 (binding):- checked signatures, checksums, licenses and compared content
of the packages. Unfortunately it seems that the binary reproduction is
still not fully working - there is some difference in "tar" layer run by
Jed and myself, so I will need to do some extra checks. It's not a blocker
though, because comparing  the content of the packages shows no
differences.

On Thu, Feb 8, 2024 at 8:38 PM Jed Cunningham 
wrote:

> Hello Apache Airflow Community,
>
> This is a call for the vote to release Helm Chart version 1.12.0.
>
> The release candidate is available at:
> https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.12.0rc1/
>
> airflow-chart-1.12.0-source.tar.gz - is the "main source release" that
> comes with INSTALL instructions.
> airflow-1.12.0.tgz - is the binary Helm Chart release.
>
> Public keys are available at: https://www.apache.org/dist/airflow/KEYS
>
> For convenience "index.yaml" has been uploaded (though excluded from
> voting), so you can also run the below commands.
>
> helm repo add apache-airflow-dev
> https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.12.0rc1/
> helm repo update
> helm install airflow apache-airflow-dev/airflow
>
> airflow-1.12.0.tgz.prov - is also uploaded for verifying Chart Integrity,
> though not strictly required for releasing the artifact based on ASF
> Guidelines.
>
> $ helm gpg verify airflow-1.12.0.tgz
> gpg: Signature made Thu Feb  8 12:21:08 2024 MST
> gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E
> gpg:issuer "jedcunning...@apache.org"
> gpg: Good signature from "Jed Cunningham "
> [ultimate]
> plugin: Chart SHA verified.
> sha256:a261081a40cb88c9052ad9c90968ddb701a2205d0eae816e7945a5b15466f054
>
> The vote will be open for at least 72 hours (2024-02-11 19:45 UTC) or until
> the necessary number of votes is reached.
>
>
> https://www.timeanddate.com/countdown/to?iso=20240211T1945=136=cursive
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Consider this my (binding) +1.
>
> For license checks, the .rat-excludes files is included, so you can run the
> following to verify licenses (just update your path to rat):
>
> tar -xvf airflow-chart-1.12.0-source.tar.gz
> cd airflow-chart-1.12.0
> java -jar apache-rat-0.13.jar chart -E .rat-excludes
>
> Please note that the version number excludes the `rcX` string, so it's now
> simply 1.12.0. This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release it.
>
> The status of testing the Helm Chart by the community is kept here:
> https://github.com/apache/airflow/issues/37259
>
> Thanks,
> Jed
>

[VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

[Jed Cunningham]

Hello Apache Airflow Community,

This is a call for the vote to release Helm Chart version 1.12.0.

The release candidate is available at:
https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.12.0rc1/

airflow-chart-1.12.0-source.tar.gz - is the "main source release" that
comes with INSTALL instructions.
airflow-1.12.0.tgz - is the binary Helm Chart release.

Public keys are available at: https://www.apache.org/dist/airflow/KEYS

For convenience "index.yaml" has been uploaded (though excluded from
voting), so you can also run the below commands.

helm repo add apache-airflow-dev
https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.12.0rc1/
helm repo update
helm install airflow apache-airflow-dev/airflow

airflow-1.12.0.tgz.prov - is also uploaded for verifying Chart Integrity,
though not strictly required for releasing the artifact based on ASF
Guidelines.

$ helm gpg verify airflow-1.12.0.tgz
gpg: Signature made Thu Feb  8 12:21:08 2024 MST
gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E
gpg:issuer "jedcunning...@apache.org"
gpg: Good signature from "Jed Cunningham "
[ultimate]
plugin: Chart SHA verified.
sha256:a261081a40cb88c9052ad9c90968ddb701a2205d0eae816e7945a5b15466f054

The vote will be open for at least 72 hours (2024-02-11 19:45 UTC) or until
the necessary number of votes is reached.

https://www.timeanddate.com/countdown/to?iso=20240211T1945=136=cursive

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Only votes from PMC members are binding, but members of the community are
encouraged to test the release and vote with "(non-binding)".

Consider this my (binding) +1.

For license checks, the .rat-excludes files is included, so you can run the
following to verify licenses (just update your path to rat):

tar -xvf airflow-chart-1.12.0-source.tar.gz
cd airflow-chart-1.12.0
java -jar apache-rat-0.13.jar chart -E .rat-excludes

Please note that the version number excludes the `rcX` string, so it's now
simply 1.12.0. This will allow us to rename the artifact without modifying
the artifact checksums when we actually release it.

The status of testing the Helm Chart by the community is kept here:
https://github.com/apache/airflow/issues/37259

Thanks,
Jed

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

I see... Hmm.. Fresh start . yeah might be a good idea.

On Thu, Feb 8, 2024 at 7:59 PM Jed Cunningham 
wrote:

> That's not what I'm proposing. I should have been more verbose before,
> sorry. Let me rephrase.
>
> Don't rename #development. Leave it where it is, restrict posting to admins
> only. Create a new, fresh #contributing where everyone is still welcome.
> One of us admins will post in #development with links to #troubleshooting,
> #random, #contributing, etc. But #development is "dead" at that point for
> everyone, just sticking around for a while so folks have time to
> navigate/join the channels they care about going forward.
>
> Basically, don't just rename #development -> #contributing, and carry 14k
> folks along with us. But leave a map in #development for folks.
>

Re: [DISCUSS] Rename channels on slack

[Jed Cunningham]

That's not what I'm proposing. I should have been more verbose before,
sorry. Let me rephrase.

Don't rename #development. Leave it where it is, restrict posting to admins
only. Create a new, fresh #contributing where everyone is still welcome.
One of us admins will post in #development with links to #troubleshooting,
#random, #contributing, etc. But #development is "dead" at that point for
everyone, just sticking around for a while so folks have time to
navigate/join the channels they care about going forward.

Basically, don't just rename #development -> #contributing, and carry 14k
folks along with us. But leave a map in #development for folks.

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

>> Maybe we restrict who can post in development for a
period of time with a message directing folks to the right places?

> As long as we don't make it committer only. If you're contributing
something and want some help/feedback, it's not welcoming to find out that
you're to be restricted from the development/contribution channel

Yeah - agree with Constance. I kinda like that so many people (potentially)
watch us while we are contributing and see what we are doing - most of them
are silent, but being in the channel, and even observing how airflow is
created "live" is really great way for a small percentage of those people
to eventually become contributors if they see what's going on and like the
vibe and way the contributors "do it". Typical contribution funnel. I think
if we limit who can join the channel (or even start with trimming it down)
all this might be lost.

I bet quite a few current committers and active contributors got there
mostly because they liked what they saw in #development.

J.


On Thu, Feb 8, 2024 at 7:14 PM Constance Martineau
 wrote:

> > Maybe we restrict who can post in development for a
> period of time with a message directing folks to the right places?
>
> As long as we don't make it committer only. If you're contributing
> something and want some help/feedback, it's not welcoming to find out that
> you're to be restricted from the development/contribution channel
>
> On Thu, Feb 8, 2024 at 12:23 PM Ferruzzi, Dennis
>  wrote:
>
> > I'm all for the shorter names.  I can never understand why so many people
> > ask the questions they do in #development, its purpose seems pretty
> obvious
> > to me but perhaps a rename is good for it; I'm -0 on that one.  I also
> > agree that #troubleshooting is clear and nothing is gained from making it
> > longer.  For the #best-practices one, I like the concept.  I wonder if
> > something like #configuration-questions (I know, it's not short...) may
> be
> > a broader category serving the same purpose?
> >
> >
> >
> >  - ferruzzi
> >
> >
> > 
> > From: Jed Cunningham 
> > Sent: Thursday, February 8, 2024 8:36 AM
> > To: dev@airflow.apache.org
> > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on
> > slack
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you can confirm the sender and
> know
> > the content is safe.
> >
> >
> >
> > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
> > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> pouvez
> > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain
> que
> > le contenu ne présente aucun risque.
> >
> >
> >
> > Sounds good to me. We already have much more niche channels than best
> > practices would be. Worst case no one uses it and we can purge it down
> the
> > road, no harm no foul.
> >
> > One thing we should consider is not renaming development, but starting
> with
> > a fresh channel for contributing. There are nearly 14k people in
> > development today. Maybe we restrict who can post in development for a
> > period of time with a message directing folks to the right places?
> >
>

Re: [DISCUSS] Rename channels on slack

[Constance Martineau]

> Maybe we restrict who can post in development for a
period of time with a message directing folks to the right places?

As long as we don't make it committer only. If you're contributing
something and want some help/feedback, it's not welcoming to find out that
you're to be restricted from the development/contribution channel

On Thu, Feb 8, 2024 at 12:23 PM Ferruzzi, Dennis
 wrote:

> I'm all for the shorter names.  I can never understand why so many people
> ask the questions they do in #development, its purpose seems pretty obvious
> to me but perhaps a rename is good for it; I'm -0 on that one.  I also
> agree that #troubleshooting is clear and nothing is gained from making it
> longer.  For the #best-practices one, I like the concept.  I wonder if
> something like #configuration-questions (I know, it's not short...) may be
> a broader category serving the same purpose?
>
>
>
>  - ferruzzi
>
>
> 
> From: Jed Cunningham 
> Sent: Thursday, February 8, 2024 8:36 AM
> To: dev@airflow.apache.org
> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on
> slack
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez
> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que
> le contenu ne présente aucun risque.
>
>
>
> Sounds good to me. We already have much more niche channels than best
> practices would be. Worst case no one uses it and we can purge it down the
> road, no harm no foul.
>
> One thing we should consider is not renaming development, but starting with
> a fresh channel for contributing. There are nearly 14k people in
> development today. Maybe we restrict who can post in development for a
> period of time with a message directing folks to the right places?
>

Re: [DISCUSS] Rename channels on slack

[Ferruzzi, Dennis]

I'm all for the shorter names.  I can never understand why so many people ask 
the questions they do in #development, its purpose seems pretty obvious to me 
but perhaps a rename is good for it; I'm -0 on that one.  I also agree that 
#troubleshooting is clear and nothing is gained from making it longer.  For the 
#best-practices one, I like the concept.  I wonder if something like 
#configuration-questions (I know, it's not short...) may be a broader category 
serving the same purpose?



 - ferruzzi



From: Jed Cunningham 
Sent: Thursday, February 8, 2024 8:36 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on slack

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.



AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne 
cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas 
confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le 
contenu ne présente aucun risque.



Sounds good to me. We already have much more niche channels than best
practices would be. Worst case no one uses it and we can purge it down the
road, no harm no foul.

One thing we should consider is not renaming development, but starting with
a fresh channel for contributing. There are nearly 14k people in
development today. Maybe we restrict who can post in development for a
period of time with a message directing folks to the right places?

Re: [DISCUSS] Rename channels on slack

[Jed Cunningham]

Sounds good to me. We already have much more niche channels than best
practices would be. Worst case no one uses it and we can purge it down the
road, no harm no foul.

One thing we should consider is not renaming development, but starting with
a fresh channel for contributing. There are nearly 14k people in
development today. Maybe we restrict who can post in development for a
period of time with a message directing folks to the right places?

Re: [DISCUSS] Rename channels on slack

[Jarek Potiuk]

I am all for shorter names.

Also the main reason I came up with best practices because over last few
days (including today) I saw people explicitly asking for best-practices
(explicitly)  in #troubleshooting - and they really did not have any
troubles to shoot, they just wanted to ask how to approach something - and
when I tried to put myself in their shoes, I would have real trouble (!) to
figure out where I should ask those questions - out of the two #development
and #troubleshooting, development would seem like a better one. Also I
think this is the main reason why we would think that #random is not needed
is because sometimes people ask #best-practices questions there. But there
are a number of other random questions there - when we release providers,
praising (yes happens) that after upgrade Airflow works snappier, And it
seems like a good place to safely post questions if it does not fit any of
the other three.

I think now that we should have those:

#contributing
#troubleshooting
#best-practices
#random

Seems like a good set, with quite intuitive meaning and generally it's easy
to guess where to put what with #random being "catch-all".

Does it sound good?

J.


On Thu, Feb 8, 2024 at 4:37 PM Aritra Basu  wrote:

> I also prefer contributing and troubleshooting over the longer names. But
> also not opposed to the other names
>
> --
> Regards,
> Aritra Basu
>
> On Thu, Feb 8, 2024, 8:24 PM Kenten Danas 
> wrote:
>
> > +1 for updating the names. I like #contributing/#troubleshooting, and
> agree
> > #best-practices would be a helpful addition.
> >
> > On Thu, Feb 8, 2024 at 7:50 AM Constance Martineau
> >  wrote:
> >
> > > +1 for #contributing and leaving #troubleshooting. Shorter names in
> slack
> > > are nice where possible.
> > >
> > > No strong opinion on the actual names. Agree that #development needs to
> > be
> > > renamed to something more obvious though.
> > >
> > > On Thu, Feb 8, 2024 at 9:30 AM Vincent Beck 
> wrote:
> > >
> > > > I am +1 in renaming these channels because, as said, most of messages
> > in
> > > > @development are nothing to do there.
> > > >
> > > > Though, I would just rename #development to #contributing. To me,
> > > > #troubleshooting is already a good name and clear. But this is only
> my
> > > > personal opinion. I am not against the names Jarek suggested.
> > > >
> > > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > > > Hey here,
> > > > >
> > > > > The number of "troubleshooting/best-practices" questions we have in
> > > > > #development channel on Slack reached the level where we have more
> of
> > > > those
> > > > > than discussion about airflow development.
> > > > >
> > > > > There were few slack proposals, that we should change the names,
> but
> > > it's
> > > > > quite a significant change for everyone, so we need to discuss and
> > have
> > > > > [LAZY CONSENSUS] here.
> > > > >
> > > > > My proposal is to rename them like that (but I am totally open to
> > other
> > > > > ideas):
> > > > >
> > > > > #development -> #contriuting-to-airflow
> > > > > #troubleshooting -> #troubleshooting-questions
> > > > >
> > > > > And I propose to create a new channel:
> > > > >
> > > > > #best-practices
> > > > >
> > > > > There users will be able to discuss best-practices on how to use
> > > airflow
> > > > > (it's not troubleshooting, it's more "please advise how I should do
> > > > that).
> > > > > We should make some announcements there, update our community pages
> > and
> > > > > welcome messages on slack to mention this channel.
> > > > >
> > > > > WDYT?
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > > >
> > > >
> > >
> >
>

[RESULT] [VOTE] "Require conversation resolution" setting in PRs as permanent solution

[Jarek Potiuk]

Hello everyone,

Summary of the vote in
https://lists.apache.org/thread/5m45dz860ovg4zyvrqscz8m1mnmmrn1g

 5 binding (+1) votes:

* Jarek Potiuk
* Amogh Desai
* Pankaj Koti
* Jens Scheffer
* Hussein Awala

2 binding (-1) votes:

* Bolke de Bruin
* Ash Berlin-Taylor

1 binding (-0.5) votes:

* Jed Cunningham

1 binding (-0) vote:

* Elad Kalif

2 non-binding +1 votes:

* Aritra Basu
* Akash Sharma

Result: +2.5, the vote passed.

So until we decide otherwise, "Require conversation resolution" stays with
us.

J,

Re: [DISCUSS] Rename channels on slack

[Aritra Basu]

I also prefer contributing and troubleshooting over the longer names. But
also not opposed to the other names

--
Regards,
Aritra Basu

On Thu, Feb 8, 2024, 8:24 PM Kenten Danas 
wrote:

> +1 for updating the names. I like #contributing/#troubleshooting, and agree
> #best-practices would be a helpful addition.
>
> On Thu, Feb 8, 2024 at 7:50 AM Constance Martineau
>  wrote:
>
> > +1 for #contributing and leaving #troubleshooting. Shorter names in slack
> > are nice where possible.
> >
> > No strong opinion on the actual names. Agree that #development needs to
> be
> > renamed to something more obvious though.
> >
> > On Thu, Feb 8, 2024 at 9:30 AM Vincent Beck  wrote:
> >
> > > I am +1 in renaming these channels because, as said, most of messages
> in
> > > @development are nothing to do there.
> > >
> > > Though, I would just rename #development to #contributing. To me,
> > > #troubleshooting is already a good name and clear. But this is only my
> > > personal opinion. I am not against the names Jarek suggested.
> > >
> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > > Hey here,
> > > >
> > > > The number of "troubleshooting/best-practices" questions we have in
> > > > #development channel on Slack reached the level where we have more of
> > > those
> > > > than discussion about airflow development.
> > > >
> > > > There were few slack proposals, that we should change the names, but
> > it's
> > > > quite a significant change for everyone, so we need to discuss and
> have
> > > > [LAZY CONSENSUS] here.
> > > >
> > > > My proposal is to rename them like that (but I am totally open to
> other
> > > > ideas):
> > > >
> > > > #development -> #contriuting-to-airflow
> > > > #troubleshooting -> #troubleshooting-questions
> > > >
> > > > And I propose to create a new channel:
> > > >
> > > > #best-practices
> > > >
> > > > There users will be able to discuss best-practices on how to use
> > airflow
> > > > (it's not troubleshooting, it's more "please advise how I should do
> > > that).
> > > > We should make some announcements there, update our community pages
> and
> > > > welcome messages on slack to mention this channel.
> > > >
> > > > WDYT?
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Rename channels on slack

[Elad Kalif]

I'm not sure about #best-practices - To my perspective best practice is
normally a symbol of something that should be improved. Things should be
simple/easy enough thus avoiding the need to have best practice on them.
Thus any best practice discussion needs to be done on GitHub Discussion or
Github Issue (depends on the maturity of the idea) - I don't think we
should have it in Slack where things are not saved and can not be
referenced later.

 On another front I think we should discuss combining #troubleshooting and
#random - At the end both channels serve the same traffic and I can't
recall any event where we asked someone to move a message from one of these
channels to the other one.


On Thu, Feb 8, 2024 at 4:54 PM Kenten Danas 
wrote:

> +1 for updating the names. I like #contributing/#troubleshooting, and agree
> #best-practices would be a helpful addition.
>
> On Thu, Feb 8, 2024 at 7:50 AM Constance Martineau
>  wrote:
>
> > +1 for #contributing and leaving #troubleshooting. Shorter names in slack
> > are nice where possible.
> >
> > No strong opinion on the actual names. Agree that #development needs to
> be
> > renamed to something more obvious though.
> >
> > On Thu, Feb 8, 2024 at 9:30 AM Vincent Beck  wrote:
> >
> > > I am +1 in renaming these channels because, as said, most of messages
> in
> > > @development are nothing to do there.
> > >
> > > Though, I would just rename #development to #contributing. To me,
> > > #troubleshooting is already a good name and clear. But this is only my
> > > personal opinion. I am not against the names Jarek suggested.
> > >
> > > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > > Hey here,
> > > >
> > > > The number of "troubleshooting/best-practices" questions we have in
> > > > #development channel on Slack reached the level where we have more of
> > > those
> > > > than discussion about airflow development.
> > > >
> > > > There were few slack proposals, that we should change the names, but
> > it's
> > > > quite a significant change for everyone, so we need to discuss and
> have
> > > > [LAZY CONSENSUS] here.
> > > >
> > > > My proposal is to rename them like that (but I am totally open to
> other
> > > > ideas):
> > > >
> > > > #development -> #contriuting-to-airflow
> > > > #troubleshooting -> #troubleshooting-questions
> > > >
> > > > And I propose to create a new channel:
> > > >
> > > > #best-practices
> > > >
> > > > There users will be able to discuss best-practices on how to use
> > airflow
> > > > (it's not troubleshooting, it's more "please advise how I should do
> > > that).
> > > > We should make some announcements there, update our community pages
> and
> > > > welcome messages on slack to mention this channel.
> > > >
> > > > WDYT?
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> > >
> >
>

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

[Elad Kalif]

I'm -0 (binding)


On Thu, Feb 8, 2024 at 10:51 AM Akash Sharma <2akash111...@gmail.com> wrote:

> +1 (non binding)
>
> On Thu, 8 Feb 2024, 13:30 Jarek Potiuk,  wrote:
>
> > Since this is a controversial topic, just a kind reminder - the voting
> ends
> > today in ~ 8 hrs. If you feel (even somewhat) strongly about either
> > direction - that's the last time to cast the vote.
> >
> > And yes - fractional votes are possible :) - see
> >
> >
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
> > For Jed's case it **might** mean:  "-0.5: 'I don't like this idea, but I
> > can't find any rational justification for my feelings.'"
> >
> > J.
> >
> > On Wed, Feb 7, 2024 at 5:12 AM Amogh Desai 
> > wrote:
> >
> > > Love the vote from @Jed Cunningham  here!
> > >
> > > On Wed, Feb 7, 2024 at 3:05 AM Jed Cunningham <
> jedcunning...@apache.org>
> > > wrote:
> > >
> > > > -0.5
> > > >
> > >
> >
>

Re: [DISCUSS] Rename channels on slack

[Kenten Danas]

+1 for updating the names. I like #contributing/#troubleshooting, and agree
#best-practices would be a helpful addition.

On Thu, Feb 8, 2024 at 7:50 AM Constance Martineau
 wrote:

> +1 for #contributing and leaving #troubleshooting. Shorter names in slack
> are nice where possible.
>
> No strong opinion on the actual names. Agree that #development needs to be
> renamed to something more obvious though.
>
> On Thu, Feb 8, 2024 at 9:30 AM Vincent Beck  wrote:
>
> > I am +1 in renaming these channels because, as said, most of messages in
> > @development are nothing to do there.
> >
> > Though, I would just rename #development to #contributing. To me,
> > #troubleshooting is already a good name and clear. But this is only my
> > personal opinion. I am not against the names Jarek suggested.
> >
> > On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > > Hey here,
> > >
> > > The number of "troubleshooting/best-practices" questions we have in
> > > #development channel on Slack reached the level where we have more of
> > those
> > > than discussion about airflow development.
> > >
> > > There were few slack proposals, that we should change the names, but
> it's
> > > quite a significant change for everyone, so we need to discuss and have
> > > [LAZY CONSENSUS] here.
> > >
> > > My proposal is to rename them like that (but I am totally open to other
> > > ideas):
> > >
> > > #development -> #contriuting-to-airflow
> > > #troubleshooting -> #troubleshooting-questions
> > >
> > > And I propose to create a new channel:
> > >
> > > #best-practices
> > >
> > > There users will be able to discuss best-practices on how to use
> airflow
> > > (it's not troubleshooting, it's more "please advise how I should do
> > that).
> > > We should make some announcements there, update our community pages and
> > > welcome messages on slack to mention this channel.
> > >
> > > WDYT?
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > For additional commands, e-mail: dev-h...@airflow.apache.org
> >
> >
>

Re: [DISCUSS] Rename channels on slack

[Constance Martineau]

+1 for #contributing and leaving #troubleshooting. Shorter names in slack
are nice where possible.

No strong opinion on the actual names. Agree that #development needs to be
renamed to something more obvious though.

On Thu, Feb 8, 2024 at 9:30 AM Vincent Beck  wrote:

> I am +1 in renaming these channels because, as said, most of messages in
> @development are nothing to do there.
>
> Though, I would just rename #development to #contributing. To me,
> #troubleshooting is already a good name and clear. But this is only my
> personal opinion. I am not against the names Jarek suggested.
>
> On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> > Hey here,
> >
> > The number of "troubleshooting/best-practices" questions we have in
> > #development channel on Slack reached the level where we have more of
> those
> > than discussion about airflow development.
> >
> > There were few slack proposals, that we should change the names, but it's
> > quite a significant change for everyone, so we need to discuss and have
> > [LAZY CONSENSUS] here.
> >
> > My proposal is to rename them like that (but I am totally open to other
> > ideas):
> >
> > #development -> #contriuting-to-airflow
> > #troubleshooting -> #troubleshooting-questions
> >
> > And I propose to create a new channel:
> >
> > #best-practices
> >
> > There users will be able to discuss best-practices on how to use airflow
> > (it's not troubleshooting, it's more "please advise how I should do
> that).
> > We should make some announcements there, update our community pages and
> > welcome messages on slack to mention this channel.
> >
> > WDYT?
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> For additional commands, e-mail: dev-h...@airflow.apache.org
>
>

Re: [DISCUSS] Rename channels on slack

[Vincent Beck]

I am +1 in renaming these channels because, as said, most of messages in 
@development are nothing to do there.

Though, I would just rename #development to #contributing. To me, 
#troubleshooting is already a good name and clear. But this is only my personal 
opinion. I am not against the names Jarek suggested.

On 2024/02/08 11:54:34 Jarek Potiuk wrote:
> Hey here,
> 
> The number of "troubleshooting/best-practices" questions we have in
> #development channel on Slack reached the level where we have more of those
> than discussion about airflow development.
> 
> There were few slack proposals, that we should change the names, but it's
> quite a significant change for everyone, so we need to discuss and have
> [LAZY CONSENSUS] here.
> 
> My proposal is to rename them like that (but I am totally open to other
> ideas):
> 
> #development -> #contriuting-to-airflow
> #troubleshooting -> #troubleshooting-questions
> 
> And I propose to create a new channel:
> 
> #best-practices
> 
> There users will be able to discuss best-practices on how to use airflow
> (it's not troubleshooting, it's more "please advise how I should do that).
> We should make some announcements there, update our community pages and
> welcome messages on slack to mention this channel.
> 
> WDYT?
> 

-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

[DISCUSS] Rename channels on slack

[Jarek Potiuk]

Hey here,

The number of "troubleshooting/best-practices" questions we have in
#development channel on Slack reached the level where we have more of those
than discussion about airflow development.

There were few slack proposals, that we should change the names, but it's
quite a significant change for everyone, so we need to discuss and have
[LAZY CONSENSUS] here.

My proposal is to rename them like that (but I am totally open to other
ideas):

#development -> #contriuting-to-airflow
#troubleshooting -> #troubleshooting-questions

And I propose to create a new channel:

#best-practices

There users will be able to discuss best-practices on how to use airflow
(it's not troubleshooting, it's more "please advise how I should do that).
We should make some announcements there, update our community pages and
welcome messages on slack to mention this channel.

WDYT?

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

[Akash Sharma]

+1 (non binding)

On Thu, 8 Feb 2024, 13:30 Jarek Potiuk,  wrote:

> Since this is a controversial topic, just a kind reminder - the voting ends
> today in ~ 8 hrs. If you feel (even somewhat) strongly about either
> direction - that's the last time to cast the vote.
>
> And yes - fractional votes are possible :) - see
>
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
> For Jed's case it **might** mean:  "-0.5: 'I don't like this idea, but I
> can't find any rational justification for my feelings.'"
>
> J.
>
> On Wed, Feb 7, 2024 at 5:12 AM Amogh Desai 
> wrote:
>
> > Love the vote from @Jed Cunningham  here!
> >
> > On Wed, Feb 7, 2024 at 3:05 AM Jed Cunningham 
> > wrote:
> >
> > > -0.5
> > >
> >
>

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

[Jarek Potiuk]

Since this is a controversial topic, just a kind reminder - the voting ends
today in ~ 8 hrs. If you feel (even somewhat) strongly about either
direction - that's the last time to cast the vote.

And yes - fractional votes are possible :) - see
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
For Jed's case it **might** mean:  "-0.5: 'I don't like this idea, but I
can't find any rational justification for my feelings.'"

J.

On Wed, Feb 7, 2024 at 5:12 AM Amogh Desai  wrote:

> Love the vote from @Jed Cunningham  here!
>
> On Wed, Feb 7, 2024 at 3:05 AM Jed Cunningham 
> wrote:
>
> > -0.5
> >
>