Hi,

I am reading the documentation for graduation[1], below is what I
think the community need to do:

- Choose PMC chair. I am suggesting Ian Luo as PMC chair. Ian is
leading the Dubbo project, and has rich experience in RPC/service
framework. I think he is the best candidate. How do others think?
- Discuss how to form PMC, normally just put all the PPMC member to
PMC member, but it is better to ask whether they are willing to or
not. I can help to send the email if the community is willing to.
- Complete maturity model assessment. I can help to draft it.
- Add a page of how to report security issue to official website. Can
some one help with it?
- Add a documentation of how to become a committer on the website. Can
some one help with it?
- Draft a resolution document, I can help to draft it. This need input
from the first 2 TODO item.

[1] https://incubator.apache.org/guides/graduation.htm


On Sat, Mar 30, 2019 at 6:00 PM Huxing Zhang <[email protected]> wrote:
>
> Hi All,
>
> It has been more than 1 year since Dubbo joins the ASF
> incubator(2018-02-16). During incubation I think Dubbo community has
> been growing in a fast and healthy way, and also learned a lot about how
> to collaborate in Apache way.
>
> I think it is time to discuss the graduation as a Top level project for Dubbo.
>
> Until now, what we've achieved:
>
> ### Releases
> Totally 10 release since incubation
> - Dubbo:  2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 2.7.0, 2.7.1
> - Dubbo spring boot starter: 0.2.1 & 0.1.2, 2.7.0
> - Dubbo ops: 0.1
> The release process has been well-documented and there are 6 different
> release managers: Jun Liu, Yong Zhu, Victory Cao, Huxing Zhang, Mercy
> Ma, Ian Luo.
>
> ### Community building:
> - PPMC 19(+8 since incubation, excluding mentors)
> - committers 35(+18 since incubation)
> The committers varies from Alibaba, Weidian, Jingdong, Qunar, Youzan,
> Netease, Meituan-Dianping, Rongguan, Handuyishe, Didi, NetsUnion,
> Caocaokeji, Huawei, GomeFinance, Asiainfo-sec, iFlytek, Keep and etc.
> - The number of contributors has grown from 70+ to 186, the number of
> stars has grown from ~16k to 25k+, the number of forks are grown from
> 12k+ to 16k+ since incubation. One thing that worthing mentioning is
> that there are 92 contributors for the website project.
> - 1401 issues and 1168 pull requests are closed since incubation.
> - 140+ companies are using Dubbo in production since incubation.
> - Discussion are happening on the mailing list. 376 subscriber for the
> dev@ mailing list. Below is some stats in recent few months:
>   * March 2019: 375 emails sent by 52 people, divided into 75 topics
>   * Feb 2019: 260 emails sent by 45 people, divided into 61 topics
>   * Jan 2019: 448 emails sent by 62 people, divided into 83 topics
>   * Dec 2018: 427 emails sent by 48 people, divided into 78 topics
>   * Nov 2018: 235 emails sent by 38 people, divided into 44 topics
>   * Oct 2018: 154 emails sent by 31 people, divided into 32 topics
> We are happy to see that more and more users joined the discussion.
>
> ### IP clearance
> - The IP clearance is completed for Dubbo, dubbo-spring-boot-starter,
> and dubbo-ops project.
> - The transfer plan for external Dubbo group has been discussed[1],
> and progress has been made steadily.
> - Podling website check complete [2]
> - Podling name search completed [3]
> - Promote the ASF download link in the official website[4]
> - A list of committers is shown in the official website[5]
> - The Dubbo incubation status page[6] has been kept up-to-date
>
> Based on the data above, I think Dubbo is ready for graduation.
> How do you folks think?
>
> [1] 
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> [2] https://whimsy.apache.org/pods/project/dubbo
> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-152
> [4] http://dubbo.apache.org/en-us/blog/download.html
> [5] http://dubbo.apache.org/en-us/docs/developers/developers_dev.html
> [6] https://incubator.apache.org/projects/dubbo.html
>
> --
> Best Regards!
> Huxing



--
Best Regards!
Huxing

Reply via email to