Re: [DISCUSS] Rename channels on slack
Ok. Let me then start LAZY CONSENSUS :) On Mon, Feb 12, 2024 at 8:31 PM Aritra Basu wrote: > +1 the names sound good to me as well > > -- > Regards, > Aritra Basu > > On Tue, Feb 13, 2024, 12:45 AM Vincent Beck wrote: > > > +1 > > > > On 2024/02/12 19:12:05 Briana Okyere wrote: > > > Same, +1 > > > > > > On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko > > > > > wrote: > > > > > > > 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 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. > > > > > > > > > > > > > > > > Yeah. Precisely I think the persona is the key problem - similarly to > > the > > > > recent change in our community page > > https://airflow.apache.org/community/ > > > > where we split "Want to contribute?" and "Are you a user?" (and an > > > > observation that #development is in "user" section does not make it > > > > clearer). So I'd avoid "development" at all. > > > > > > > > I like Niko's idea about using personas as channel names. > > > > > > > > How about this - not very short, but pretty explicit: > > > > > > > > #contributors (with archiving current #development and announcement > > there) > > > > #new-contributors (renamed from #first-pr-support) > > > > #user-troubleshooting > > > > #user-best-practices (let's see how popular it will be - we can close > > it if > > > > not used) > > > > #random > > > > > > > > J. > > > > > > > > > > > > > > > > > > > > On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin > > wrote: > > > > > > > > > The challenge is the persona here. I bet people think that they are > > doing > > > > > "dev" on Airflow when writing dags :-). > > > > > > > > > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > > > > > wrote: > > > > > > > > > > > Love this thread. From my experience in community management (for > > > > > whatever > > > > > > it's worth), naming channels after personas is the way to go. I > > also > > > > > think > > > > > > we can consolidate some of these. I think: > > > > > > > > > > > > #dev-support -> from #development > > > > > > #troubleshooting > > > > > > #best-practices > > > > > > #random > > > > > > #first-pr-support --> change to #contributing > > > > > > > > > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of > > just > > > > > > > archiving the current development channel and starting fresh > > with a > > > > new > > > > > > > channel for contribution. There no manner of rebranding that we > > can > > > > do > > > > > to > > > > > > > save #development now, with that many folks in it. > > > > > > > > > > > > > > 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 > > > >
Re: [DISCUSS] Rename channels on slack
+1 the names sound good to me as well -- Regards, Aritra Basu On Tue, Feb 13, 2024, 12:45 AM Vincent Beck wrote: > +1 > > On 2024/02/12 19:12:05 Briana Okyere wrote: > > Same, +1 > > > > On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko > > > wrote: > > > > > 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 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. > > > > > > > > > > > > Yeah. Precisely I think the persona is the key problem - similarly to > the > > > recent change in our community page > https://airflow.apache.org/community/ > > > where we split "Want to contribute?" and "Are you a user?" (and an > > > observation that #development is in "user" section does not make it > > > clearer). So I'd avoid "development" at all. > > > > > > I like Niko's idea about using personas as channel names. > > > > > > How about this - not very short, but pretty explicit: > > > > > > #contributors (with archiving current #development and announcement > there) > > > #new-contributors (renamed from #first-pr-support) > > > #user-troubleshooting > > > #user-best-practices (let's see how popular it will be - we can close > it if > > > not used) > > > #random > > > > > > J. > > > > > > > > > > > > > > > On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin > wrote: > > > > > > > The challenge is the persona here. I bet people think that they are > doing > > > > "dev" on Airflow when writing dags :-). > > > > > > > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > > > > wrote: > > > > > > > > > Love this thread. From my experience in community management (for > > > > whatever > > > > > it's worth), naming channels after personas is the way to go. I > also > > > > think > > > > > we can consolidate some of these. I think: > > > > > > > > > > #dev-support -> from #development > > > > > #troubleshooting > > > > > #best-practices > > > > > #random > > > > > #first-pr-support --> change to #contributing > > > > > > > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > > > > > > > > > > wrote: > > > > > > > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of > just > > > > > > archiving the current development channel and starting fresh > with a > > > new > > > > > > channel for contribution. There no manner of rebranding that we > can > > > do > > > > to > > > > > > save #development now, with that many folks in it. > > > > > > > > > > > > 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. > > > > > > > > > > > > > > > > > > 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 organization. > Do > > >
Re: [DISCUSS] Rename channels on slack
+1 On 2024/02/12 19:12:05 Briana Okyere wrote: > Same, +1 > > On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko > wrote: > > > 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 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. > > > > > > > > Yeah. Precisely I think the persona is the key problem - similarly to the > > recent change in our community page https://airflow.apache.org/community/ > > where we split "Want to contribute?" and "Are you a user?" (and an > > observation that #development is in "user" section does not make it > > clearer). So I'd avoid "development" at all. > > > > I like Niko's idea about using personas as channel names. > > > > How about this - not very short, but pretty explicit: > > > > #contributors (with archiving current #development and announcement there) > > #new-contributors (renamed from #first-pr-support) > > #user-troubleshooting > > #user-best-practices (let's see how popular it will be - we can close it if > > not used) > > #random > > > > J. > > > > > > > > > > On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin wrote: > > > > > The challenge is the persona here. I bet people think that they are doing > > > "dev" on Airflow when writing dags :-). > > > > > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > > > wrote: > > > > > > > Love this thread. From my experience in community management (for > > > whatever > > > > it's worth), naming channels after personas is the way to go. I also > > > think > > > > we can consolidate some of these. I think: > > > > > > > > #dev-support -> from #development > > > > #troubleshooting > > > > #best-practices > > > > #random > > > > #first-pr-support --> change to #contributing > > > > > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > > > > > > > wrote: > > > > > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of just > > > > > archiving the current development channel and starting fresh with a > > new > > > > > channel for contribution. There no manner of rebranding that we can > > do > > > to > > > > > save #development now, with that many folks in it. > > > > > > > > > > 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. > > > > > > > > > > > > > > > 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 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. > > > > > > > > &
Re: [DISCUSS] Rename channels on slack
Same, +1 On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko wrote: > 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 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. > > > > Yeah. Precisely I think the persona is the key problem - similarly to the > recent change in our community page https://airflow.apache.org/community/ > where we split "Want to contribute?" and "Are you a user?" (and an > observation that #development is in "user" section does not make it > clearer). So I'd avoid "development" at all. > > I like Niko's idea about using personas as channel names. > > How about this - not very short, but pretty explicit: > > #contributors (with archiving current #development and announcement there) > #new-contributors (renamed from #first-pr-support) > #user-troubleshooting > #user-best-practices (let's see how popular it will be - we can close it if > not used) > #random > > J. > > > > > On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin wrote: > > > The challenge is the persona here. I bet people think that they are doing > > "dev" on Airflow when writing dags :-). > > > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > > wrote: > > > > > Love this thread. From my experience in community management (for > > whatever > > > it's worth), naming channels after personas is the way to go. I also > > think > > > we can consolidate some of these. I think: > > > > > > #dev-support -> from #development > > > #troubleshooting > > > #best-practices > > > #random > > > #first-pr-support --> change to #contributing > > > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > > > > wrote: > > > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of just > > > > archiving the current development channel and starting fresh with a > new > > > > channel for contribution. There no manner of rebranding that we can > do > > to > > > > save #development now, with that many folks in it. > > > > > > > > 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. > > > > > > > > > > > > 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 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. > > > > > > > > > > > > > > > > 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: > > > > > >
Re: [DISCUSS] Rename channels on slack
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 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. Yeah. Precisely I think the persona is the key problem - similarly to the recent change in our community page https://airflow.apache.org/community/ where we split "Want to contribute?" and "Are you a user?" (and an observation that #development is in "user" section does not make it clearer). So I'd avoid "development" at all. I like Niko's idea about using personas as channel names. How about this - not very short, but pretty explicit: #contributors (with archiving current #development and announcement there) #new-contributors (renamed from #first-pr-support) #user-troubleshooting #user-best-practices (let's see how popular it will be - we can close it if not used) #random J. On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin wrote: > The challenge is the persona here. I bet people think that they are doing > "dev" on Airflow when writing dags :-). > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > wrote: > > > Love this thread. From my experience in community management (for > whatever > > it's worth), naming channels after personas is the way to go. I also > think > > we can consolidate some of these. I think: > > > > #dev-support -> from #development > > #troubleshooting > > #best-practices > > #random > > #first-pr-support --> change to #contributing > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > wrote: > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of just > > > archiving the current development channel and starting fresh with a new > > > channel for contribution. There no manner of rebranding that we can do > to > > > save #development now, with that many folks in it. > > > > > > 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. > > > > > > > > > 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 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. > > > > > > > > > > > > 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 > >
Re: [DISCUSS] Rename channels on slack
Yeah. Precisely I think the persona is the key problem - similarly to the recent change in our community page https://airflow.apache.org/community/ where we split "Want to contribute?" and "Are you a user?" (and an observation that #development is in "user" section does not make it clearer). So I'd avoid "development" at all. I like Niko's idea about using personas as channel names. How about this - not very short, but pretty explicit: #contributors (with archiving current #development and announcement there) #new-contributors (renamed from #first-pr-support) #user-troubleshooting #user-best-practices (let's see how popular it will be - we can close it if not used) #random J. On Mon, Feb 12, 2024 at 12:22 PM Bolke de Bruin wrote: > The challenge is the persona here. I bet people think that they are doing > "dev" on Airflow when writing dags :-). > > On Fri, 9 Feb 2024 at 20:17, Briana Okyere > wrote: > > > Love this thread. From my experience in community management (for > whatever > > it's worth), naming channels after personas is the way to go. I also > think > > we can consolidate some of these. I think: > > > > #dev-support -> from #development > > #troubleshooting > > #best-practices > > #random > > #first-pr-support --> change to #contributing > > > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > > > > wrote: > > > > > I'm not too picky on the names, but I'm +5 to Jed's approach of just > > > archiving the current development channel and starting fresh with a new > > > channel for contribution. There no manner of rebranding that we can do > to > > > save #development now, with that many folks in it. > > > > > > 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. > > > > > > > > > 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 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. > > > > > > > > > > > > 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
Re: [DISCUSS] Rename channels on slack
The challenge is the persona here. I bet people think that they are doing "dev" on Airflow when writing dags :-). On Fri, 9 Feb 2024 at 20:17, Briana Okyere wrote: > Love this thread. From my experience in community management (for whatever > it's worth), naming channels after personas is the way to go. I also think > we can consolidate some of these. I think: > > #dev-support -> from #development > #troubleshooting > #best-practices > #random > #first-pr-support --> change to #contributing > > On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko > > wrote: > > > I'm not too picky on the names, but I'm +5 to Jed's approach of just > > archiving the current development channel and starting fresh with a new > > channel for contribution. There no manner of rebranding that we can do to > > save #development now, with that many folks in it. > > > > 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. > > > > > > 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 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. > > > > > > > > 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/ > > >
Re: [DISCUSS] Rename channels on slack
Love this thread. From my experience in community management (for whatever it's worth), naming channels after personas is the way to go. I also think we can consolidate some of these. I think: #dev-support -> from #development #troubleshooting #best-practices #random #first-pr-support --> change to #contributing On Fri, Feb 9, 2024 at 10:33 AM Oliveira, Niko wrote: > I'm not too picky on the names, but I'm +5 to Jed's approach of just > archiving the current development channel and starting fresh with a new > channel for contribution. There no manner of rebranding that we can do to > save #development now, with that many folks in it. > > 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. > > > 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 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. > > > > 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
Re: [DISCUSS] Rename channels on slack
I'm not too picky on the names, but I'm +5 to Jed's approach of just archiving the current development channel and starting fresh with a new channel for contribution. There no manner of rebranding that we can do to save #development now, with that many folks in it. 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. 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 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. 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<https://aka.ms/o
Re: [DISCUSS] Rename channels on slack
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<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 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, > > >> > > > > > >> > >
Re: [DISCUSS] Rename channels on slack
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<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 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: > 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<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 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
#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<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 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
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<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 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
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
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<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 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
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<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 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
+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: [DISCUSS] Rename channels on slack
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
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
>> 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
> 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
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
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
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 > > > > > > > > > > > > > >
Re: [DISCUSS] Rename channels on slack
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
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: [DISCUSS] Rename channels on slack
+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
+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
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
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?
