___
> > > > From: Jarek Potiuk
> > > > Sent: Monday, February 12, 2024 3:37:35 AM
> > > > To: dev@airflow.apache.org
> > > > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels
> on
> > > > slack
> > &g
> > > I'm happy with that set of names +1
> > >
> > >
> > > From: Jarek Potiuk
> > > Sent: Monday, February 12, 2024 3:37:35 AM
> > > To: dev@airflow.apache.org
> > > Subject: RE: [EXTERNAL] [COURRIEL
day, February 12, 2024 3:37:35 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 op
t; > I'll throw #contributors into the ring as a name for the new
> > development
> > > > channel. I like naming it after a persona. Then as a user you know
> that
> > > if
> > > > you're trying to contribute that's where you should hang out.
> > > &
I'm happy with that set of names +1
From: Jarek Potiuk
Sent: Monday, February 12, 2024 3:37:35 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on slack
CAUTION: This email originated from outside
ng to contribute that's where you should hang out.
> > >
> > >
> > > From: Aritra Basu
> > > Sent: Thursday, February 8, 2024 9:50:42 PM
> > > To: dev@airflow.apache.org
> > > Subject: RE: [EXTERNAL] [COURRIEL EXTE
>
> > From: Aritra Basu
> > Sent: Thursday, February 8, 2024 9:50:42 PM
> > To: dev@airflow.apache.org
> > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on
> > slack
> >
> > CAUTION: This
at's where you should hang out.
>
>
> From: Aritra Basu
> Sent: Thursday, February 8, 2024 9:50:42 PM
> To: dev@airflow.apache.org
> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on
> slack
>
> CAUTION: This email originated from outside of the orga
@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
gt; > >> > #random
> > >> > #first-pr-support
> > >> >
> > >> > Or maybe someone can propose a better name for #contributing that is
> > >> less
> > >> > ambiguous?
> > >> >
> > >> > J.
> >
;
> >> > 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 (
ens (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
b 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.
>> > >
>>
gt; > ____
> > 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 i
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?
--
gainst Jarek but shorter is
> better.
>
> Sent from Outlook for iOS<https://aka.ms/o0ukef>
>
> From: Vincent Beck
> Sent: Thursday, February 8, 2024 3:29:24 PM
> To: dev@airflow.apache.org
> Subject: Re: [DISCUSS] Rename chann
: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 goo
+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...
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.
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
ame purpose?
> >
> >
> >
> > - ferruzzi
> >
> >
> > ____
> > From: Jed Cunningham
> > Sent: Thursday, February 8, 2024 8:36 AM
> > To: dev@airflow.apache.org
> > Subject: RE: [EXTERNAL] [COURRIEL EX
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
>
> C
: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
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
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
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
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
+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
+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
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
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
31 matches
Mail list logo
