@mentors, can you sign off on the podling report please?

https://docs.google.com/document/d/1tOxwHV937F1Jx1W2VJNtO0qCOUAIwFm3JCeb-x2GsSg/edit

Thanks!

On Wed, May 22, 2019 at 9:01 PM Maxime Beauchemin <
[email protected]> wrote:

> Integrated, thanks for the edits!
>
> On Wed, May 22, 2019, 6:24 AM Jeff Feng <[email protected]>
> wrote:
>
>> Hey Max, I added a couple updates.  Thanks for spearheading!
>> Jeff
>>
>> On Tue, May 21, 2019 at 11:16 PM Maxime Beauchemin <
>> [email protected]> wrote:
>>
>> > Here's the draft of the report, please comment and suggest edits. I did
>> a
>> > very quick scan of the commit log to identify highlights, very possible
>> I
>> > missed many important ones.
>> >
>> >
>> https://docs.google.com/document/d/1tOxwHV937F1Jx1W2VJNtO0qCOUAIwFm3JCeb-x2GsSg/edit
>> >
>> > On Tue, May 21, 2019 at 10:38 PM Jeff Feng <[email protected]
>> >
>> > wrote:
>> >
>> > > Thank you Max!  🙌
>> > >
>> > > On Tue, May 21, 2019 at 10:36 PM Maxime Beauchemin <
>> > > [email protected]> wrote:
>> > >
>> > > > I volunteer to ship this quarter's report.
>> > > >
>> > > > Max
>> > > >
>> > > > On Sat, May 18, 2019 at 5:41 PM <[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, 19 June 2019, 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, June 05).
>> > > > >
>> > > > > 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/June2019
>> > > > >
>> > > > > Note: This is manually populated. You may need to wait a little
>> > before
>> > > > > this page is created from a template.
>> > > > >
>> > > > > 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
>> > > > >
>> > > >
>> > >
>> > >
>> > > --
>> > >
>> > > *Jeff Feng*
>> > > Product Lead
>> > > m: (949)-610-5108
>> > > twitter: @jtfeng
>> > >
>> >
>>
>>
>> --
>>
>> *Jeff Feng*
>> Product Lead
>> m: (949)-610-5108
>> twitter: @jtfeng
>>
>

Reply via email to