On 9/9/2020 8:49 PM, Julian Hyde wrote:
> I just read the report. I am not going to sign off yet. 3 sections ('Are 
> there any issues...', 'Have your mentors been helpful...' and 'Is the PPMC 
> managing the podling's brand') have not been answered. Please let me know 
> when I should re-review.
>

I am very sorry, Julian! I just fixed that now.
Please have a look again.

Thanks,
Bernard.

> Julian
>
>
> On 2020/09/09 18:45:01, Julian Hyde <jh...@apache.org> wrote:
>> Felix, I think you need to check the box otherwise it's not 'signed off'.
>>
>> Luciano, As the third mentor, can you please sign the report?
>>
>> Bernard & others, It would help me (and I suspect other mentors) if you send 
>> us a note, with a link to the wiki page [1], when the report is ready to be 
>> signed off. It's good for the project and for the mentors if we have 3 
>> sign-offs each reporting period.
>>
>> Julian
>>
>> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/September2020
>>
>> On 2020/09/01 19:37:35, Felix Cheung <felixcheun...@hotmail.com> wrote:
>>> Actually I just saw it. Thanks for putting it together.
>>>
>>> It is great to hear updates on (hopefully) generating more activities
>>>
>>> ________________________________
>>> From: Felix Cheung <felixcheun...@hotmail.com>
>>> Sent: Tuesday, September 1, 2020 12:35:24 PM
>>> To: dev@crail.apache.org <dev@crail.apache.org>; 
>>> d...@crail.incubator.apache.org <d...@crail.incubator.apache.org>
>>> Subject: Re: Podling Crail Report Reminder - September 2020
>>>
>>> Reminder on report
>>>
>>> ________________________________
>>> From: jmcl...@apache.org <jmcl...@apache.org>
>>> Sent: Saturday, August 29, 2020 6:55:15 PM
>>> To: d...@crail.incubator.apache.org <d...@crail.incubator.apache.org>
>>> Subject: Podling Crail Report Reminder - September 2020
>>>
>>> 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, 16 September 2020.
>>> 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, September 02).
>>>
>>> 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/September2020
>>>
>>> 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