[RESULT] [VOTE] Accept APISIX into Apache Incubator

[Ming]

Vote passed.

We got:
+1 binding (11)
Kevin Ratnasekera
Willem Jiang
Dave Fisher
Ted Liu
Liang Chen
Von Gosling
Furkan KAMACI
Justin Mclean
Mohammad Asif Siddiqui
Sheng Wu
Woonsan Ko

+1 non-binding (1)
Jeff Zhang

The vote thread:
https://lists.apache.org/thread.html/158d27f914831401e9d1d7efce96084fc8d8a87f0a27be1fe5ac43cd@%3Cgeneral.incubator.apache.org%3E

Thanks for the support and votes.

Re: [VOTE] Accept APISIX into Apache Incubator

[Jeff Zhang]

+1 （non-binding）

Woonsan Ko  于2019年10月14日周一 下午5:28写道：

> +1 (binding)
>
> Good luck!
>
> Woonsan
>
> On Thu, Oct 10, 2019 at 5:55 PM Ming  wrote:
> >
> > Hi all,
> >
> > After the discussion of APISIX proposal
> > (discussion thread:
> >
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E
> ),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring APISIX into Incubator
> >   [ ] +0, I don't care either way
> >   [ ] -1, do not bring APISIX into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > = APISIX Proposal =
> >
> > == Abstract ==
> >
> > APISIX is a cloud-native microservices API gateway, delivering the
> > ultimate performance, security,
> > open source and scalable platform for all your APIs and microservices.
> >
> > APISIX is based on OpenResty and etcd, and has dynamic routing and
> > plug-in hot loading,
> >  which is especially suitable for API management under micro-service
> system.
> >
> > == Proposal ==
> >
> > The goal of this proposal is to bring the existing APISIX
> >  codebase and existing developers
> > and community
> > into the Apache Software Foundation (ASF) in order to build a global,
> > diverse and self-governed open source community in API gateway field.
> >
> > Zhiliu is submitting this proposal to donate the APISIX sources code
> > and associated artifacts
> > (documentation, web site content, wiki, etc.) to the Apache Software
> > Foundation Incubator under the Apache License, Version 2.0.
> >
> > These artifacts are currently available on GitHub at
> > https://github.com/iresty/apisix and include:
> > - APISIX: The Cloud-Native Microservices API gateway.
> > - APISIX-dashboard: The dashboard for APISIX API gateway.
> >
> > == Background ==
> >
> > Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> > traditional monolithic applications are being replaced by microservices.
> > This also brings more challenges for API gateways, not only handling
> > north-south traffic,
> > but also handling east-west traffic between microservices,
> > and need to ensure high concurrency and very low latency at the same
> time.
> >
> > APISIX was open sourced on Github in in June 2019.
> > At first, APISIX needs to interact directly with etcd to modify the
> > configuration of routes and plugins.
> > After we opened on the GitHub, the community gives the feedbacks about
> > high level API and built-in dashboard.
> > So in 0.6 version, APISIX provided REST admin API and dashboard to
> > control the API gateway.
> > Since then more and more contributors have joined in, and more plugins
> > and features provided.
> >
> > == Rationale ==
> >
> > APISIX acts as an entry point for business traffic and plays an
> > important role in the current system.
> >  Making traffic more secure and faster to process is the ultimate goal
> > of APISIX.
> >
> > APISIX includes these primary parts:
> > - Provide the core of the API gateway, including various
> > processing of requests and responses, dynamic upstream and dynamic SSL
> > certificates,
> > upstream active and passive health checks, etc. The core does not
> > bind APISIX, other projects can be used directly.
> > - Provide the plug-in hot plugging mechanism based on the core, to
> > support gRPC transcoding,
> >  identity authentication, rate limiting, OpenTracing etc. And
> > provide a plugin development library,
> >   users can easily write their own plugins.
> > - Provide the admin API and dashboard to operate the API gateway,
> > and also support updating with the yaml configuration file, which
> > is friendly for Kubernetes.
> >
> > There is a strong need for an open, easy-to-use microservice API
> > gateway to help developers
> >  reduce duplication of code development and better manage APIs.
> > We believe that by moving to Apache it will help us work in a more
> > global and open way.
> > Under Apache’s strong governance and existing processes, hope is also
> > to make APISIX more reliable and encourage more developers to
> > participate,
> >  as is crucial for API gateway.
> >
> > == Current Status ==
> >
> > === Meritocracy ===
> >
> > APISIX was created in April 2019 and opened on github on June 6, 2019.
> > The project now has contributors and users from a dozen companies;
> > we have set up the PMC Team and Committer Team. New contributors are
> > guided and reviewed by existed PMC members.
> > When they are ready, PMC will start a vote to promote him/her to
> > become a member of PMC or Committer Team,
> > see the votes for Committer:
> > https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> > Contributions are always welcomed and highly valued.
> > A lot of energy is allocated to 

Re: [VOTE] Accept APISIX into Apache Incubator

[Woonsan Ko]

+1 (binding)

Good luck!

Woonsan

On Thu, Oct 10, 2019 at 5:55 PM Ming  wrote:
>
> Hi all,
>
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> = APISIX Proposal =
>
> == Abstract ==
>
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
>
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service system.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
>
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
>
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
>
> == Background ==
>
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
>
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
>
> == Rationale ==
>
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
>
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
>
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
>
> == Current Status ==
>
> === Meritocracy ===
>
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
>
> === Community ===
>
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group of more than 500 

Re: [VOTE] Accept APISIX into Apache Incubator

[Sheng Wu]

+1 binding. Good luck.

Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108


Mohammad Asif Siddiqui  于2019年10月12日周六 下午2:41写道：

> +1 (binding)
>
> Regards
> Asif
>
> On 2019/10/10 08:54:38, Ming  wrote:
> > Hi all,
> >
> > After the discussion of APISIX proposal
> > (discussion thread:
> >
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E
> ),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring APISIX into Incubator
> >   [ ] +0, I don't care either way
> >   [ ] -1, do not bring APISIX into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > = APISIX Proposal =
> >
> > == Abstract ==
> >
> > APISIX is a cloud-native microservices API gateway, delivering the
> > ultimate performance, security,
> > open source and scalable platform for all your APIs and microservices.
> >
> > APISIX is based on OpenResty and etcd, and has dynamic routing and
> > plug-in hot loading,
> >  which is especially suitable for API management under micro-service
> system.
> >
> > == Proposal ==
> >
> > The goal of this proposal is to bring the existing APISIX
> >  codebase and existing developers
> > and community
> > into the Apache Software Foundation (ASF) in order to build a global,
> > diverse and self-governed open source community in API gateway field.
> >
> > Zhiliu is submitting this proposal to donate the APISIX sources code
> > and associated artifacts
> > (documentation, web site content, wiki, etc.) to the Apache Software
> > Foundation Incubator under the Apache License, Version 2.0.
> >
> > These artifacts are currently available on GitHub at
> > https://github.com/iresty/apisix and include:
> > - APISIX: The Cloud-Native Microservices API gateway.
> > - APISIX-dashboard: The dashboard for APISIX API gateway.
> >
> > == Background ==
> >
> > Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> > traditional monolithic applications are being replaced by microservices.
> > This also brings more challenges for API gateways, not only handling
> > north-south traffic,
> > but also handling east-west traffic between microservices,
> > and need to ensure high concurrency and very low latency at the same
> time.
> >
> > APISIX was open sourced on Github in in June 2019.
> > At first, APISIX needs to interact directly with etcd to modify the
> > configuration of routes and plugins.
> > After we opened on the GitHub, the community gives the feedbacks about
> > high level API and built-in dashboard.
> > So in 0.6 version, APISIX provided REST admin API and dashboard to
> > control the API gateway.
> > Since then more and more contributors have joined in, and more plugins
> > and features provided.
> >
> > == Rationale ==
> >
> > APISIX acts as an entry point for business traffic and plays an
> > important role in the current system.
> >  Making traffic more secure and faster to process is the ultimate goal
> > of APISIX.
> >
> > APISIX includes these primary parts:
> > - Provide the core of the API gateway, including various
> > processing of requests and responses, dynamic upstream and dynamic SSL
> > certificates,
> > upstream active and passive health checks, etc. The core does not
> > bind APISIX, other projects can be used directly.
> > - Provide the plug-in hot plugging mechanism based on the core, to
> > support gRPC transcoding,
> >  identity authentication, rate limiting, OpenTracing etc. And
> > provide a plugin development library,
> >   users can easily write their own plugins.
> > - Provide the admin API and dashboard to operate the API gateway,
> > and also support updating with the yaml configuration file, which
> > is friendly for Kubernetes.
> >
> > There is a strong need for an open, easy-to-use microservice API
> > gateway to help developers
> >  reduce duplication of code development and better manage APIs.
> > We believe that by moving to Apache it will help us work in a more
> > global and open way.
> > Under Apache’s strong governance and existing processes, hope is also
> > to make APISIX more reliable and encourage more developers to
> > participate,
> >  as is crucial for API gateway.
> >
> > == Current Status ==
> >
> > === Meritocracy ===
> >
> > APISIX was created in April 2019 and opened on github on June 6, 2019.
> > The project now has contributors and users from a dozen companies;
> > we have set up the PMC Team and Committer Team. New contributors are
> > guided and reviewed by existed PMC members.
> > When they are ready, PMC will start a vote to promote him/her to
> > become a member of PMC or Committer Team,
> > see the votes for Committer:
> > 

Re: [VOTE] Accept APISIX into Apache Incubator

[Mohammad Asif Siddiqui]

+1 (binding)  
  
Regards  
Asif

On 2019/10/10 08:54:38, Ming  wrote: 
> Hi all,
> 
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
> 
> Please cast your vote:
> 
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
> 
> = APISIX Proposal =
> 
> == Abstract ==
> 
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
> 
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service system.
> 
> == Proposal ==
> 
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
> 
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
> 
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
> 
> == Background ==
> 
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
> 
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
> 
> == Rationale ==
> 
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
> 
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
> 
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
> 
> === Community ===
> 
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group of more 

Re: [VOTE] Accept APISIX into Apache Incubator

[Justin Mclean]

Hi,

+1 from me. Good luck on your journey!

Thanks,
Justin



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept APISIX into Apache Incubator

[Furkan KAMACI]

Hi,

+1 (binding)

Kind Regards,
Furkan KAMACI

11 Eki 2019 Cum, saat 06:36 tarihinde Gosling Von 
şunu yazdı:

> +1, binding
>
>
> Best Regards,
> Von Gosling
>
> > On Oct 10, 2019, at 4:54 PM, Ming  wrote:
> >
> > Hi all,
> >
> > After the discussion of APISIX proposal
> > (discussion thread:
> >
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E
> ),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >  [ ] +1, bring APISIX into Incubator
> >  [ ] +0, I don't care either way
> >  [ ] -1, do not bring APISIX into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > = APISIX Proposal =
> >
> > == Abstract ==
> >
> > APISIX is a cloud-native microservices API gateway, delivering the
> > ultimate performance, security,
> > open source and scalable platform for all your APIs and microservices.
> >
> > APISIX is based on OpenResty and etcd, and has dynamic routing and
> > plug-in hot loading,
> > which is especially suitable for API management under micro-service
> system.
> >
> > == Proposal ==
> >
> > The goal of this proposal is to bring the existing APISIX
> >  codebase and existing developers
> > and community
> > into the Apache Software Foundation (ASF) in order to build a global,
> > diverse and self-governed open source community in API gateway field.
> >
> > Zhiliu is submitting this proposal to donate the APISIX sources code
> > and associated artifacts
> > (documentation, web site content, wiki, etc.) to the Apache Software
> > Foundation Incubator under the Apache License, Version 2.0.
> >
> > These artifacts are currently available on GitHub at
> > https://github.com/iresty/apisix and include:
> >- APISIX: The Cloud-Native Microservices API gateway.
> >- APISIX-dashboard: The dashboard for APISIX API gateway.
> >
> > == Background ==
> >
> > Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> > traditional monolithic applications are being replaced by microservices.
> > This also brings more challenges for API gateways, not only handling
> > north-south traffic,
> > but also handling east-west traffic between microservices,
> > and need to ensure high concurrency and very low latency at the same
> time.
> >
> > APISIX was open sourced on Github in in June 2019.
> > At first, APISIX needs to interact directly with etcd to modify the
> > configuration of routes and plugins.
> > After we opened on the GitHub, the community gives the feedbacks about
> > high level API and built-in dashboard.
> > So in 0.6 version, APISIX provided REST admin API and dashboard to
> > control the API gateway.
> > Since then more and more contributors have joined in, and more plugins
> > and features provided.
> >
> > == Rationale ==
> >
> > APISIX acts as an entry point for business traffic and plays an
> > important role in the current system.
> > Making traffic more secure and faster to process is the ultimate goal
> > of APISIX.
> >
> > APISIX includes these primary parts:
> >- Provide the core of the API gateway, including various
> > processing of requests and responses, dynamic upstream and dynamic SSL
> > certificates,
> >upstream active and passive health checks, etc. The core does not
> > bind APISIX, other projects can be used directly.
> >- Provide the plug-in hot plugging mechanism based on the core, to
> > support gRPC transcoding,
> > identity authentication, rate limiting, OpenTracing etc. And
> > provide a plugin development library,
> >  users can easily write their own plugins.
> >- Provide the admin API and dashboard to operate the API gateway,
> >and also support updating with the yaml configuration file, which
> > is friendly for Kubernetes.
> >
> > There is a strong need for an open, easy-to-use microservice API
> > gateway to help developers
> > reduce duplication of code development and better manage APIs.
> > We believe that by moving to Apache it will help us work in a more
> > global and open way.
> > Under Apache’s strong governance and existing processes, hope is also
> > to make APISIX more reliable and encourage more developers to
> > participate,
> > as is crucial for API gateway.
> >
> > == Current Status ==
> >
> > === Meritocracy ===
> >
> > APISIX was created in April 2019 and opened on github on June 6, 2019.
> > The project now has contributors and users from a dozen companies;
> > we have set up the PMC Team and Committer Team. New contributors are
> > guided and reviewed by existed PMC members.
> > When they are ready, PMC will start a vote to promote him/her to
> > become a member of PMC or Committer Team,
> > see the votes for Committer:
> > https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> > Contributions are always welcomed and highly 

Re: [VOTE] Accept APISIX into Apache Incubator

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> On Oct 10, 2019, at 4:54 PM, Ming  wrote:
> 
> Hi all,
> 
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
> 
> Please cast your vote:
> 
>  [ ] +1, bring APISIX into Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring APISIX into Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
> 
> = APISIX Proposal =
> 
> == Abstract ==
> 
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
> 
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
> which is especially suitable for API management under micro-service system.
> 
> == Proposal ==
> 
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
> 
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
> 
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
>- APISIX: The Cloud-Native Microservices API gateway.
>- APISIX-dashboard: The dashboard for APISIX API gateway.
> 
> == Background ==
> 
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
> 
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
> 
> == Rationale ==
> 
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
> Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
> 
> APISIX includes these primary parts:
>- Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
>upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
>- Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
> identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>  users can easily write their own plugins.
>- Provide the admin API and dashboard to operate the API gateway,
>and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
> 
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
> reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
> as is crucial for API gateway.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
> 
> === Community ===
> 
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group of more 

Re: [VOTE] Accept APISIX into Apache Incubator

[Liang Chen]

+1(binding)

Regards
Liang


Ming wrote
> Hi all,
> 
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
> 
> Please cast your vote:
> 
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
> 
> = APISIX Proposal =
> 
> == Abstract ==
> 
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
> 
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service
> system.
> 
> == Proposal ==
> 
> The goal of this proposal is to bring the existing APISIX
> https://github.com/iresty/apisix; codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
> 
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
> 
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
> 
> == Background ==
> 
> Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
> 
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
> 
> == Rationale ==
> 
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
> 
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
> 
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
> 
> === Community ===
> 
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group of more than 500 people.
> 
> APISIX’s 

回复：Re: [VOTE] Accept APISIX into Apache Incubator

[Liu Ted]

+1 (binding)

Best regards,

Ted Liu

 
 
  2019 年 10 月 10 日周四 22:48，Dave Fisher 写道：   +1 (binding)

Regards,
Dave

Sent from my iPhone

> On Oct 10, 2019, at 1:54 AM, Ming  wrote:
> 
> Hi all,
> 
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
> 
> Please cast your vote:
> 
>  [ ] +1, bring APISIX into Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring APISIX into Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
> 
> = APISIX Proposal =
> 
> == Abstract ==
> 
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
> 
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
> which is especially suitable for API management under micro-service system.
> 
> == Proposal ==
> 
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
> 
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
> 
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
>    - APISIX: The Cloud-Native Microservices API gateway.
>    - APISIX-dashboard: The dashboard for APISIX API gateway.
> 
> == Background ==
> 
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
> 
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
> 
> == Rationale ==
> 
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
> Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
> 
> APISIX includes these primary parts:
>    - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
>    upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
>    - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>    identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>      users can easily write their own plugins.
>    - Provide the admin API and dashboard to operate the API gateway,
>    and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
> 
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
> reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
> as is crucial for API gateway.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
> 
> === Community ===
> 
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> 

Re: [VOTE] Accept APISIX into Apache Incubator

[Dave Fisher]

+1 (binding)

Regards,
Dave

Sent from my iPhone

> On Oct 10, 2019, at 1:54 AM, Ming  wrote:
> 
> Hi all,
> 
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
> 
> Please cast your vote:
> 
>  [ ] +1, bring APISIX into Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring APISIX into Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
> 
> = APISIX Proposal =
> 
> == Abstract ==
> 
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
> 
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
> which is especially suitable for API management under micro-service system.
> 
> == Proposal ==
> 
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
> 
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
> 
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
>- APISIX: The Cloud-Native Microservices API gateway.
>- APISIX-dashboard: The dashboard for APISIX API gateway.
> 
> == Background ==
> 
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
> 
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
> 
> == Rationale ==
> 
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
> Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
> 
> APISIX includes these primary parts:
>- Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
>upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
>- Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
> identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>  users can easily write their own plugins.
>- Provide the admin API and dashboard to operate the API gateway,
>and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
> 
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
> reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
> as is crucial for API gateway.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
> 
> === Community ===
> 
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group 

Re: [VOTE] Accept APISIX into Apache Incubator

[Willem Jiang]

+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Oct 10, 2019 at 4:55 PM Ming  wrote:
>
> Hi all,
>
> After the discussion of APISIX proposal
> (discussion thread:
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> = APISIX Proposal =
>
> == Abstract ==
>
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
>
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service system.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
>
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
>
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
>
> == Background ==
>
> Mircro-service and Cloud Native architecture are becoming more and more 
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
>
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
>
> == Rationale ==
>
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
>
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
>
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
>
> == Current Status ==
>
> === Meritocracy ===
>
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
>
> === Community ===
>
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a 

Re: [VOTE] Accept APISIX into Apache Incubator

[Kevin Ratnasekera]

+1

On Thu, Oct 10, 2019 at 2:25 PM Ming  wrote:

> Hi all,
>
> After the discussion of APISIX proposal
> (discussion thread:
>
> https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring APISIX into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring APISIX into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> = APISIX Proposal =
>
> == Abstract ==
>
> APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security,
> open source and scalable platform for all your APIs and microservices.
>
> APISIX is based on OpenResty and etcd, and has dynamic routing and
> plug-in hot loading,
>  which is especially suitable for API management under micro-service
> system.
>
> == Proposal ==
>
> The goal of this proposal is to bring the existing APISIX
>  codebase and existing developers
> and community
> into the Apache Software Foundation (ASF) in order to build a global,
> diverse and self-governed open source community in API gateway field.
>
> Zhiliu is submitting this proposal to donate the APISIX sources code
> and associated artifacts
> (documentation, web site content, wiki, etc.) to the Apache Software
> Foundation Incubator under the Apache License, Version 2.0.
>
> These artifacts are currently available on GitHub at
> https://github.com/iresty/apisix and include:
> - APISIX: The Cloud-Native Microservices API gateway.
> - APISIX-dashboard: The dashboard for APISIX API gateway.
>
> == Background ==
>
> Mircro-service and Cloud Native architecture are becoming more and more
> popular,
> traditional monolithic applications are being replaced by microservices.
> This also brings more challenges for API gateways, not only handling
> north-south traffic,
> but also handling east-west traffic between microservices,
> and need to ensure high concurrency and very low latency at the same time.
>
> APISIX was open sourced on Github in in June 2019.
> At first, APISIX needs to interact directly with etcd to modify the
> configuration of routes and plugins.
> After we opened on the GitHub, the community gives the feedbacks about
> high level API and built-in dashboard.
> So in 0.6 version, APISIX provided REST admin API and dashboard to
> control the API gateway.
> Since then more and more contributors have joined in, and more plugins
> and features provided.
>
> == Rationale ==
>
> APISIX acts as an entry point for business traffic and plays an
> important role in the current system.
>  Making traffic more secure and faster to process is the ultimate goal
> of APISIX.
>
> APISIX includes these primary parts:
> - Provide the core of the API gateway, including various
> processing of requests and responses, dynamic upstream and dynamic SSL
> certificates,
> upstream active and passive health checks, etc. The core does not
> bind APISIX, other projects can be used directly.
> - Provide the plug-in hot plugging mechanism based on the core, to
> support gRPC transcoding,
>  identity authentication, rate limiting, OpenTracing etc. And
> provide a plugin development library,
>   users can easily write their own plugins.
> - Provide the admin API and dashboard to operate the API gateway,
> and also support updating with the yaml configuration file, which
> is friendly for Kubernetes.
>
> There is a strong need for an open, easy-to-use microservice API
> gateway to help developers
>  reduce duplication of code development and better manage APIs.
> We believe that by moving to Apache it will help us work in a more
> global and open way.
> Under Apache’s strong governance and existing processes, hope is also
> to make APISIX more reliable and encourage more developers to
> participate,
>  as is crucial for API gateway.
>
> == Current Status ==
>
> === Meritocracy ===
>
> APISIX was created in April 2019 and opened on github on June 6, 2019.
> The project now has contributors and users from a dozen companies;
> we have set up the PMC Team and Committer Team. New contributors are
> guided and reviewed by existed PMC members.
> When they are ready, PMC will start a vote to promote him/her to
> become a member of PMC or Committer Team,
> see the votes for Committer:
> https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
> Contributions are always welcomed and highly valued.
> A lot of energy is allocated to ensure help to all wishing to contribute.
>
> === Community ===
>
> APISIX has been building an active community since its open source,
> and hosted meetup in 5 different cities in China.
> Currently, the community includes over 22 contributors, and we already
> have a user group of more than 500 people.
>
> APISIX’s 

[VOTE] Accept APISIX into Apache Incubator

[Ming]

Hi all,

After the discussion of APISIX proposal
(discussion thread:
https://lists.apache.org/thread.html/aada574d5fe8e9cf246f213f3915aebb2afa710607676c2af5d5eb73@%3Cgeneral.incubator.apache.org%3E),
I would like to call a VOTE to accept it into the Apache Incubator.

Please cast your vote:

  [ ] +1, bring APISIX into Incubator
  [ ] +0, I don't care either way
  [ ] -1, do not bring APISIX into Incubator, because...

The vote will open at least for 72 hours and only votes from the Incubator
PMC are binding.

= APISIX Proposal =

== Abstract ==

APISIX is a cloud-native microservices API gateway, delivering the
ultimate performance, security,
open source and scalable platform for all your APIs and microservices.

APISIX is based on OpenResty and etcd, and has dynamic routing and
plug-in hot loading,
 which is especially suitable for API management under micro-service system.

== Proposal ==

The goal of this proposal is to bring the existing APISIX
 codebase and existing developers
and community
into the Apache Software Foundation (ASF) in order to build a global,
diverse and self-governed open source community in API gateway field.

Zhiliu is submitting this proposal to donate the APISIX sources code
and associated artifacts
(documentation, web site content, wiki, etc.) to the Apache Software
Foundation Incubator under the Apache License, Version 2.0.

These artifacts are currently available on GitHub at
https://github.com/iresty/apisix and include:
- APISIX: The Cloud-Native Microservices API gateway.
- APISIX-dashboard: The dashboard for APISIX API gateway.

== Background ==

Mircro-service and Cloud Native architecture are becoming more and more popular,
traditional monolithic applications are being replaced by microservices.
This also brings more challenges for API gateways, not only handling
north-south traffic,
but also handling east-west traffic between microservices,
and need to ensure high concurrency and very low latency at the same time.

APISIX was open sourced on Github in in June 2019.
At first, APISIX needs to interact directly with etcd to modify the
configuration of routes and plugins.
After we opened on the GitHub, the community gives the feedbacks about
high level API and built-in dashboard.
So in 0.6 version, APISIX provided REST admin API and dashboard to
control the API gateway.
Since then more and more contributors have joined in, and more plugins
and features provided.

== Rationale ==

APISIX acts as an entry point for business traffic and plays an
important role in the current system.
 Making traffic more secure and faster to process is the ultimate goal
of APISIX.

APISIX includes these primary parts:
- Provide the core of the API gateway, including various
processing of requests and responses, dynamic upstream and dynamic SSL
certificates,
upstream active and passive health checks, etc. The core does not
bind APISIX, other projects can be used directly.
- Provide the plug-in hot plugging mechanism based on the core, to
support gRPC transcoding,
 identity authentication, rate limiting, OpenTracing etc. And
provide a plugin development library,
  users can easily write their own plugins.
- Provide the admin API and dashboard to operate the API gateway,
and also support updating with the yaml configuration file, which
is friendly for Kubernetes.

There is a strong need for an open, easy-to-use microservice API
gateway to help developers
 reduce duplication of code development and better manage APIs.
We believe that by moving to Apache it will help us work in a more
global and open way.
Under Apache’s strong governance and existing processes, hope is also
to make APISIX more reliable and encourage more developers to
participate,
 as is crucial for API gateway.

== Current Status ==

=== Meritocracy ===

APISIX was created in April 2019 and opened on github on June 6, 2019.
The project now has contributors and users from a dozen companies;
we have set up the PMC Team and Committer Team. New contributors are
guided and reviewed by existed PMC members.
When they are ready, PMC will start a vote to promote him/her to
become a member of PMC or Committer Team,
see the votes for Committer:
https://github.com/iresty/apisix/issues?utf8=%E2%9C%93=label%3Avote.
Contributions are always welcomed and highly valued.
A lot of energy is allocated to ensure help to all wishing to contribute.

=== Community ===

APISIX has been building an active community since its open source,
and hosted meetup in 5 different cities in China.
Currently, the community includes over 22 contributors, and we already
have a user group of more than 500 people.

APISIX’s contributors, who can provide employer information, are from
iresty.com, meizu.com, weibo.com, ke.com, fansup.mobi,
which also provide many important feedbacks from their actual scenarios.

We hope to grow the base of contributors by inviting all those who
offer contributions through