Hi Justin,

Thank you for suggestions. I have already modified something on Podling
Report.

> 1. There is no need to list things that have been completed in the list
of things to be done before graduating.

I just removed completed things for IP clearance and first apache release.

> 2. That list also only needs to include things that are important to the
ASF. Points 5 and 6 ate more suited to the  project development section.

I just removed the points 5 and 6.

> 3. In the community development you provide some numbers, these don't
mean anything to people outside your project, please describe why these
number are important, is for instance the community growing?

I add more descriptions of how to understand the numbers of contributors
and companies which powered-by ShardingSphere. They are good changes for
community growing up.

> 4. You mention the brand issues as something the IPMC/board needs to be
aware of. Are you expected any action here by the board or IPMC?

Right now, the brand issues are under control, so we think board or IPMC
may do not need do any actions for now. I have already add note here.


------------------

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Justin Mclean <[email protected]> 于2019年9月25日周三 上午6:32写道:

> Hi ,
>
> Thanks for submitting the report early and having it contain more
> information than last time. There's a few things you still might want to
> improve:
> 1. There is no need to list things that have been completed in the list of
> things to be done before graduating.
> 2. That list also only needs to include things that are important to the
> ASF. Points 5 and 6 ate more suited to the  project development section.
> 3. In the community development you provide some numbers, these don't mean
> anything to people outside your project, please describe why these number
> are important, is for instance the community growing?
> 4. You mention the brand issues as something the IPMC/board needs to be
> aware of. Are you expected any action here by the board or IPMC?
>
> Thanks,
> Justin

Reply via email to