Hey Guys -

It seems that our next step involves submitting a motion to the ASF board
that re-identifies our scope, mission and charter.

Are we at that point in the process now and do we have access to previous
motions to use as an example?

I assume that we don't need a separate vote for this?
It seems that we have three +1's from IPMC members.

From:
http://incubator.apache.org/incubation/Process_Description.html#Graduation

"For projects aiming to be a Top-Level-Project (TLP), you have an
additional obstacle, namely the ASF Board. While the ASF Board might be
your Sponsor, this does not mean they have formally accepted you as a TLP.
To establish a TLP you need to draft a board motion that identifies the
project scope, mission and charter. You can submit the motion to the Board
using the board at apache dot org email address. Well-prepared projects
will have already developed contacts with members of the Board so this
should not be a surprise agenda item. Keep in mind that the Board can
approve your motion as supplied, amend it, or reject it. If you are
rejected then you need to sort this out with the Incubator PMC and allies
you have developed during the incubation process. In other words, for a TLP
objective the Incubator PMC okay is only half of the story."

thanks,

--larry


On Thu, Oct 17, 2013 at 4:26 PM, Alan Gates <[email protected]> wrote:

> +1.  I think you guys were turbo fast learners of the Apache way, and are
> ready to run the project as a PMC.
>
> Alan.
>
> On Oct 15, 2013, at 8:44 PM, Chris Mattmann wrote:
>
> > Great work Kevin!
> >
> > So, it's time to start talking graduation.
> >
> > 3 releases. New committer/PPMC members added. Great job discussing
> > on list. I don't think there's anything really left for the Incubator.
> >
> > Thoughts?
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > -----Original Message-----
> > From: Kevin Minder <[email protected]>
> > Reply-To: "[email protected]" <[email protected]
> >
> > Date: Tuesday, October 15, 2013 5:16 PM
> > To: "[email protected]" <[email protected]>
> > Subject: [RESULT][VOTE] Release Apache Knox (Incubator) 0.3.0 (PASSED)
> >
> >> Hi Everyone,
> >>
> >> More than 72 hours have passed and the current vote thread is considered
> >> concluded and passes with the following resolution:
> >>
> >> Three +1 binding votes from the following IPMCs:
> >>
> >> * Devaraj Das
> >> * Chris A. Mattmann
> >> * Mahadev Konar
> >>
> >> Two +1 binding votes from the following PPMCs:
> >>
> >> * Kevin Minder
> >> * Larry McCay
> >>
> >> Four +1 non-binding votes
> >>
> >> * Dilli Arumugam
> >> * Maksim Kononenko
> >> * Vladimir Tkhir
> >> * Sergey Balan
> >>
> >> Zero -1 votes
> >>
> >> I will notify general@incubator and wait an additional 72 hours for
> >> feedback before beginning the process of moving the release artifacts to
> >> the mirrors.
> >>
> >> For reference here is the link to the [VOTE] thread
> >>
> http://mail-archives.apache.org/mod_mbox/knox-dev/201310.mbox/%3C5255AC37.
> >> [email protected]%3E
> >>
> >> Kevin.
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or entity
> >> to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> >> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> >> immediately
> >> and delete it from your system. Thank You.
> >
> >
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to