+1

On Sun, Jul 15, 2018, 20:12 Maxime Beauchemin <maximebeauche...@gmail.com>
wrote:

> +1
>
> On Tue, Jul 10, 2018 at 1:09 PM Sid Anand <san...@apache.org> wrote:
>
> > +1
> >
> > On Tue, Jul 10, 2018 at 1:02 PM George Leslie-Waksman
> > <geo...@cloverhealth.com.invalid> wrote:
> >
> > > +1
> > >
> > > On Tue, Jul 10, 2018 at 11:50 AM Jakob Homan <jgho...@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
> > > >
> > >
> >
>

Reply via email to