The Logging Services project is an “umbrella” project that manages all the logging projects, including Log4j 1.x. We would not be in favor of having Log4j 1.x become a new standalone PMC.
But yes, any Logging Services PMC member can veto a code change in any of the sub-projects. I don’t know that it has ever happened. Ralph > On Dec 19, 2021, at 2:13 PM, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> > wrote: > >> All new ASF projects go through the incubator. Sub-projects don’t have to > but when an entirely new community is being > > I'm a member of PMC Calcite and JMeter, however, I have not submitted > projects to the incubator yet. > >> Once graduated the podling > PMC members would become part of the Logging Services PMC. > > Does that mean the current members of Logging Services PMC could veto code > changes in the "new" log4j1? > That sounds strange, and it defeats the reason to re-establish the new set > of PMC members for log4j 1.x > > Vladimir
