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 <vincb...@apache.org> Sent: Thursday, February 8, 2024 3:29:24 PM To: dev@airflow.apache.org <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
