From dev-return-95954-archive-asf-public=cust-asf.ponee.io@httpd.apache.org Tue Jun 29 21:25:17 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 5822918064E for ; Tue, 29 Jun 2021 23:25:17 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id C44A2616F1 for ; Tue, 29 Jun 2021 21:25:15 +0000 (UTC) Received: (qmail 12768 invoked by uid 500); 29 Jun 2021 21:25:14 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 12755 invoked by uid 99); 29 Jun 2021 21:25:14 -0000 Received: from mailrelay1-he-de.apache.org (HELO mailrelay1-he-de.apache.org) (116.203.21.61) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jun 2021 21:25:14 +0000 Received: from [IPv6:2601:649:280:9d60:7024:9a98:9c62:9608] (unknown [IPv6:2601:649:280:9d60:7024:9a98:9c62:9608]) by mailrelay1-he-de.apache.org (ASF Mail Server at mailrelay1-he-de.apache.org) with ESMTPSA id C714E3E8A5; Tue, 29 Jun 2021 21:25:11 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: migration of the HTTPD project website From: Dave Fisher In-Reply-To: <8d4052b4-036b-a7eb-fdea-0b9b2a3c7045@wanadoo.fr> Date: Tue, 29 Jun 2021 14:23:49 -0700 Cc: Andrew Wetmore Content-Transfer-Encoding: quoted-printable Message-Id: References: <228ed0af-21f3-18ea-b0d6-2f0daf10b266@apache.org> <777E73B9-23CB-4898-8CE1-545CA17D76FD@apache.org> <8d4052b4-036b-a7eb-fdea-0b9b2a3c7045@wanadoo.fr> To: dev@httpd.apache.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Hi - > On Jun 29, 2021, at 1:17 PM, Marion & Christophe JAILLET = wrote: >=20 > Hi Dave, >=20 > Thanks for having done it. >=20 > You did faster and better than what I had started. >=20 >=20 > Here are a few details spotted here and there: > - The download page looks broken > (https://httpd.staged.apache.org/download.cgi) This is due to the staging environment not picking up the production = pickup of cgi to mirror mapping into the download.html template. >=20 > - some '&' have been turned into & > (https://httpd.staged.apache.org/dev/debugging.htmll#gcore) Fixed by switching from ``` fenced code to

>=20
>    - some extra spaces in a command (around the use of awk)
> (https://httpd.staged.apache.org/dev/release.html#how-to-do-a-release)

Removed. BTW - this page and associated scripts need to be edited to =
reflect the website being git based.

>=20
>    - a bold string left with **
>      (https://httpd.staged.apache.org/dev/styleguide.html)

Good catch Github Flavored Markdown (GFM) does not like spaces for =
emphasis. If you want to do bold italic: it=E2=80=99s =E2=80=98**_word_**'=


>=20
>    - a link that is left as [foo](bar) instead of an hypertext link
>      (at the very bottom of =
https://httpd.staged.apache.org/contributors/)

Also GFM does not do any markdown within HTML blocks. I switched from =

to ### heading. >=20 > Only the first point is an issue. It is maybe linked to the fact that = it is in staging? Yes. >=20 > 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. >=20 >=20 > 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! There were a few tweaks to obviously broken content. URLs and emails are = automatically turned to hyperlinks by GFM. > Thanks a lot. You=E2=80=99re welcome. Dave >=20 > CJ >=20 >=20 >=20 > Le 25/06/2021 =C3=A0 19:12, Dave Fisher a =C3=A9crit : >> The Migration from CMS to ASF-Pelican is staged! >>=20 >> https://httpd.staged.apache.org/ is ready. >>=20 >> https://github.com/apache/httpd-site/ >>=20 >> See the README on GitHub for details. >>=20 >> All The Best, >> Dave >>=20 >>> On Jun 22, 2021, at 11:00 AM, Dave Fisher wrote: >>>=20 >>>=20 >>>=20 >>>> On Jun 21, 2021, at 6:26 AM, Eric Covener = wrote: >>>>=20 >>>> On Sun, Jun 20, 2021 at 3:25 PM Andrew Wetmore = wrote: >>>>> Hi, Eric: >>>>>=20 >>>>> Yes, committers can use either GitHub or Gitbox. >>>>>=20 >>>>> 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 website. >>>> I was referring to "...migration process available that could = speed >>>> things along." not the overall migration off the CMS. >>>> Daniel referred to >>>> = https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features= >>>> but I didn't find any reference to "migration". >>>>=20 >>>> https://github.com/apache/httpd-site 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. >>>=20 >>> Expect more information this week. >>>=20 >>> All The Best, >>> Dave >>>=20 >>>=20