Re: Archiving inactive project repositories
Ralph Goers <[email protected]> Mon, 18 May 2026 12:39:47 -0700
| Newsgroups | gmane.comp.jakarta.log4j.devel |
|---|---|
| Message-ID | <111C6F89-24FC-4B44-B1E1-E1100A549B88__26648.5424524703$1779133257$gmane$org@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ı <[email protected]> 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.