Thanks for sending this around, Paul - I should've linked it to the vote
thread, duh... 

Anyway, back to Rich's question: the answer is 'yes' as implied by my +1 on
the vote. Why would I be voting for the graduation if I weren't sure the
project is ready? Looks like a rhetorical question, this one.

Regards,
  Cos

On Mon, Nov 02, 2015 at 09:10AM, Paul King wrote:
> I certainly don't want to limit discussion but if anyone hasn't seen it
> yet,  here is the direct link to our self assessment against the maturity
> metrics (completed with the assistance of our mentors in particular
> Bertrand):
> https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc
> On 2 Nov 2015 5:30 am, "Rich Bowen" <rbo...@rcbowen.com> wrote:
> 
> > On Oct 28, 2015 4:26 PM, "Konstantin Boudnik" <c...@apache.org> wrote:
> > >
> > > Following discussions [1] about its current status, the Groovy community
> > > has voted [2] to graduate from the Incubator. The vote passed [3] with 12
> > +1s
> > > total, 5 are binding:
> > >
> > >     Guillaume Laforge
> > >     Cédric Champeau
> > >     Paul King
> > >     Jochen Theodorou
> > >     Pascal Schumacher
> > >     Emmanuel Lécharny (binding)
> > >     Bertrand Delacretaz (binding)
> > >     Andrew Bayer (binding)
> > >     Jim Jagielski (binding)
> > >     Konstantin Boudnik (binding)
> > >     Russel Winder
> > >     Guillaume Alleon
> > >
> > > The Groovy community has:
> > > * completed all required paperwork:
> > >     https://incubator.apache.org/projects/groovy.html
> > > * completed multiple releases (2.4.4, 2.4.5, 2.4.6 is in the works)
> > > * completed the name check procedure:
> > >     https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-88
> > > * addressed 50+ JIRAs:
> > >     http://is.gd/1tACON
> > > * voted in multiple new committers/PPMC members
> > >
> > > Therefore, I'm calling a VOTE to graduate Groovy with the following Board
> > > resolution. The VOTE will run for at least 72 hours, ending
> > > Saturday, October 31st 8 PM PST.
> >
> > I recognize that I have missed the vote and thus my response is moot. I
> > have been traveling, but i don't expect preferential treatment.
> >
> > However, as useful as these other measures are, as a member, and as a
> > director who will need to vote on this resolution, I'd like to know if you,
> > as a mentor, feel that this project had attainded maturity as described in
> > the maturity metric document, and will operate according to the Apache way?
> >
> > >
> > > [ ] +1 Graduate Apache Groovy from the Incubator.
> > > [ ] +0 Don't care.
> > > [ ] -1 Don't graduate Apache Groovy from the Incubator because ...
> > >
> > > Regards,
> > >     Cos
> > >
> > > [1] http://is.gd/DX41lO
> > > [2] http://is.gd/pPweq3
> > > [3] http://is.gd/VTLiqO
> > >
> > > ---- Apache Groovy graduation resolution draft
> > >
> > > Establish the Apache Groovy Top-Level 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 evolution
> > > and maintenance of the Groovy programming language,
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Groovy Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Groovy Project be and hereby is responsible
> > > for the evolution and maintenance of the Groovy programming language;
> > > and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Groovy" 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 Groovy
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache Groovy
> > > 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 Groovy Project
> > > PMC:
> > >
> > >     Cédric Champeau <cedric.champ...@gmail.com>
> > >     Paul King <pa...@asert.com.au>
> > >     Guillaume Laforge <glafo...@gmail.com>
> > >     Pascal Schumacher <pascalschumac...@gmx.net>
> > >     Jochen Theodorou <blackd...@gmx.org>
> > >     Andrew Bayer <andrew.ba...@gmail.com>
> > >     Konstantin Boudnik <c...@apache.org>
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Guillaume Laforge be
> > > appointed to the office of Vice President, Apache Groovy, 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 Apache Groovy Project be and hereby is tasked with
> > > the migration and rationalization of the Apache Incubator Groovy
> > > podling; and be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > Groovy podling encumbered upon the Apache Incubator Project are
> > > hereafter discharged.
> >

Attachment: signature.asc
Description: Digital signature

Reply via email to