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 <aritrabasu1...@gmail.com> 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 <amoghdesai....@gmail.com> 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 <ja...@potiuk.com> wrote: > > > #learn-contributing maybe ? > > > > On Fri, Feb 9, 2024 at 12:14 AM Jarek Potiuk <ja...@potiuk.com> 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 <vincb...@apache.org> > > 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) > > >> > <jens.scheff...@de.bosch.com.invalid> 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 <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 > > >> > > > > >> > > > > >> > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > >> For additional commands, e-mail: dev-h...@airflow.apache.org > > >> > > >> > > >
