The Commons approach isn’t likely to work. Besides sharing several PMC members, it already deprecated Commons Logging in favor of Log4j2 as a logging API.
— Matt Sicker > On Dec 22, 2021, at 12:59, Dave Fisher <w...@apache.org> wrote: > > Have the initial committers for this effort been identified? > >> On Dec 22, 2021, at 10:28 AM, Vladimir Sitnikov >> <sitnikov.vladi...@gmail.com> wrote: >> >> Matt>Attaching patches to Jira is exactly how v1 was developed back in the >> day. V2 did it for some time as well before migrating to git >> >> Matt, let us please refrain from off-topic discussions here? (at the end of >> the day, this is "Looking for a champion" thread) > > IMO - this effort would not benefit from Incubation. Incubation will slow > down this effort as graduation requirements won’t fit a small and compact > community that has in mind a singular effort. > > Alternatives ways to organize this: > > (1) Get at least 3 Apache Members together (IPMC members are almost all > Apache Members) and make a Board Resolution to form a new PMC. Fork the > resources, or Logging turns them over. > > (2) Work within the Logging PMC > > (3) Ask the Commons PMC if they would take back Log4J 1.x. > > Regards, > Dave > >> >> If you have objections or comments regarding LOG4J2-3272, would you please >> comment there? >> (I truly do not understand why is it important to know how v1 or v2 >> accepted fixes back in the days) >> >> Vladimir > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
