httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <>
Subject Re: migration of the HTTPD project website
Date Fri, 18 Jun 2021 13:32:47 GMT

Sent from my iPhone

> On Jun 18, 2021, at 5:35 AM, Daniel Gruno <> wrote:
> On 18/06/2021 14.33, Eric Covener wrote:
>>> On Fri, Jun 18, 2021 at 8:20 AM Daniel Gruno <> wrote:
>>> On 18/06/2021 14.16, Eric Covener wrote:
>>>> I reviewed Christophes old post, I think we should proceed with the
>>>> ASF template and migration process. Worst case Christophe can still
>>>> apply what he has learned to further refine the output of the
>>>> migration.
>>>> I'll create an infra ticket to ask for the repo and migration on
>>>> Monday unless someone objects.
>>> repo request is done via
>> Since we do not use gitbox yet: So this would result in e.g.
>> and users can then choose to interact
>> with github or gitbox.a.o, right?
> Yep.

The repository is already created.

>>> migrating the site (and using pelican/jbake/hugo??) is done also
>>> self-serve-y via .asf.yaml -
>> A lot of info there, I see the pelican config stuff but can you give a
>> hint about the migration aspect there?
> The migration would largely just happen automatically once .asf.yaml is in place and
working. There is some httpd docs aliasing that infra needs to figure out, but that's tangential
to this.

Your whole approach to the security pages will need to change. You will need to produce the
html as a separate step.

Also the mdtext files need to be converted to md with a manual review in order to catch the
discrepancies between the CMS’s flavor of markdown and the GFM.


View raw message