hi, I have fixed the Question No.2 and No.3 according to your suggestion.

### How has the community developed since the last report?

- Learning the Apache way and its value behind rules, working in Apache way.
- Our Apache website is constructed.
- We have 12 committers and 35 contributors (including 12 committers)
contributing to Apache APISIX.
- Over 13 company users have announced that they are using APISIX and more
than 50% of them also submitted code or fixed the documentation for APISIX
: https://github.com/apache/incubator-apisix/issues/487

### How has the project developed since the last report?

The project has been quite healthy, with ~50 pull requests being merged in
October. These pull requests are authored by a diverse set of
contributors(~30 authors last month).

Some highlights of recent developments:
- APISIX support etcd v3.
- New plugin: data-validator
- Supported cluster limit-req and limit-conn.
- Fixed some bugs.

We are planning to have a 0.9.0 release in November.




Justin Mclean <[email protected]> 于2019年11月1日周五 下午4:43写道:

> Hi,
>
> > 2.How has the community developed since the last report?
> >
> > - Github stars grew from 800+ to 1201 in October.
>
> Why would the IPMC or board care about this? Being popular is not the same
> as community growth.
>
> > - Over 13 company users have announced that he is using APISIX:
> > https://github.com/apache/incubator-apisix/issues/487
>
> At the ASF we don’t care so much if companies use our software, it’s nice
> if they do but that is not community growth. What would be more interesting
> is efforts in making people involved in that community members. And when
> people get involved we don’t care who they work for.
>
> > 3.How has the project developed since the last report?
> >
> > - We have 68 incoming pull request, and 58 of them are merged.
> > - We have 17 committers contributing to apisix.
>
> These numbers don’t mean much to anyone outside of the project, would it
> be possible to add some commentary to how the project has developed.
>
> Thanks,
> Justin
>
>

Reply via email to