fluo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Walch <mwa...@apache.org>
Subject Re: Podling Report Reminder - July 2016
Date Tue, 05 Jul 2016 18:30:24 GMT
It makes sense to have only one copy.  Also, we don't have to remember to
post the final draft to incubator wiki which is nice.

I was able to get write access to incubator wiki and I posted our report. I
will delete the podling reports page on our wiki.

On Tue, Jul 5, 2016 at 1:39 PM Christopher <ctubbsii@apache.org> wrote:

> I added a small note about our branding transition to the report on our
> wiki. I think in the future we can/should just edit the report inline on
> the Incubator wiki, though. I don't want to have to go looking in two
> places.
>
> On Tue, Jul 5, 2016 at 12:24 PM Josh Elser <josh.elser@gmail.com> wrote:
>
> > Nope, an email to general@incubator is the way to do it :)
> >
> > I don't think I have the karma to grant you the access myself.
> >
> > Mike Walch wrote:
> > > I created a page on our wiki so we can collaborate on podling reports
> and
> > > easily view previous reports.
> > >
> > > https://github.com/apache/incubator-fluo/wiki/Podling-Reports
> > >
> > > I created a July report.  Feel free to add/modify.
> > >
> > > The podling report is due tomorrow by end of day.  I am willing to add
> it
> > > to the incubator wiki.  However, I don't have write access to the
> > incubator
> > > wiki.  How do I get it?  I have seen people in the past send an email
> to
> > > general@incubator.apache.org but that's kind of spammy.  Is there
> > another
> > > way?
> > >
> > >
> > > On Tue, Jul 5, 2016 at 8:51 AM Josh Elser<josh.elser@gmail.com>
> wrote:
> > >
> > >> Can I ask to get a volunteer to write up this month's board report,
> > >> please? :)
> > >>
> > >> johndament@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, 20 July 2016, 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 06).
> > >>>
> > >>> 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.
> > >>>
> > >>> 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.
> > >>>
> > >>> This should be appended to the Incubator Wiki page at:
> > >>>
> > >>> http://wiki.apache.org/incubator/July2016
> > >>>
> > >>> 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
> > >
> >
>

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