vy commented on issue #370: URL: https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074228484
> > Pages I cited are implemented in a project agnostic way. > > They really do not read like that. They are heavily oriented towards Log4j. Please feel free to make changes as see fit. You have write access to the `logging-site` repository. > > The goal is to > > Remove the maintenance burden of these pages for each project individually > > Create a coherent Download-Support-Security experience for users of all LS projects > > Is it not more important to be useful to the user than to "Remove the maintenance burden"? What I say is it **also** removes the maintenance burden. > Does it really "Remove the maintenance burden" ? Log4cxx has one website, Log4j has 6. Log4cxx doesn't even have a Security page – I hope it won't need its Log4Shell to have one. Yes, _"maintenance burden"_ is a real thing. > Is "a coherent Download-Support-Security experience for users" a thing when the user is a C++/Java/C# developer? I don't know where you get that impression from, but a big part of our users are **not** developers: system administrators (some without any programming background!), DevOps, etc. just trying to get the logging working, or upgraded, or patched, etc. of an application they happen to be responsible for taking care of. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
