No worries, thanks Brian. These are every month as a podling, correct? Maybe 
it's every quarter. I don't remember.

> On Mar 30, 2023, at 08:33, Brian Proffitt <[email protected]> wrote:
> 
> Okay, my error. I must not have seen the update.
> 
> BKP
> 
> Brian Proffitt
> VP, Marketing & Publicity
> Co-organizer, Community Over Code
> Member, Apache Software Foundation
> Member, Apache Community Development & Incubator PMCs
> Red Hat Open Source Program Office
> 
> On Thu, Mar 30, 2023 at 10:32 AM Jason Porter <[email protected]>
> wrote:
> 
>> Yeah, we did this already. The mentors signed off on this.
>> 
>> Jason Porter
>> Software Engineer
>> He/Him/His
>> 
>> IBM
>> 
>> On Mar 30, 2023, at 08:12, Jason Porter <[email protected]> wrote:
>> 
>> I this one of the things that need to be set up before we can do it? I
>> thought we submitted our report on the wiki.
>> 
>> Jason Porter
>> Software Engineer
>> He/Him/His
>> 
>> IBM
>> 
>> On Mar 30, 2023, at 08:04, Brian Proffitt <[email protected]<mailto:
>> [email protected]>> wrote:
>> 
>> Who wants to take this on, this is late.
>> 
>> Brian Proffitt
>> VP, Marketing & Publicity
>> Co-organizer, Community Over Code
>> Member, Apache Software Foundation
>> Member, Apache Community Development & Incubator PMCs
>> Red Hat Open Source Program Office
>> 
>> On Thu, Mar 2, 2023 at 2:46 AM <[email protected]> wrote:
>> 
>> 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 March 2023.
>> 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, March 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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_INCUBATOR_March2023&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=ccejQvbgPmKVXnd3-rUfVA&m=g33pCagk9UBMEZjw_jltWhls9w3uLYZ6VURBzNtwIOpQvt0jHFt0MiPgbghKDlzZ&s=H6dkGUcj-vLU5nCaW009FaMnnX1D-sklKPfUYMIR7x0&e=
>>  
>> 
>> 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
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to