Hi Volkan, On 18.05.2026 10:47, Volkan Yazıcı wrote: > logging-chainsaw
+1, go ahead with this one. > logging-chainsaw-site > logging-log4php-site (`logging-log4php` is already archived) > logging-flume-site We can not archive the website repos, because we need to be able to modify the content on those websites. As long as these repos provide content for logging.apache.org, we can not close them. > logging-log4j-audit > logging-log4j-audit-sample This is really up to Ralph. > logging-flume I planned to start working on it at the start of May, but because of all the security-related topics going on these days I had to defer. Starting today I am actively working on it to provide a slimmer version 2.0.0, that can be easily maintained for years. Unlike Chainsaw, which is a desktop application, we *do* have users that deploy Flume in production and we must be able to address security issues at each time, without waiting for unarchiving the repo. Piotr
