incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: Podling Report Reminder - July 2018
Date Thu, 05 Jul 2018 11:35:52 GMT
I want to get this out there. I do not know why everyone is stuck on
gossip. There are some TLP that do not have activity for years and podlings
much older then gossip. I can give numerous examples.

On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament <johndament@apache.org>
wrote:

> That sounds like retirement to me.  The way I've always seen it is that
> podlings don't fail, the people behind them simply had a change in
> priorities.
>
> Gossip is a great toolkit that I believe people will continue to use.
>
> John
>
>
> On Thu, Jun 28, 2018, 12:44 PM Josh Elser <elserj@apache.org> wrote:
>
> > I've been trying to be patient around this, but I think this month's
> > incubator report must be "Gossip is going to exit incubation" (I'm not
> > sure what the proper verb is here; I only know that "retire" is wrong)
> >
> > We've gone through many months where the only traffic I've seen on the
> > mailing list are the report reminders.
> >
> > This doesn't need to be interpreted as "Gossip is a failure at the ASF"
> > or anything of the such. It just means "It's not the right time for
> > Gossip at the ASF incubator". By all means, we can bring it back into
> > incubation if we get some more community traction behind the project.
> >
> > On 6/27/18 5:41 PM, jmclean@apache.org 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, 18 July 2018, 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, July 04).
> > >
> > > 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://wiki.apache.org/incubator/July2018
> > >
> > > 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
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message