I am actively working on Log4j-Audit at the moment. I am currently upgrading it 
to all the latest dependencies.  Once I commit that I will be adding in 
ElectronJS to solve the UI problem I have had with that. The upgrade only has 
one challenging aspect - The upgrade of JGit necessitates that I replace JSch 
with Apache Mina for SSH access to the Git repo. I have a need to use this to 
add audit logging to some services at work so I need to get this done asap.  I 
will probably have issues here doing a release as I have no idea if I can still 
publish the web site or perform a release given how the build process has 
changed for the other log4j projects.

I do have a task to upgrade Flume as well as add a fix for a problem that was 
reported. As you know we use Flume at my work and it needs to be upgraded. So I 
will be jumping back on this in the next couple of months.

I don’t work on Chainsaw and never have. I don’t know of anyone who plans to do 
any work on it so I do not object to archiving chainsaw.

I do have to apologize. While I try to follow the dev l& pmc lists I have had a 
terrible time following the email generated by GitHub. I currently have almost 
10,000 unread messages from GitHub for the logging project. My mailboxes for 
Maven are worse. I have 30,000 unread messages from Jira and 11,000 from 
GitHub. I’ve given up trying to keep up to date with Maven’s email.

Ralph

> On Jun 16, 2025, at 1:23 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
> 
> Hey Ralph! In the last 6 months, I haven't noticed any progress regarding
> these projects. Though you might have changes ready locally, or I might
> have missed your activity. Would you mind updating us on your progress and
> plans, please?
> 
> On Wed, Jan 15, 2025 at 2:21 PM Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
> 
>> -1 on Flume
>> 
>> Despite you not seeing visible evidence I am still working on these. I am
>> actually fairly confident I will need to create releases of Flume in the
>> next 6 months.
>> 
>> Ralph
>> 
>>> On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
>>> 
>>> Chainsaw and Flume projects have been moved to dormant state with PMC
>>> consensus. Yet their GitHub repositories (i.e., `logging-chainsaw` and
>>> `logging-flume*`) don't reflect this and they  weekly get flagged by
>> GitHub
>>> due to vulnerable dependencies. This is also confusing for users, since
>> the
>>> list of Logging Services dormant projects
>>> <https://logging.apache.org/dormant.html> and the GitHub repository
>>> statuses don't match.
>>> 
>>> *I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub
>>> repositories. Objections?*
>>> 
>>> ¹ When a GitHub project gets archived, it becomes read-only. This is a
>>> reversible operation; we can anytime unarchive these projects if PMC
>>> decides to start maintaining them again.
>> 
>> 

Reply via email to