Hi, Sheng,
Thank you for your suggestions.
Through the community maturity assessment, I hope that we can find the way
to build Apache APISIX better.
Apache APISIX has now released 4 apache releases with 4 different release
managers,
and we will continue to build the community.

Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing


Sheng Wu <[email protected]> 于2020年3月26日周四 上午9:01写道:

> Ming Wen <[email protected]> 于2020年3月22日周日 下午7:02写道:
>
> > Some suggestions inline
> > Thanks,
> > Ming Wen, Apache APISIX & Apache SkyWalking
> > Twitter: _WenMing
> >
> >
> > coolsoul <[email protected]> 于2020年3月22日周日 下午6:32写道:
> >
> > > Hello everyone, I finished the second draft of the report. Please
> review
> > > the
> > > report and your advice is welcome.
> > >
> > >
> > > ## APISIX
> > >
> > > 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 Nginx and etcd. Compared with traditional API
> > > gateways, APISIX has dynamic routing and plug-in hot loading, which is
> > > especially suitable for API management under micro-service system.
> > >
> > > APISIX has been incubating since 2019-10-17.
> > >
> > > ### Three most important unfinished issues to address before
> graduating:
> > >
> > >  1. More Apache Releases and more committers act as release manager to
> > >  release a version.
> > >  2. More committers and PPMC members.
> > >  3. Branding issues in the documentation, code, website, etc.
> > >
> > > ### Are there any issues that the IPMC or ASF Board need to be aware
> of?
> > >
> > >  None
> > >
> > > ### How has the community developed since the last report?
> > >
> > >  - We have some talks about how to build a good dashboard for impoving
> > > easiness
> > >  of using Apache APISIX, Mar 14th. Then it can make more users quick
> get
> > > start
> > >  and learn about this project.
> > >
> >
> > I think you'd better put important things first, such as we released
> three
> > apache releases.
> >
> >  - we release the version 1.0. the verison is import for us with a lot
> > > enhancement
> > >  in the core of Apache APISIX, also fixed many bugs come from users's
> > > production
> > >   enviroment. more and more company choose using Apache APISIX and
> > feedback
> > > experience
> > >   to the community and we're happy to see that feedback.
> > >
> >
> > we released APISIX 1.0, APISIX 1.1 and apisix-dashaobrd 1.0, three apache
> > releases.
> >
> >  - we elected the first committer in Europe @sshniro who introduced
> Apache
> > > APISIX
> > >
> >
> > we elected 3 new committers and 2 new PPMCs.
> >
> >  into the EU's industrial Internet Project and made a lot of optimization
> > > and improvement.
> > >  it is good for the promotion of the Apache APISIX all over the world.
> > >
> >
> > I think the diversity of the community is more important then promotion.
> >
> >  - We have 15 committers and 69 contributors (including 15 committers)
> now.
> > > since
> > >  the last report, two commiters was elected, including one core
> > contributor
> > > on Openresty.
> > >
> >
> > 3 new committers, not two.
> >
> >  we elected first non-initial PPMC @lilien1010. they contribute a lot for
> > > our community.
> > >  - We strengthen interaction/cooperation with other Apache project.
> E.g.
> > > Apache skywalking.
> > >  we also elected @Sheng Wu ( the PMC of Apache skywalking ) as our
> PPMC.
> > > then he can help us
> > >  a lot on community building.
> > >  - the official docker image library migrated to Apache.
> > >
> > > ### How has the project developed since the last report?
> > >
> > >  The project has been quite health, with more than 255 pull requests,
> 120
> > > of
> > >  them have being merged since the last report. Compare to the last
> > report,
> > > the number
> > >  of pull requests have 779% increase and the number of merged requests
> > have
> > > 380% increse.
> > >  These pull requests are authored by a diverse set of contributors. In
> > > order to guide more users
> > >  to get started, we have added a quick start guide and enriched more
> > > documents. Continue to
> > >  remind people to communicate via the Apache APISIX mailing list.
> > >
> > >
> > I think you can also count the number of participants and threads on the
> > mailing list.
> >
> >  During the peroid,we release two versions (1.0 and 1.1). the Pull
> Request
> > > is mainly
> > >  divided three aspects:
> > >  - Fixing Apache APISIX bug.
> > >  - add new feature and strengthen the stability of the code.
> > >  - enrich more documents.
> > >
> > > ### How would you assess the podling's maturity?
> > >
> > > Please feel free to add your own commentary.
> > >
> > >  - [ ] Initial setup
> > >  - [ ] Working towards first release
> > >  - [X] Community building
> > >  - [ ] Nearing graduation
> > >  - [ ] Other:
> > >
> > >
> > The progress of Apache APISIX, released 4 Apache releases by 4 different
> > release managers,
> > added 4 new committers and 2 new PPMCs:
> > - 2019-10-17 Project enters incubation.
> > - 2019-11-25 APISIX 0.9 has been released.
> > - 2019-11-28 New committer: lilien1010.
> > - 2020-1-15 APISIX 1.0 has been released.
> > - 2020-1-19 New committer: agile6v.
> > - 2020-2-24 Apache APISIX Dashboard 1.0 has been released.
> > - 2020-2-24 Apache APISIX 1.1 has been released.
> > - 2020-3-1 New committer: sshniro.
> > - 2020-3-6 New PPMC: lilien1010.
> > - 2020-3-15 New PPMC: Sheng Wu.
> > - 2020-3-16 New committer: spacewander.
> > -
> > I personally think the community is doing well,
> > so my assessment of maturity is nearing graduation, what do you think?
> >
>
> I think Community Building is the right statement.
> I noticed the APISIX's community development is good, but the `near
> graduation` stage should be only after the community has made the
> consensus.
> Right now, we are not.
>
> APISIX has just 160 days in the incubator, I would say we have time.
> Personally, I would suggest at least 3-5 release managers successfully do
> 5+ ASF releases, to make sure the PPMC team is ready on release check.
>
> Doing the graduation preparation, we should review the maturity model
> result, branding check, website review, release manager diversity check,
> community discussion, etc.
>
>
>
> > Myabe we can do the podling maturity assessment[1] for APISIX?
> >
> > [1]
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> >
> > ### Date of last release:
> > >
> > >  Fri Feb 24 2020 (1.1)
> > >
> > > ### When were the last committers or PPMC members elected?
> > >
> > >  At Mar 15 2020 PPMC members elected a new PPMC @Sheng Wu who help us a
> > lot
> > >  on the mail list. he also share the experience on the apache
> community.
> > >  At Mar 16 2020 PPMC members elected a new commiter @spacewander who
> > > contributed
> > >  a lot for some new features.
> > >
> > > ### Have your mentors been helpful and responsive?
> > >
> > >  Mentors are responsive and helpful. Things tend to be on the right
> way.
> > >
> > > ### Is the PPMC managing the podling's brand / trademarks?
> > >
> > >  Yes, We keep tracking podling's brand / trademarks.
> > >
> > > ### Signed-off-by:
> > >
> > >  - [] (apisix) Willem Ning Jiang
> > >     Comments:
> > >  - [] (apisix) Justin Mclean
> > >     Comments:
> > >  - [] (apisix) Kevin Ratnasekera
> > >     Comments:
> > >  - [] (apisix) Von Gosling
> > >     Comments:
> > >
> > > ### IPMC/Shepherd notes:
> > >
> >
>

Reply via email to