If we are going to mention components, shouldn't we also list Chainsaw? Gary
On Tue, Nov 12, 2024, 5:30 AM Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote: > Hi all, > > Sorry for the short notice, but only today I found the time to prepare > the board report for November. > > Unless there are some remarks, I plan to send the following report > before tomorrow's deadline. > > Summary: > > - Flume is dormant. Due to INFRA-26201[1], I am a little bit afraid to > update the website. If it fails, I'll have to restore all our other > public websites. > > - Log4j Audit is _de facto_ dormant, but I have Ralph's assurances that > some work is being done. I didn't find any public trace of this work to > report to the board. > > - Log4cxx, Log4j and Log4net: keep up the good work! > > I the near future I will contact the Apache Answer team to see if they > can open a section for us on their VM[1]. > > [1] https://issues.apache.org/jira/browse/INFRA-26201 > > [2] https://issues.apache.org/jira/browse/INFRA-25866 > > Piotr > > --------Board report-------- > > ## Description: > The mission of the Apache Logging Services project is to create and > maintain of > software for managing the logging of application behavior, and for related > software components. > > ## Project Status: > Current project status: Ongoing with high activity > Issues for the board: none > > ## Membership Data: > Apache Logging Services was founded 2003-12-17 (21 years ago) > There are currently 45 committers (17 active) > and 23 PMC (15 active) members in this project. > The Committer-to-PMC ratio is roughly 2:1 (1:1 for active members). > > Community changes, past quarter: > - No new PMC members. Last addition was Fred am Nil on 2024-08-07. > - No new committers. Last addition was Fred am Nil on 2024-02-09. > > ## Project Activity: > > Flume: > The project has been voted dormant on 2024-10-10[1]. > During the past trimester it didn't receive any bug or security reports. > > [1] https://lists.apache.org/thread/dg9wro6dp7w95o1x911lbyqxzl808b3l > > Log4cxx: > The project is active, with a moderate activity. > Recently it was integrated with Google OSS Fuzz[2] for additional security > and gained a "Release Review Guide"[3] to help PMC members without C++ > experience in the voting procedure. > There are roughly two releases a year. In the reporting period: > > log4cxx-1.3.0 was released on 2024-10-18. > > [2] https://github.com/apache/logging-log4cxx/pull/411 > [3] > > https://github.com/apache/logging-log4cxx/blob/master/admin/release-review-instructions.md > > Log4j: > The project is active, with a high activity. > Recently it was integrated with Google OSS Fuzz[3][4] for additional > security. > It currently has a roughly monthly release schedule: > > LOG4J-2.24.0 was released on 2024-09-06. > LOG4J-2.24.1 was released on 2024-09-29. > LOG4J-3.0.0-BETA3 was released on 2024-11-12. > > [4] https://github.com/apache/logging-log4j2/issues/2891 > [5] https://github.com/apache/logging-log4j2/issues/2892 > > Log4j Audit: > The project is _de facto_ dormant, although marked as active. > A single contributor is currently committed to it. > > Log4j Transform: > The project is active, with a low activity. > Its current release schedule is roughly once a year: > > LOG4J-TRANSFORM-0.2.0 was released on 2024-10-31. > > Log4net: > The project is active, with a high activity. > Recently it published a set of release review instructions[6] for PMC > members > without .NET experience. > The project released its newest 3.x version and makes roughly one release > a month: > > log4net-3.0.0 was released on 2024-09-15. > log4net-3.0.1 was released on 2024-09-27. > log4net-3.0.2 was released on 2024-10-21. > log4net-3.0.3 was released on 2024-11-07. > > [6] > https://logging.apache.org/log4net/release/release-review-instructions.html > > ## Community Health: > > Flume: > As far as we can tell, there is no community behind Flume. > > Log4cxx and Log4net: > After the recent Log4cxx and Log4net releases, we noticed a spike of > feature requests and bug reports, which confirms the presence of an active > community that follows the recent project enhancements. > > Log4j: > Since Log4j and its sub-projects use multiple repositories, the automatic > GitHub statistics don't give the real picture about the community. > After the summer break, the main Log4j repo has received and solved roughly > one issue report per working day and around 3 PRs per working day were > submitted. > Its community seems healthy and we have observed new recurring > contributors. > > Log4j Audit: > > As far as we know, there is no community behind this sub-project. > >
