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 <aritrabasu1...@gmail.com> 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 <ken...@astronomer.io.invalid> > 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 > > <consta...@astronomer.io.invalid> 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 <vincb...@apache.org> > 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 > > > > > > > > > > > > > >
