You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Jakob Homan <jg...@gmail.com> on 2018/07/10 18:50:00 UTC
[DISCUSS] AIP - Time for Airflow Improvement Proposals?
Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to
document and gather consensus on large changes to the code base. Some
examples:
* Kafka Improvement Proposals (KIP) -
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
* Flink Improvement Proposal (FLIP) -
https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
* Spark Improvement Proposal (SPIP) -
https://spark.apache.org/improvement-proposals.html
We've got a few changes that have been discussed, either on the
list/JIRA (good) or in private (bad -
https://incubator.apache.org/guides/committer.html#mailing_lists) that
are of a magnitude that they may benefit from some version of this
process. Examples:
* The in-progress plan to refactor out connectors and hooks (AIRFLOW-2732)
* K8S deployment operator proposal
* Initial Design for Supporting fine-grained Connection encryption
The benefits of this approach is that the design is hosted somewhere
less ephemeral and more editable than email. It also provides a
framework for documenting and confirming consensus through the whole
community.
What do y'all think?
-Jakob
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Bolke de Bruin <bd...@gmail.com>.
Here you go:
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals
B.
Verstuurd vanaf mijn iPad
> Op 31 jul. 2018 om 06:49 heeft Tao Feng <fe...@gmail.com> het volgende geschreven:
>
> Hey Jakob,
>
> Are we going to start AIF for airflow? Currently it is a little bit hard to
> find out the proposals for different enhancement. It would be great if we
> could consolidate and put them in a central place(e.g like airflow wiki).
>
> Thanks,
> -Tao
>
> On Tue, Jul 17, 2018 at 10:14 PM, Chao-Han Tsai <mi...@gmail.com>
> wrote:
>
>> +1
>>
>>> On Tue, Jul 17, 2018 at 3:49 PM, Jin Chang <ji...@lyft.com> wrote:
>>>
>>> +1
>>>
>>>> On Tue, Jul 17, 2018 at 3:26 PM, Tao Feng <fe...@gmail.com> wrote:
>>>>
>>>> +1, should we put them in airflow wiki space(like kafka(kip)) or google
>>> doc
>>>> or email?
>>>>
>>>> On Sun, Jul 15, 2018 at 11:24 AM, Arthur Wiedmer <
>>> arthur.wiedmer@gmail.com
>>>>>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <
>>>> maximebeauchemin@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org>
>> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
>>>>>>> <ge...@cloverhealth.com.invalid> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <
>> jghoman@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Lots of Apache projects use ?IPs - Whatever Improvement
>>> Proposal
>>>> -
>>>>> to
>>>>>>>>> document and gather consensus on large changes to the code
>>> base.
>>>>>> Some
>>>>>>>>> examples:
>>>>>>>>> * Kafka Improvement Proposals (KIP) -
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/KAFKA/
>>>>> Kafka+Improvement+Proposals
>>>>>>>>> * Flink Improvement Proposal (FLIP) -
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/FLINK/
>>>>> Flink+Improvement+Proposals
>>>>>>>>> * Spark Improvement Proposal (SPIP) -
>>>>>>>>> https://spark.apache.org/improvement-proposals.html
>>>>>>>>>
>>>>>>>>> We've got a few changes that have been discussed, either on
>> the
>>>>>>>>> list/JIRA (good) or in private (bad -
>>>>>>>>> https://incubator.apache.org/guides/committer.html#mailing_
>>> lists
>>>> )
>>>>>> that
>>>>>>>>> are of a magnitude that they may benefit from some version of
>>>> this
>>>>>>>>> process. Examples:
>>>>>>>>> * The in-progress plan to refactor out connectors and
>> hooks
>>>>>>>>> (AIRFLOW-2732)
>>>>>>>>> * K8S deployment operator proposal
>>>>>>>>> * Initial Design for Supporting fine-grained Connection
>>>>> encryption
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The benefits of this approach is that the design is hosted
>>>>> somewhere
>>>>>>>>> less ephemeral and more editable than email. It also
>> provides
>>> a
>>>>>>>>> framework for documenting and confirming consensus through
>> the
>>>>> whole
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> What do y'all think?
>>>>>>>>>
>>>>>>>>> -Jakob
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>> --
>>
>> Chao-Han Tsai
>>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Tao Feng <fe...@gmail.com>.
Hey Jakob,
Are we going to start AIF for airflow? Currently it is a little bit hard to
find out the proposals for different enhancement. It would be great if we
could consolidate and put them in a central place(e.g like airflow wiki).
Thanks,
-Tao
On Tue, Jul 17, 2018 at 10:14 PM, Chao-Han Tsai <mi...@gmail.com>
wrote:
> +1
>
> On Tue, Jul 17, 2018 at 3:49 PM, Jin Chang <ji...@lyft.com> wrote:
>
> > +1
> >
> > On Tue, Jul 17, 2018 at 3:26 PM, Tao Feng <fe...@gmail.com> wrote:
> >
> > > +1, should we put them in airflow wiki space(like kafka(kip)) or google
> > doc
> > > or email?
> > >
> > > On Sun, Jul 15, 2018 at 11:24 AM, Arthur Wiedmer <
> > arthur.wiedmer@gmail.com
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <
> > > maximebeauchemin@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org>
> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > > > > > <ge...@cloverhealth.com.invalid> wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <
> jghoman@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Lots of Apache projects use ?IPs - Whatever Improvement
> > Proposal
> > > -
> > > > to
> > > > > > > > document and gather consensus on large changes to the code
> > base.
> > > > > Some
> > > > > > > > examples:
> > > > > > > > * Kafka Improvement Proposals (KIP) -
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > https://cwiki.apache.org/confluence/display/KAFKA/
> > > > Kafka+Improvement+Proposals
> > > > > > > > * Flink Improvement Proposal (FLIP) -
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > https://cwiki.apache.org/confluence/display/FLINK/
> > > > Flink+Improvement+Proposals
> > > > > > > > * Spark Improvement Proposal (SPIP) -
> > > > > > > > https://spark.apache.org/improvement-proposals.html
> > > > > > > >
> > > > > > > > We've got a few changes that have been discussed, either on
> the
> > > > > > > > list/JIRA (good) or in private (bad -
> > > > > > > > https://incubator.apache.org/guides/committer.html#mailing_
> > lists
> > > )
> > > > > that
> > > > > > > > are of a magnitude that they may benefit from some version of
> > > this
> > > > > > > > process. Examples:
> > > > > > > > * The in-progress plan to refactor out connectors and
> hooks
> > > > > > > > (AIRFLOW-2732)
> > > > > > > > * K8S deployment operator proposal
> > > > > > > > * Initial Design for Supporting fine-grained Connection
> > > > encryption
> > > > > > > >
> > > > > > > >
> > > > > > > > The benefits of this approach is that the design is hosted
> > > > somewhere
> > > > > > > > less ephemeral and more editable than email. It also
> provides
> > a
> > > > > > > > framework for documenting and confirming consensus through
> the
> > > > whole
> > > > > > > > community.
> > > > > > > >
> > > > > > > > What do y'all think?
> > > > > > > >
> > > > > > > > -Jakob
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
>
> Chao-Han Tsai
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Chao-Han Tsai <mi...@gmail.com>.
+1
On Tue, Jul 17, 2018 at 3:49 PM, Jin Chang <ji...@lyft.com> wrote:
> +1
>
> On Tue, Jul 17, 2018 at 3:26 PM, Tao Feng <fe...@gmail.com> wrote:
>
> > +1, should we put them in airflow wiki space(like kafka(kip)) or google
> doc
> > or email?
> >
> > On Sun, Jul 15, 2018 at 11:24 AM, Arthur Wiedmer <
> arthur.wiedmer@gmail.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <
> > maximebeauchemin@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > > > > <ge...@cloverhealth.com.invalid> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Lots of Apache projects use ?IPs - Whatever Improvement
> Proposal
> > -
> > > to
> > > > > > > document and gather consensus on large changes to the code
> base.
> > > > Some
> > > > > > > examples:
> > > > > > > * Kafka Improvement Proposals (KIP) -
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > https://cwiki.apache.org/confluence/display/KAFKA/
> > > Kafka+Improvement+Proposals
> > > > > > > * Flink Improvement Proposal (FLIP) -
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > https://cwiki.apache.org/confluence/display/FLINK/
> > > Flink+Improvement+Proposals
> > > > > > > * Spark Improvement Proposal (SPIP) -
> > > > > > > https://spark.apache.org/improvement-proposals.html
> > > > > > >
> > > > > > > We've got a few changes that have been discussed, either on the
> > > > > > > list/JIRA (good) or in private (bad -
> > > > > > > https://incubator.apache.org/guides/committer.html#mailing_
> lists
> > )
> > > > that
> > > > > > > are of a magnitude that they may benefit from some version of
> > this
> > > > > > > process. Examples:
> > > > > > > * The in-progress plan to refactor out connectors and hooks
> > > > > > > (AIRFLOW-2732)
> > > > > > > * K8S deployment operator proposal
> > > > > > > * Initial Design for Supporting fine-grained Connection
> > > encryption
> > > > > > >
> > > > > > >
> > > > > > > The benefits of this approach is that the design is hosted
> > > somewhere
> > > > > > > less ephemeral and more editable than email. It also provides
> a
> > > > > > > framework for documenting and confirming consensus through the
> > > whole
> > > > > > > community.
> > > > > > >
> > > > > > > What do y'all think?
> > > > > > >
> > > > > > > -Jakob
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Chao-Han Tsai
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Jin Chang <ji...@lyft.com>.
+1
On Tue, Jul 17, 2018 at 3:26 PM, Tao Feng <fe...@gmail.com> wrote:
> +1, should we put them in airflow wiki space(like kafka(kip)) or google doc
> or email?
>
> On Sun, Jul 15, 2018 at 11:24 AM, Arthur Wiedmer <arthur.wiedmer@gmail.com
> >
> wrote:
>
> > +1
> >
> > On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <
> maximebeauchemin@gmail.com>
> > wrote:
> >
> > > +1
> > >
> > > On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org> wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > > > <ge...@cloverhealth.com.invalid> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Lots of Apache projects use ?IPs - Whatever Improvement Proposal
> -
> > to
> > > > > > document and gather consensus on large changes to the code base.
> > > Some
> > > > > > examples:
> > > > > > * Kafka Improvement Proposals (KIP) -
> > > > > >
> > > > > >
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/
> > Kafka+Improvement+Proposals
> > > > > > * Flink Improvement Proposal (FLIP) -
> > > > > >
> > > > > >
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/FLINK/
> > Flink+Improvement+Proposals
> > > > > > * Spark Improvement Proposal (SPIP) -
> > > > > > https://spark.apache.org/improvement-proposals.html
> > > > > >
> > > > > > We've got a few changes that have been discussed, either on the
> > > > > > list/JIRA (good) or in private (bad -
> > > > > > https://incubator.apache.org/guides/committer.html#mailing_lists
> )
> > > that
> > > > > > are of a magnitude that they may benefit from some version of
> this
> > > > > > process. Examples:
> > > > > > * The in-progress plan to refactor out connectors and hooks
> > > > > > (AIRFLOW-2732)
> > > > > > * K8S deployment operator proposal
> > > > > > * Initial Design for Supporting fine-grained Connection
> > encryption
> > > > > >
> > > > > >
> > > > > > The benefits of this approach is that the design is hosted
> > somewhere
> > > > > > less ephemeral and more editable than email. It also provides a
> > > > > > framework for documenting and confirming consensus through the
> > whole
> > > > > > community.
> > > > > >
> > > > > > What do y'all think?
> > > > > >
> > > > > > -Jakob
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Tao Feng <fe...@gmail.com>.
+1, should we put them in airflow wiki space(like kafka(kip)) or google doc
or email?
On Sun, Jul 15, 2018 at 11:24 AM, Arthur Wiedmer <ar...@gmail.com>
wrote:
> +1
>
> On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <ma...@gmail.com>
> wrote:
>
> > +1
> >
> > On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org> wrote:
> >
> > > +1
> > >
> > > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > > <ge...@cloverhealth.com.invalid> wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com>
> > wrote:
> > > >
> > > > > Lots of Apache projects use ?IPs - Whatever Improvement Proposal -
> to
> > > > > document and gather consensus on large changes to the code base.
> > Some
> > > > > examples:
> > > > > * Kafka Improvement Proposals (KIP) -
> > > > >
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/
> Kafka+Improvement+Proposals
> > > > > * Flink Improvement Proposal (FLIP) -
> > > > >
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/FLINK/
> Flink+Improvement+Proposals
> > > > > * Spark Improvement Proposal (SPIP) -
> > > > > https://spark.apache.org/improvement-proposals.html
> > > > >
> > > > > We've got a few changes that have been discussed, either on the
> > > > > list/JIRA (good) or in private (bad -
> > > > > https://incubator.apache.org/guides/committer.html#mailing_lists)
> > that
> > > > > are of a magnitude that they may benefit from some version of this
> > > > > process. Examples:
> > > > > * The in-progress plan to refactor out connectors and hooks
> > > > > (AIRFLOW-2732)
> > > > > * K8S deployment operator proposal
> > > > > * Initial Design for Supporting fine-grained Connection
> encryption
> > > > >
> > > > >
> > > > > The benefits of this approach is that the design is hosted
> somewhere
> > > > > less ephemeral and more editable than email. It also provides a
> > > > > framework for documenting and confirming consensus through the
> whole
> > > > > community.
> > > > >
> > > > > What do y'all think?
> > > > >
> > > > > -Jakob
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Arthur Wiedmer <ar...@gmail.com>.
+1
On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <ma...@gmail.com>
wrote:
> +1
>
> On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org> wrote:
>
> > +1
> >
> > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > <ge...@cloverhealth.com.invalid> wrote:
> >
> > > +1
> > >
> > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com>
> wrote:
> > >
> > > > Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to
> > > > document and gather consensus on large changes to the code base.
> Some
> > > > examples:
> > > > * Kafka Improvement Proposals (KIP) -
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > > * Flink Improvement Proposal (FLIP) -
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
> > > > * Spark Improvement Proposal (SPIP) -
> > > > https://spark.apache.org/improvement-proposals.html
> > > >
> > > > We've got a few changes that have been discussed, either on the
> > > > list/JIRA (good) or in private (bad -
> > > > https://incubator.apache.org/guides/committer.html#mailing_lists)
> that
> > > > are of a magnitude that they may benefit from some version of this
> > > > process. Examples:
> > > > * The in-progress plan to refactor out connectors and hooks
> > > > (AIRFLOW-2732)
> > > > * K8S deployment operator proposal
> > > > * Initial Design for Supporting fine-grained Connection encryption
> > > >
> > > >
> > > > The benefits of this approach is that the design is hosted somewhere
> > > > less ephemeral and more editable than email. It also provides a
> > > > framework for documenting and confirming consensus through the whole
> > > > community.
> > > >
> > > > What do y'all think?
> > > >
> > > > -Jakob
> > > >
> > >
> >
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Maxime Beauchemin <ma...@gmail.com>.
+1
On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <sa...@apache.org> wrote:
> +1
>
> On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> <ge...@cloverhealth.com.invalid> wrote:
>
> > +1
> >
> > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com> wrote:
> >
> > > Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to
> > > document and gather consensus on large changes to the code base. Some
> > > examples:
> > > * Kafka Improvement Proposals (KIP) -
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > * Flink Improvement Proposal (FLIP) -
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
> > > * Spark Improvement Proposal (SPIP) -
> > > https://spark.apache.org/improvement-proposals.html
> > >
> > > We've got a few changes that have been discussed, either on the
> > > list/JIRA (good) or in private (bad -
> > > https://incubator.apache.org/guides/committer.html#mailing_lists) that
> > > are of a magnitude that they may benefit from some version of this
> > > process. Examples:
> > > * The in-progress plan to refactor out connectors and hooks
> > > (AIRFLOW-2732)
> > > * K8S deployment operator proposal
> > > * Initial Design for Supporting fine-grained Connection encryption
> > >
> > >
> > > The benefits of this approach is that the design is hosted somewhere
> > > less ephemeral and more editable than email. It also provides a
> > > framework for documenting and confirming consensus through the whole
> > > community.
> > >
> > > What do y'all think?
> > >
> > > -Jakob
> > >
> >
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by Sid Anand <sa...@apache.org>.
+1
On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
<ge...@cloverhealth.com.invalid> wrote:
> +1
>
> On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com> wrote:
>
> > Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to
> > document and gather consensus on large changes to the code base. Some
> > examples:
> > * Kafka Improvement Proposals (KIP) -
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > * Flink Improvement Proposal (FLIP) -
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
> > * Spark Improvement Proposal (SPIP) -
> > https://spark.apache.org/improvement-proposals.html
> >
> > We've got a few changes that have been discussed, either on the
> > list/JIRA (good) or in private (bad -
> > https://incubator.apache.org/guides/committer.html#mailing_lists) that
> > are of a magnitude that they may benefit from some version of this
> > process. Examples:
> > * The in-progress plan to refactor out connectors and hooks
> > (AIRFLOW-2732)
> > * K8S deployment operator proposal
> > * Initial Design for Supporting fine-grained Connection encryption
> >
> >
> > The benefits of this approach is that the design is hosted somewhere
> > less ephemeral and more editable than email. It also provides a
> > framework for documenting and confirming consensus through the whole
> > community.
> >
> > What do y'all think?
> >
> > -Jakob
> >
>
Re: [DISCUSS] AIP - Time for Airflow Improvement Proposals?
Posted by George Leslie-Waksman <ge...@cloverhealth.com.INVALID>.
+1
On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jg...@gmail.com> wrote:
> Lots of Apache projects use ?IPs - Whatever Improvement Proposal - to
> document and gather consensus on large changes to the code base. Some
> examples:
> * Kafka Improvement Proposals (KIP) -
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> * Flink Improvement Proposal (FLIP) -
>
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
> * Spark Improvement Proposal (SPIP) -
> https://spark.apache.org/improvement-proposals.html
>
> We've got a few changes that have been discussed, either on the
> list/JIRA (good) or in private (bad -
> https://incubator.apache.org/guides/committer.html#mailing_lists) that
> are of a magnitude that they may benefit from some version of this
> process. Examples:
> * The in-progress plan to refactor out connectors and hooks
> (AIRFLOW-2732)
> * K8S deployment operator proposal
> * Initial Design for Supporting fine-grained Connection encryption
>
>
> The benefits of this approach is that the design is hosted somewhere
> less ephemeral and more editable than email. It also provides a
> framework for documenting and confirming consensus through the whole
> community.
>
> What do y'all think?
>
> -Jakob
>