incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: [DISCUSS] Fluo graduation as TLP
Date Mon, 03 Jul 2017 21:31:05 GMT
On Mon, Jul 3, 2017 at 4:23 PM John D. Ament <johndament@apache.org> wrote:

> Oh hmm did a bit more digging.
>
> Looks like you did add someone, but I guess due to timing it was missed in
> the last board report? Then nevermind, ignore my 2nd bullet point.
>
>
Correct. This was due to timing. If we don't graduate by then, the new
committer will appear on our next report. (And will appear on our first
board report if we do graduate.) Our podling status page does include him,
however.


> John
>
> On Mon, Jul 3, 2017 at 4:15 PM John D. Ament <johndament@apache.org>
> wrote:
>
> > Hi Christopher,
> >
> > Thanks for the heads up.  A few nits on my part, but overall I would be
> > happy to see Fluo graduate.  When reading my notes, please also consult
> the
> > graduation guide at [1].
> >
> > - The discussion and vote should have happened on your public dev list,
> > not private.  It's good that at least discussion happened publicly, and
> the
> > actual vote isn't required so it's not a big deal.
> > - I don't see any sign that you added new committers or PPMC members
> since
> > incubating.  See also [2].  I don't see that as a show stopper, as it
> looks
> > like a diverse group.
>

It's not as diverse as we'd like. We recognize this and really want to do
better. This was raised in our DISCUSS thread, but it seems agreed that
remaining in Incubation is not going to help this situation much. It will
be something we will continue to work on, regardless, and something we'd
include in our board reports as a TLP.


> > - Of the proposed PMC, how many are actively committing to Fluo?  Was
> > there an ask at any point to see who was still interested?
>

At least three are actively committing. An additional one (myself) helps
out more with code reviews, build system maintenance, bug reports, and
releases rather than coding. At least one of the mentors was active with
reading issues and participating in discussions. Two others have mainly
been acting only as mentors.

I'm not sure I understand your second question.


> > - Only one mentor voted on the graduation.  Would be great to see if the
> > other mentors are equally on board.
> >
>

I don't want to speak for them, but to summarize what's in the podling
VOTE/DISCUSS threads: only one formally voted in the VOTE thread, but one
more gave their enthusiastic +1 in the DISCUSS thread. The third expressed
some hesitation based on the size of the community (see my response about
diversity/size above), but seemed to accept the argument I made in that
thread for us continuing to work on this and include our progress in our
regular board reports as a TLP.


> > John
> >
> > [1]: http://incubator.apache.org/guides/graduation.html#toplevel
> > [2]: https://whimsy.apache.org/board/minutes/Fluo
> >
> >
> > On Mon, Jul 3, 2017 at 2:12 PM Christopher <ctubbsii@apache.org> wrote:
> >
> >> Greetings Incubator,
> >>
> >> The Fluo podling has decided to pursue graduation to a TLP. The result
> of
> >> the internal PPMC vote is at [1] (apologies that it occurred on our
> >> private
> >> list instead of on our dev list; the discuss thread [2] which preceded
> it
> >> did occur on the dev list). Our podling status page has recently been
> >> updated and can be found here[3].
> >>
> >> Below, you can view the proposed TLP resolution which we'd like to
> present
> >> to the board with the support of the IPMC, after sufficient discussion
> >> here
> >> and subsequent IPMC vote.
> >>
> >> [1]:
> >>
> >>
> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
> >> [2]:
> >>
> >>
> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
> >> [3]: https://incubator.apache.org/projects/fluo
> >>
> >> **********
> >> Establish the Apache Fluo Project
> >>
> >> WHEREAS, the Board of Directors deems it to be in the best interests of
> >> the Foundation and consistent with the Foundation's purpose to establish
> >> a Project Management Committee charged with the creation and maintenance
> >> of open-source software, for distribution at no charge to the public,
> >> related to the storage and incremental processing of large data sets.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Fluo Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
> >> the creation and maintenance of software related to the storage and
> >> incremental processing of large data sets; and be it further
> >>
> >> RESOLVED, that the office of "Vice President, Apache Fluo" be and hereby
> >> is created, the person holding such office to serve at the direction of
> >> the Board of Directors as the chair of the Apache Fluo Project, and to
> >> have primary responsibility for management of the projects within the
> >> scope of responsibility of the Apache Fluo Project; and be it further
> >>
> >> RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Fluo Project:
> >>
> >> * Billie Rinaldi <billie@apache.org>
> >> * Chris McTague <cjmctague@apache.org>
> >> * Christopher Tubbs <ctubbsii@apache.org>
> >> * Corey J. Nolet <cjnolet@apache.org>
> >> * Drew Farris <drew@apache.org>
> >> * Josh Elser <elserj@apache.org>
> >> * Keith Turner <kturner@apache.org>
> >> * Mike Walch <mwalch@apache.org>
> >>
> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
> >> to the office of Vice President, Apache Fluo, to serve in accordance
> >> with and subject to the direction of the Board of Directors and the
> >> Bylaws of the Foundation until death, resignation, retirement, removal
> >> or disqualification, or until a successor is appointed; and be it
> >> further
> >>
> >> RESOLVED, that the initial Apache Fluo PMC be and hereby is tasked with
> >> the creation of a set of bylaws intended to encourage open development
> >> and increased participation in the Apache Fluo Project; and be it
> >> further
> >>
> >> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
> >> migration and rationalization of the Apache Incubator Fluo podling; and
> >> be it further
> >>
> >> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> >> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
> >> discharged.
> >>
> >
>

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