httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marion & Christophe JAILLET <>
Subject Re: migration of the HTTPD project website
Date Tue, 29 Jun 2021 20:17:29 GMT
Hi Dave,

Thanks for having done it.

You did faster and better than what I had started.

Here are a few details spotted here and there:
    - The download page looks broken

    - some '&' have been turned into &amp;

    - some extra spaces in a command (around the use of awk)

    - a bold string left with **

    - a link that is left as [foo](bar) instead of an hypertext link
      (at the very bottom of

Only the first point is an issue. It is maybe linked to the fact that it 
is in staging?

I guess that all the other tiny things could be fixed easily but don't 
have time to look at it by myself in the coming days/weeks.

I don't know if you hand modified a few things, but several places looks 
better now (some spacing between paragraphs which are smaller now, some 
alignment, some missing spaces between words that have been fixed, some 
numbering that were broken and fixed now, some links that have been 
added for URL or mails). So, great work!

Thanks a lot.


Le 25/06/2021 à 19:12, Dave Fisher a écrit :
> The Migration from CMS to ASF-Pelican is staged!
> is ready.
> See the README on GitHub for details.
> All The Best,
> Dave
>> On Jun 22, 2021, at 11:00 AM, Dave Fisher <> wrote:
>>> On Jun 21, 2021, at 6:26 AM, Eric Covener <> wrote:
>>> On Sun, Jun 20, 2021 at 3:25 PM Andrew Wetmore <> wrote:
>>>> Hi, Eric:
>>>> Yes, committers can use either GitHub or Gitbox.
>>>> I am not sure what the "can you give a hint about the migration aspect" means.
Maybe I was not clear. We have to move all projects off the Apache CMS and to some other technology,
such as Pelican. Infra can help with that move to a Git repository. Sometime this summer the
Apache CMS will stop functioning, which would mean you would have a hard time updating your
>>> I was referring to  "...migration process available that could speed
>>> things along." not the overall migration off the CMS.
>>> Daniel referred to
>>> but I didn't find any reference to "migration".
>>> was created but it's empty.  I
>>> was assuming we'd have some starting point based on the CMS-based site
>>> content and whatever additional template/scaffolding is needed that
>>> we'd be able to see w/o replacing our currently published site.
>>> I don't want anyone to start from scratch if there's a better way to
>>> get started.
>> I have the go ahead to do the migration for you. The goal is to create a staged site
that will be nearly identical to your current site.
>> Expect more information this week.
>> All The Best,
>> Dave

View raw message