I’d be interesting in helping with this, particularly around plugin development docs which are somewhat anemic. I’ve got several things to document in a non-API-doc fashion from the new DI system and such, too.
> On Dec 18, 2023, at 1:13 PM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > *TLDR:* Log4j websites & manual will be rewritten. Feedback and support are > more than welcome. > > Starting from February, Christian, Piotr, and I will be working on > reorganizing the Log4j websites (Log4j, Log4j Scala, Log4j Tools, etc.) and > rewriting the Log4j manual. Many implementation details are still yet to be > decided and we look forward to pursuing this big undertaking with the help > of other PMC members and our community. > > I want to kick-off this project using the following agenda: > > 1. An email thread on *website & manual reorganization* – What are the > current shortcomings? Shall we have global support, security, etc. pages? > Do we need separate pages for distribution details of each project? Where > shall we place `logging-parent`? What about release instructions? > 2. An email thread on *tooling* – What are the requirements? What are > the available solutions in the market? > 3. A *video call* for resolution – Q&A. Fleshing out a plan forward. > 4. An email sharing the *conclusive plan* in detail. > > If you have general feedback that doesn't fit into aforementioned > reorganization- and tooling-related discussions, please go ahead and share > them in response to this post.
