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

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

I'm -0 (binding) On Thu, Feb 8, 2024 at 10:51 AM Akash Sharma <2akash111...@gmail.com> wrote: > +1 (non binding) > > On Thu, 8 Feb 2024, 13:30 Jarek Potiuk, wrote: > > > Since this is a controversial topic, just a kind reminder - the voting > ends > > today in ~ 8 hrs. If you feel (even

[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

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

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+1 (non binding) On Thu, 8 Feb 2024, 13:30 Jarek Potiuk, wrote: > Since this is a controversial topic, just a kind reminder - the voting ends > today in ~ 8 hrs. If you feel (even somewhat) strongly about either > direction - that's the last time to cast the vote. > > And yes - fractional votes

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

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

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

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

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

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

[VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

Hello Apache Airflow Community, This is a call for the vote to release Helm Chart version 1.12.0. The release candidate is available at: https://dist.apache.org/repos/dist/dev/airflow/helm-chart/1.12.0rc1/ airflow-chart-1.12.0-source.tar.gz - is the "main source release" that comes with INSTALL

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

[RESULT] [VOTE] "Require conversation resolution" setting in PRs as permanent solution

Hello everyone, Summary of the vote in https://lists.apache.org/thread/5m45dz860ovg4zyvrqscz8m1mnmmrn1g 5 binding (+1) votes: * Jarek Potiuk * Amogh Desai * Pankaj Koti * Jens Scheffer * Hussein Awala 2 binding (-1) votes: * Bolke de Bruin * Ash Berlin-Taylor 1 binding (-0.5) votes: * Jed

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

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

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.

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

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

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

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

+0 (non-binding) Best, Wei > On Feb 8, 2024, at 11:15 PM, Elad Kalif wrote: > > I'm -0 (binding) > > > On Thu, Feb 8, 2024 at 10:51 AM Akash Sharma <2akash111...@gmail.com> wrote: > >> +1 (non binding) >> >> On Thu, 8 Feb 2024, 13:30 Jarek Potiuk, wrote: >> >>> Since this is a

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

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

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

Re: [VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

+1 (binding):- checked signatures, checksums, licenses and compared content of the packages. Unfortunately it seems that the binary reproduction is still not fully working - there is some difference in "tar" layer run by Jed and myself, so I will need to do some extra checks. It's not a blocker

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 From: Vincent Beck Sent: Thursday, February 8, 2024 3:29:24

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

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

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

Since this is a controversial topic, just a kind reminder - the voting ends today in ~ 8 hrs. If you feel (even somewhat) strongly about either direction - that's the last time to cast the vote. And yes - fractional votes are possible :) - see