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