I am hoping to have at least 1 binary release before marking #2 as complete.

On Thu, Jan 16, 2020 at 10:20 AM Josh Fischer <[email protected]> wrote:

> Hi,
> inlined
>
>
>
> On Thu, Jan 16, 2020 at 10:11 AM Dave Fisher <[email protected]> wrote:
>
> > Hi -
> >
> > The list of three actions towards graduation should include current
> > actions and not ones that are completed.
> >
> > I have questions on #1. What are the licensing issues that remain? How
> are
> > these being tracked?
> >
> ** Github issues at the moment.  The licensing issue is mentioned here
> https://github.com/apache/incubator-heron/issues/3406 .
>
> > ** I don't think we need to list making several releases anymore.  I
> think
> we've demonstrated that we can create source releases.
>
> >
> > #3 should be improving the amount of community discussion and decision
> > making on the dev@ mailing list. Monthly Meetups are only in Sunnyvale
> > and exclude most of the world. It is a critical part of the Apache Way to
> > make sure discussion and decision making happens on the mailing list.
> >
> ** agreed
>
> >
> > On last committers and PPMC members please provide the date of the
> > elections.
> >
>
> ** will do
>
> >
> > Regards,
> > Dave
> >
> > > On Jan 16, 2020, at 12:27 AM, Ning Wang <[email protected]> wrote:
> > >
> > > Hi,
> > >
> > > I prepared a draft of the Feb podling report:
> > >
> > >
> >
> https://docs.google.com/document/d/1_8ckuEuL7pdo-eOCHaXs32ymD2_qRKzEybL2Zyr6gXU/edit#
> > >
> > > Please help to update if anything is missing. Thanks!
> > >
> > > On Wed, Jan 15, 2020 at 4:26 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 February 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, February 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/February2020
> > >>
> > >> 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