[LAZY CONSENSUS] Accept Kafka Provider

[Jarek Potiuk <ja...@potiuk.com>]

Hey everyone,

Following the discussion in
https://lists.apache.org/thread/xf4wn1hw08cs725fp962252y7mmptk3b and the
proposed draft policies for accepting new providers (
https://github.com/apache/airflow/pull/30657) I would like to propose a
LAZY CONSENSUS on accepting the Kafka Provider as a new community managed
provider.

The Kafka's Provider's PR is https://github.com/apache/airflow/pull/30175
and Dylan has been iterating over it for about a month now to get to the
(great IMHO) state that we want our new providers to have:

* popular software with  vendor-neutral governance (Kafka is our sister
project in the ASF)
* great quality code
* well documented and tested
* has integration tests built-in Breeze and our CI so we  can test it with
"real" Kafka in an instant and easily upgrade to newer versions of Kafka if
needed
* it has been proven to work at Astronomer in their provider - Astronomer
is donating it to us

If there are no objections, we will merge it (pending all approvals).

Unless there are objections, I would love to merge that one before the
first RC of Airflow 2.6.0 is released on Monday afternoon (likely). To
include "kafka" extra and constraints there.

So I propose to keep the lazy consensus running till then (Monday 1 pm CET,
17th of April 2023).
If there are any objections and discussion is needed, we can of course
prolong that and conclude it later - just respond to that email asking for
it.

J.

Re: [LAZY CONSENSUS] Accept Kafka Provider

[Jarek Potiuk <ja...@potiuk.com>]

Hello everyone,

We have not yet merged the change as it is still being reviewed. also 2.6.0
RC did not yet happen, so I kept the consensus running. 72H passed few
hours ago and there were no objections, so the consensus has been reached.
We will merge and release Kafka provider soon.

On Sat, Apr 15, 2023 at 1:02 PM Jarek Potiuk <ja...@potiuk.com> wrote:

> Hey everyone,
>
> Following the discussion in
> https://lists.apache.org/thread/xf4wn1hw08cs725fp962252y7mmptk3b and the
> proposed draft policies for accepting new providers (
> https://github.com/apache/airflow/pull/30657) I would like to propose a
> LAZY CONSENSUS on accepting the Kafka Provider as a new community managed
> provider.
>
> The Kafka's Provider's PR is https://github.com/apache/airflow/pull/30175
> and Dylan has been iterating over it for about a month now to get to the
> (great IMHO) state that we want our new providers to have:
>
> * popular software with  vendor-neutral governance (Kafka is our sister
> project in the ASF)
> * great quality code
> * well documented and tested
> * has integration tests built-in Breeze and our CI so we  can test it with
> "real" Kafka in an instant and easily upgrade to newer versions of Kafka if
> needed
> * it has been proven to work at Astronomer in their provider - Astronomer
> is donating it to us
>
> If there are no objections, we will merge it (pending all approvals).
>
> Unless there are objections, I would love to merge that one before the
> first RC of Airflow 2.6.0 is released on Monday afternoon (likely). To
> include "kafka" extra and constraints there.
>
> So I propose to keep the lazy consensus running till then (Monday 1 pm
> CET, 17th of April 2023).
> If there are any objections and discussion is needed, we can of course
> prolong that and conclude it later - just respond to that email asking for
> it.
>
> J.
>