Hello all,
Since we entered the incubation on 29th Aug 2019,with the contribution of 
everyone,our community grow up quickly.
Now, I'm glad to call on a discussion about whether we are ready for
graduation and what remains to be done.

I've summarized some of the data below:
- There are 1840 emails sent by 191 people in dev mailing-list excepted GitBox 
forwarded
- Released 8 Apache releases, through 5 different release managers
- Invited 14 new committers (all accepted)
- Invited 2 new PPMC members (all accepted)
- There are 149 contributors for now
- 1936 Issues created during ASF incubating, 1491 Issues resolved during ASF 
incubating
- 2410 PRs created during ASF incubating, 1970 PRs merged during ASF incubating
- finished the Podling Maturity Assessment for DolphinScheduler [1], all items 
are passed

I have created the issue [3] to ensure whether "Apache DolphinScheduler" is a 
suitable name,now we need to wait for the result.

Here are other things we need to discuss.
1.Website
We are updating our Website [3] content, document, and so on according to 
Apache rules.
and hopefully, it's following all requirements.
You may help check the rules [4] and discuss the ones that you think need to 
change.

2.Status File
I found I have no permisson to modify [5],Need help on how to get the modify 
permission.

For more details,see the checklist [6],welcome to check and add what need doing.


[1]https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/Podling+Maturity+Assessment+for+DolphinScheduler
[2]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-186
[3]https://dolphinscheduler.apache.org/
[4]https://incubator.apache.org/guides/sites.html<https://incubator.apache.org/guides/sites.htmlddddddddddddddddddddd/>
[5]http://incubator.apache.org/projects/dolphinscheduler.html
[6]https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/DolphinScheduler+Graduation+Checklist


Best Regards

------------------------------------------------------
DolphinScheduler(Incubator) PPMC
Gang Li 李岗

[email protected]

Reply via email to