Hello, On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote: > 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.
Thanks. You did not respond to my earlier question why this is so urgent after 10 years, but I guess we see what you are trying to do on the fork. If we feel this is valuable, we may vote again. Thanks for keeping that door open. I think working on a fork is the best way at this point of time. Good luck. Kind regards, Christian > > -- > 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ü >>>
