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 <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 > > > > > > > > >
