Thanks for doing the research, Bertrand. That thread describes a case (from 2019) that is virtually identical to this one.
I recommend Hop does the same as that case: remove that person’s name from the resolution, and vote them in as a PMC member after graduating. Since the effect is the same, they can do that without requiring a vote on dev@hop. For the record, my reading of the thread is that resolutions MAY include non-Apache people but the candidate project removed the non-Apache people from the resolution in order to accommodate limitations in the tooling. Julian > On Nov 29, 2021, at 9:12 AM, Bertrand Delacretaz <bdelacre...@codeconsult.ch> > wrote: > > Hi, > > On Mon, Nov 29, 2021 at 5:56 PM Julian Hyde <jhyde.apa...@gmail.com> wrote: >> ...Let’s just assume that it’s OK to include people with non-Apache email >> addresses in the graduation resolution... > > I don't think that's the case, in previous similar cases Board members > asked for the resolutions to be modified to avoid including non-apache > email addresses [1]. > > it's very easy for the PMC to fix that as soon as it's created, by > voting in the "missing" member. To me that's the safe option here. > > -Bertrand > > [1] https://lists.apache.org/thread/v7b1l27zf1xbkm45y8ryzs6pc0dwcl9g > (accessible to PMC chairs and ASF Members) > > --------------------------------------------------------------------- > 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
