Re: migration of the HTTPD project website

2021-06-18 Thread Dave Fisher



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 selfserve.apache.org
>> Since we do not use gitbox yet: So this would result in e.g.
>> github.com/apache/httpd-site 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 - s.apache.org/asfyaml
>> 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.

Regards,
Dave


Re: migration of the HTTPD project website

2021-06-18 Thread Daniel Gruno

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 selfserve.apache.org


Since we do not use gitbox yet: So this would result in e.g.
github.com/apache/httpd-site and users can then choose to interact
with github or gitbox.a.o, right?


Yep.




migrating the site (and using pelican/jbake/hugo??) is done also
self-serve-y via .asf.yaml - s.apache.org/asfyaml


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.


Re: migration of the HTTPD project website

2021-06-18 Thread Eric Covener
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 selfserve.apache.org

Since we do not use gitbox yet: So this would result in e.g.
github.com/apache/httpd-site and users can then choose to interact
with github or gitbox.a.o, right?

> migrating the site (and using pelican/jbake/hugo??) is done also
> self-serve-y via .asf.yaml - s.apache.org/asfyaml

A lot of info there, I see the pelican config stuff but can you give a
hint about the migration aspect there?


Re: migration of the HTTPD project website

2021-06-18 Thread Daniel Gruno

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 selfserve.apache.org
migrating the site (and using pelican/jbake/hugo??) is done also 
self-serve-y via .asf.yaml - s.apache.org/asfyaml





On Thu, Jun 17, 2021 at 9:34 AM Andrew Wetmore  wrote:


To avoid confusion because of the bad title for my previous email, here is what 
I wrote concerning your project website:

The Apache CMS system is going out of service and we really need to get the
last couple of projects off it.

I know that Christophe was working on a migration path to Pelican some
months ago, so perhaps all is well. If not, we now have an "ASF-Pelican"
template and migration process available that could speed things along.

Please let me know today where things stand with your website. Information
about the Pelican template is at https://infra.apache.org/asf-pelican.html.

(please do a reply-all, as I am not subscribed to your dev@ list.)

Thank you!

--
Andrew Wetmore
Technical Writer-Editor
Infra
Apache Software Foundation
andr...@apache.org




--
Eric Covener
cove...@gmail.com





Re: migration of the HTTPD project website

2021-06-18 Thread Eric Covener
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.


On Thu, Jun 17, 2021 at 9:34 AM Andrew Wetmore  wrote:
>
> To avoid confusion because of the bad title for my previous email, here is 
> what I wrote concerning your project website:
>
> The Apache CMS system is going out of service and we really need to get the
> last couple of projects off it.
>
> I know that Christophe was working on a migration path to Pelican some
> months ago, so perhaps all is well. If not, we now have an "ASF-Pelican"
> template and migration process available that could speed things along.
>
> Please let me know today where things stand with your website. Information
> about the Pelican template is at https://infra.apache.org/asf-pelican.html.
>
> (please do a reply-all, as I am not subscribed to your dev@ list.)
>
> Thank you!
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> Apache Software Foundation
> andr...@apache.org



--
Eric Covener
cove...@gmail.com