Archiving inactive project repositories

[Volkan Yazıcı <vo...@yazi.ci>]

We receive automated PRs (by INFRA) for repositories associated with
inactive projects, such as Chainsaw, Log4j 1, and Log4php. I propose
archiving the following repositories:

logging-chainsaw
logging-chainsaw-site
logging-log4php-site (`logging-log4php` is already archived)
logging-log4j-audit
logging-log4j-audit-sample
logging-flume-site
logging-flume

Note that this is a reversible operation. If we decide to activate
these projects, we can un-archive them back.

Re: Archiving inactive project repositories

["Piotr P. Karwasz" <pi...@mailing.copernik.eu>]

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

Re: Archiving inactive project repositories

[Ralph Goers <ra...@dslextreme.com>]

-1 to Log4j-Audit and Flume. I began the process of upgrading Log4j-Audit a few months ago and will be working on that again shortly. I am currently working with Piotr to get Flume trimmed down to a manageable size and upgraded. 

Ralph

> On May 18, 2026, at 1:47 AM, Volkan Yazıcı <vo...@yazi.ci> wrote:
> 
> We receive automated PRs (by INFRA) for repositories associated with
> inactive projects, such as Chainsaw, Log4j 1, and Log4php. I propose
> archiving the following repositories:
> 
> logging-chainsaw
> logging-chainsaw-site
> logging-log4php-site (`logging-log4php` is already archived)
> logging-log4j-audit
> logging-log4j-audit-sample
> logging-flume-site
> logging-flume
> 
> Note that this is a reversible operation. If we decide to activate
> these projects, we can un-archive them back.