fluo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: Podling Report Reminder - November 2016
Date Wed, 02 Nov 2016 02:59:39 GMT
I do think it would be helpful to label our issues with tags, like
"newbie". That's still a limitation imposed by INFRA with our preferred
choice of issue tracker.

On Tue, Nov 1, 2016 at 10:57 PM Christopher <ctubbsii@apache.org> wrote:

> I think growing our community is really the only outstanding area of
> concern (with respect to graduation) that we need to work on. However, I'm
> not sure how we can do that. One thing is that we could reach out to Rya,
> and any other developers who are using Fluo that we know about, to
> explicitly invite them (rather than wait for them to come to us).
>
> Aside from that, I'm not sure what else we can do. Maybe we could spend
> some dev cycles on packaging and blogging about how to use the software
> more (with examples) to help lower the barrier to entry and to highlight
> use cases?
>
> On Tue, Nov 1, 2016 at 10:16 PM Josh Elser <josh.elser@gmail.com> wrote:
>
> Thanks for posting, Keith. A couple of thoughts:
>
> * Growing the community is probably worth a few spots on the top-3
> things to do
> * Lots of good things are written up that Fluo has done, but nothing on
> how you intend to grow Fluo beyond the current size.
>
> Good enough to sign off, but this is the area of most importance to
> focus on now that you have a cadence for releases.
>
> - Josh
>
> Keith Turner wrote:
> > I just udpated the wiki if anyone wants to review the changes.
> >
> > On Mon, Oct 31, 2016 at 3:56 PM, Josh Elser<josh.elser@gmail.com>
> wrote:
> >> I know you're already in a writing "mood", Keith.
> >>
> >> Don't forget about this one, please. Needs to be done by Wednesday this
> week
> >> (48hrs).
> >>
> >>
> >> 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, 16 November 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, November 02).
> >>>
> >>> 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/November2016
> >>>
> >>> 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