Just have a look and edited a few things below:

   1. There is a trademark section in the new template report [1] from
   Incubator. I replied the question according the situation of Apache Weex.
   2. We should start a Poddling Name Search [2], through which we will
   know whether we can continue use the name of Apache Weex legally.

I am fine with other parts. Thanks for your contribution @任 跃兵
<[email protected]> .

Feel free to make a comment if any contributor in this mailing list has an
opinion.

Considering the fact that the deadline is 1st, Jan, 2020, a national
holiday, we will submit the report officially by the end of this week.

[1]
https://cwiki.apache.org/confluence/display/INCUBATOR/January2020#is-the-ppmc-managing-the-podlings-brand--trademarks-17
[2] https://incubator.apache.org/guides/names.html

Best Regards,
YorkShen

申远


任 跃兵 <[email protected]> 于2019年12月21日周六 下午6:34写道:

> @申远 <[email protected]>
>
> Please review the draft of Podding report[2].
>
>
>
> Three most important unfinished issues and How has the community developed
> since, I'm not sure. I just wrote down the information I was sure.
>
> The pull request, issue in github and mailing list are calculated from
> 2019-10-01.
>
>
>
> [2] https://cwiki.apache.org/confluence/display/WEEX/January%2C+2020
>
>
>
> *发件人**: *申远 <[email protected]>
> *日期**: *2019年12月19日 星期四 下午4:53
> *收件人**: *dev <[email protected]>, 任 跃兵 <[email protected]>
> *主题**: *Re: Podling Weex Report Reminder - January 2020
>
>
>
> @cnryb
>
>
>
> Best Regards,
> YorkShen
>
> 申远
>
>
>
>
>
> 申远 <[email protected]> 于2019年12月19日周四 下午4:51写道:
>
> @cnryb
>
>
>
> Could you please do the honour for Weex wrting the draft of Podding report?
>
>
>
> You can take our previous report [1] as an example, thanks.
>
>
>
> [1] https://cwiki.apache.org/confluence/display/WEEX/Poddling+report
>
>
>
> Best Regards,
> YorkShen
>
> 申远
>
>
>
>
>
> <[email protected]> 于2019年12月19日周四 下午1:15写道:
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, January 01).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>     the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>     towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>     aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/January2020
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
>

Reply via email to