The great renaming is done now. The most important part that requires an
action - #development channel is now archived and if you want to continue
be involved in contributing - the #contributors channel is the right one to
subscribe to.

On Thu, Feb 15, 2024 at 8:14 PM Jarek Potiuk <ja...@potiuk.com> wrote:

> The lazy consensus has been reached. I will proceed with renaming!
>
> On Thu, Feb 15, 2024 at 3:50 PM Ryan Hatter
> <ryan.hat...@astronomer.io.invalid> wrote:
>
>> Ah! Great idea!
>>
>> On Tue, Feb 13, 2024 at 12:22 PM Akash Sharma <2akash111...@gmail.com>
>> wrote:
>>
>> > +1
>> >
>> > On Tue, 13 Feb 2024, 22:50 Briana Okyere,
>> > <briana.oky...@astronomer.io.invalid> wrote:
>> >
>> > > +1
>> > >
>> > > On Mon, Feb 12, 2024 at 11:42 AM Jarek Potiuk <ja...@potiuk.com>
>> wrote:
>> > >
>> > > > Hey here,
>> > > >
>> > > > Following the earlier discussion, I am calling for a lazy consensus
>> on
>> > > > renaming of our slack channels:
>> > > >
>> > > > #development -> *#contributors*
>> > > > #first-pr-support -> *#new-contributors*
>> > > > #troubleshooting -> *#user-troubleshooting*
>> > > > #random -> *#random* (hehe)
>> > > >
>> > > > The current #development channel will be archived and we will ask
>> > people
>> > > to
>> > > > add themselves to #contributors if they are working on contributing
>> to
>> > > > airflow. If they are starting their journey, they will should ask
>> > > questions
>> > > > in #new-contributors
>> > > >
>> > > > New channel: *#user-best-practices* - this is for sharing best
>> > practices
>> > > > with and between users. Let's see how popular it will be - we can
>> close
>> > > it
>> > > > if not used.
>> > > >
>> > > > Discussion was held here:
>> > > > https://lists.apache.org/thread/fjswvwg4ttbkr14bhq9s5xkc50h0qc76
>> > > >
>> > > > I will run the lazy consensus till Thursday, Feb 15th 2024, 8PM CET
>> (72
>> > > hrs
>> > > > from now).
>> > > >
>> > > > There is no need or expectation to respond to it if you are in
>> > agreement.
>> > > > Lack of response is a silent agreement.
>> > > >
>> > > > J.
>> > > >
>> > >
>> >
>>
>

Reply via email to