On Thu, Aug 19, 2021 at 5:35 AM Jonathan Ellis <jbel...@gmail.com> wrote: > > Moving back to dev. > > Since it seems like there's some confusion on this point, it's perfectly > normal for PMC discussions around new proposals with decision-making > authority by the PMC to take place on the public dev list. The private > list is only necessary when confidentiality is required, and the dev list > allows non-PMC voices to be heard more readily as well as promoting > transparency on how consensus was reached. > > I am not aware of any ASF policy that would prohibit subcommittees like > this. (I'm not aware of precedent in starting one either, but as Aaron > pointed out, this *is* common at similar foundations with similar > governance goals to the ASF, and there's no reason we can't cross-pollinate > good ideas.)
Jonathan, If you keep switching from private@ to dev@ list, most of the people on dev@ list will be out of context of the replies from other PMC members on the private list. Your proposal of subcommittees has already raised strong concerns from 4 PMC members, with no one speaking in favour of it. > I am not aware of any ASF policy that would prohibit subcommittees like > this The part of your proposal of including representatives of vendors in these subcommittees goes directly against the spirit of these guidelines: https://community.apache.org/projectIndependence.html Matteo -- Matteo Merli <mme...@apache.org>
