On 07/01/2022 01:53, Matt Sicker wrote:

> If you had left a comment back when we voted on the EOL status
> recently, then perhaps things would be different. Waiting until
> right after the second EOL announcement makes us seem like we
> just lied about said EOL status.

On 07/01/2022 02:46, Matt Sicker wrote:
> I should also note that naming a fork “relog4j” is confusingly
> similar to “log4j”. Please don’t infringe the trademark.

One would have hoped that the Logging PMC would vote to fix outstanding critical issues in log4j 1.x and be done with it.

Instead, the PMC decided to reaffirm log4j 1.x EOL status even in the presence of multiple ASF committers/members volunteering to do the work. Ralph then stated that this was because those volunteers were not existing log4j committers but since I had commit privileges, I could volunteer, which I did.

I started working on branch log4j 1.2.18 and was vetoed down and had to revert. That's fine.

No one in their right mind would accuse the PMC of lying about the EOL status of log4j1.x. That is a formal decision which publicized for everyone to see. Having said this, the current Logging PMC is creating obstacles about the temporary revival of log4j 1.x. I don't see how you could say otherwise.

As for infringing on the log4j trademark, I will rename the repo to something else, for example "re4j".

As mentioned in my previous message, if the ASF decides to integrate "re4j" as log4j 1.x, the door is open.

--
Ceki Gülcü

—
Matt Sicker

On Jan 6, 2022, at 18:18, Ceki Gülcü <[email protected]> wrote:



Hello all,

Given the recent refusal to even consider work on a 1.2.18 branch, which would have been 
subject to PMC vote before release anyway, I have created a  separate repository on 
github under the name "relog4j1". The intent of relog4j1 is to fix existing 
critical issues in log4j 1.x.

If one day the logging PMC changes its mind and decides to integrate "relog4j1" 
as log4j 1.x, the door is open.

Those interested to contribute, please contact me directly.

Good luck and thanks for the fish.
--
Ceki Gülcü

Reply via email to