> If we now exercise our means to object [to] a nomination after it’s executed, > we have this odd unpleasant situation of the person knowing what happened.
While this is a legitimate concern, as far as I know the Board and the IPMC have not once exercised the right of veto, for hundreds if not thousands of PMC and PPMC appointments. So, let's optimize the common code path (approval without objection) over the rare path (veto from the Board/IPMC). On Sat, Oct 15, 2022 at 9:40 AM Christofer Dutz <christofer.d...@c-ware.de> wrote: > > Hi, > > Well, I guess one of the reasons for the 72 hour was, that others can express > their doubts before the person is invited. > If we now exercise our means to object a nomination after it’s executed, we > have this odd unpleasant situation of the person knowing what happened. > > But I guess we could try it and put it back in place if we see things go > south. > > Chris > > > From: Justin Mclean <jus...@classsoftware.com> > Date: Friday, 14. October 2022 at 17:39 > To: general@incubator.apache.org <general@incubator.apache.org> > Subject: Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members. > Hi, > > > I’m a bit worried that in contrast to PMCs PPMCs are usually not quite > > familiar with how things work at Apache. > > Would we still have an option to intervene, if for example one PPMC bunch > > adds people from the same company, for example? > > I have a slight concern there as well, but this would very rarely occur. The > IPMC can remove people from the PPMC if they were inappropriately added. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
