> We should consider PPMC votes binding for the *motion to release*, and IPMC votes binding for the *vote to release*. The PPMC has to motion (with 3x+1) the Incubator to release, so it's not as if the PPMC doesn't have binding votes...it's just not for the release, but for the *motion to release*...if that makes sense :)
It's basically a bicameral system. --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Wed, Dec 19, 2018 at 9:01 PM Daniel Gruno <[email protected]> wrote: > > On 12/19/18 7:54 PM, Geertjan Wielenga wrote: > > Yes, basically, this is exactly what I meant, but you said it much better > > and with fewer and better words. :-) > > > > Gj > > > > On Wednesday, December 19, 2018, Neil C Smith <[email protected]> wrote: > > > >> On Wed, 19 Dec 2018, 15:13 Laszlo Kishalmi <[email protected] > >> wrote: > >> > >>> The only time when a PPMC member’s vote is binding is for the addition > >>> of new PPMC members and committers. Release votes are only binding to > >>> IPMC members. > >>> > >> > >> Yes, that's true. But since the first votes we've had we've used (binding) > >> and (non-binding) to indicate votes from PPMC members and not. Non-PPMC > >> members can also vote. As far as I understand it's also about acting like > >> we're ready to graduate. > > There's the key word :) Ideally, it would go like this: > > 1 - Podling votes to *motion the IPMC to release* (PPMC binding, all > other non-binding), this is what we would consider a vote in a top level > project, and would require 3x+1 from PPMC and more +1s than -1s (vetoes > are not allowed) > > 2 - Actual release vote held on general@incubator (IPMC binding, all > other non-binding), this is the Incubator singing off on the actions of > the podling, and required 3x+1 from the IPMC and more +1s than -1s. > > Once graduated, step 2 is merely removed, as oversight is no longer > deemed necessary. > > The tricky part is where IPMC votes on (1) carries over to (2), and PPMC > votes (those that are not on the IPMC) does not. This is just a bit of > slightly tricky housekeeping/math till you get the hang of it, to get > the legalities in order. > > We should consider PPMC votes binding for the *motion to release*, and > IPMC votes binding for the *vote to release*. The PPMC has to motion > (with 3x+1) the Incubator to release, so it's not as if the PPMC doesn't > have binding votes...it's just not for the release, but for the *motion > to release*...if that makes sense :) > > >> > >> We obviously still need IPMC votes to actually release once the PPMC vote > >> passes (or not). > >> > >> Best wishes, > >> > >> Neil > >> > >>> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
