Re: `logging-parent` website

There are several reasons that a single `README.adoc` will not suffice for `logging-parent`: 1. It bundles plenty of functionality (reusable CI workflows, profiles for creating distributions, maintaining release notes, etc.) that needs to be documented. 2. It is the foundation of the n

Re: `logging-parent` website

Why does log4j-parent need a web site? Why isn’t there README in the Git repo enough? Ralph > On Sep 26, 2023, at 2:12 PM, Matt Sicker wrote: > > You can add an asf-site (and asf-staging) branch to logging-parent to get a > website published. You can create a branch in git without any commit

Re: `logging-parent` website

Right. Will indeed use the `logging-parent` repository instead. On Tue, Sep 26, 2023 at 10:01 PM Piotr P. Karwasz wrote: > Hi Volkan, > > On Tue, 26 Sept 2023 at 21:00, Volkan Yazıcı wrote: > > > > *Summary:* I want to place the website of `logging-parent` to ` > > logging.apache.org/parent`

Re: `logging-parent` website

You can add an asf-site (and asf-staging) branch to logging-parent to get a website published. You can create a branch in git without any commits in its history to start it. — Matt Sicker > On Sep 26, 2023, at 14:00, Volkan Yazıcı wrote: > > *Summary:* I want to place the website of `logging-p

Re: `logging-parent` website

Hi Volkan, On Tue, 26 Sept 2023 at 21:00, Volkan Yazıcı wrote: > > *Summary:* I want to place the website of `logging-parent` to ` > logging.apache.org/parent` served from a to-be-created > `logging-parent-site` repository. Objections? Shouldn't we use an existing repository? Wouldn't `logging-s

`logging-parent` website

*Summary:* I want to place the website of `logging-parent` to ` logging.apache.org/parent` served from a to-be-created `logging-parent-site` repository. Objections? `logging-parent` version `10.1.0` is ready to be released with plenty of features. I want it to play a role model for the rest of the