Re: migration of the HTTPD project website

2021-06-28 Thread Andrew Wetmore
Nobody ever really gets off the naughty list...

On Mon, Jun 28, 2021 at 2:40 PM Eric Covener  wrote:

> I spot checked and it looked good to me.  Thanks Dave!
>
> Can anyone else review please so we can cut over and get off the naughty
> list?
>
> On Fri, Jun 25, 2021 at 1:13 PM Dave Fisher  wrote:
> >
> > The Migration from CMS to ASF-Pelican is staged!
> >
> > https://httpd.staged.apache.org/ is ready.
> >
> > https://github.com/apache/httpd-site/
> >
> > 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 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".
> > >>
> > >> 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.
> > >
> > > Expect more information this week.
> > >
> > > All The Best,
> > > Dave
> > >
> > >
> >
>
>
> --
> Eric Covener
> cove...@gmail.com
>


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


Re: migration of the HTTPD project website

2021-06-20 Thread Andrew Wetmore
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
website.

Please write more if I am not understanding your question.

Andrew

On Fri, Jun 18, 2021 at 9:33 AM 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?
>
> > 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?
>


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


migration of the HTTPD project website

2021-06-17 Thread Andrew Wetmore
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


Re: Reply requested: Migration of the DockerHub website

2021-06-16 Thread Andrew Wetmore
Got your attention, though...

On Wed, Jun 16, 2021 at 10:43 AM Andrew Wetmore  wrote:

> hahaha it sure is. Probably an autocorrect. Apologies.
>
> On Wed, Jun 16, 2021 at 10:27 AM Eric Covener  wrote:
>
>> Hi Andrew, is "DockerHub" a typo in the subject? I assume this is
>> actually about httpd.apache.org ?
>>
>> On Wed, Jun 16, 2021 at 9:12 AM Andrew Wetmore 
>> wrote:
>> >
>> > Hi:
>> >
>> > 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
>>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Reply requested: Migration of the DockerHub website

2021-06-16 Thread Andrew Wetmore
hahaha it sure is. Probably an autocorrect. Apologies.

On Wed, Jun 16, 2021 at 10:27 AM Eric Covener  wrote:

> Hi Andrew, is "DockerHub" a typo in the subject? I assume this is
> actually about httpd.apache.org ?
>
> On Wed, Jun 16, 2021 at 9:12 AM Andrew Wetmore  wrote:
> >
> > Hi:
> >
> > 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
>


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


Reply requested: Migration of the DockerHub website

2021-06-16 Thread Andrew Wetmore
Hi:

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


Re: Your project's website

2021-01-16 Thread Andrew Wetmore
Hi, and happy New Year.

Is there any further progress on migrating the project website?

Andrew

On 2020/11/11 17:32:05, Marion & Christophe JAILLET 
 wrote: 
> Hi,
> 
> I have something that seems to work pretty well on my machine.
> 
> The main steps done so far are:
> 
>     - install pelican
> 
>     - move, as-is, the content of the old CMS into the content/pages/ 
> directory of pelican
> 
>     - rename .mdtext files into .md files
>   find . -name '*.mdtext' -exec sh -c 'mv "$0" "${0%.mdtext}.md"' {} \;
> 
>     - copy the 'simple' template from pelican
> 
>     - tweak the base.html and page.html from this template
> 
>     - move some css and images in the static/css and static/images 
> directories of the theme template
> 
>     - move the the 'navigation.mdtext' from the template directory of 
> the old CMS to the content/pages/ directory in order to keep its 
> markdown syntax
>      (I've not been able to use Markdown within the template, and I've 
> adapted the solution proposed in 
> https://stackoverflow.com/questions/60759348/how-to-include-a-markdown-file-in-index-html)
> 
>     - make some tweak here and there (the {.centered} in the main 
> index.md file doesn't work the same for exemple)
> 
> Still need some testing but the result is visually the same for what 
> have looked at.
> 
> To be continued.
> 
> CJ
> 
> 
> Le 10/11/2020 à 21:21, Marion & Christophe JAILLET a écrit :
> >
> > Hi,
> >
> > I'll try to give a look at Pelican to see what I can get out of it.
> > I agree with Daniel that it shouldn't be to difficult. But it may take 
> > some time to install/test/tweak the site as I've never used Pelican 
> > before.
> >
> > Moreover, we have some scripts that update the CMS when we make a 
> > release that will need some attention too.
> >
> > CJ
> >
> > Le 10/11/2020 à 15:22, Andrew Wetmore a écrit :
> >> Hi, all:
> >>
> >> Any progress on the site migration? Is there a Jira ticket for 
> >> tracking this work?
> >>
> >> Thanks in advance.
> >>
> >> Andrew
> >>
> >> On Tue, Aug 18, 2020 at 10:59 AM Andrew Wetmore  >> <mailto:andr...@apache.org>> wrote:
> >>
> >> Hi:
> >>
> >> Any progress finding someone to handle the site migration?
> >> Initial steps include:
> >>
> >> - deciding what technology to move to, either Pelican, Hugo,
> >> GitHub Pages or some other static site generator
> >> - recording a formal PMC decision to make the move
> >> - opening a Jira ticket for INFRA to help us track what we need
> >> to do to facilitate the move.
> >>
> >> Thanks!
> >>
> >> Andrew
> >>
> >> On Wed, Aug 5, 2020 at 9:17 AM Andrew Wetmore  >> <mailto:andr...@apache.org>> wrote:
> >>
> >> Hi:
> >>
> >> I am part of the Infrastructure team, and am writing to ask
> >> whether your project is still using the Apache CMS for your
> >> project website. As you know, the CMS is reaching
> >> end-of-life, and we need projects to move their websites onto
> >> a different option within the next few weeks.
> >>
> >> There are several alternatives available, including those
> >> listed on this page [1] on managing project websites. Infra
> >> is assembling a Wiki page [2] on migrating a website from the
> >> CMS, and is looking forward to helping projects with this
> >> transition.
> >>
> >> Please let me know whether your site is still on the Apache
> >> CMS and, if so, who will be the project point-of-contact with
> >> Infra for the migration.
> >>
> >> Thank you!
> >>
> >>
> >>
> >>
> >> [1] https://infra.apache.org/project-site.html
> >> <https://infra.apache.org/project-site.html>
> >>
> >> [2]
> >>     
> >> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> >> 
> >> <https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS>
> >>
> >>
> >>
> >> -- 
> >> Andrew Wetmore
> >> Technical Writer-Editor
> >> Infra
> >> *Apache Software Foundation*
> >> andr...@apache.org <mailto:andr...@apache.org>
> >>
> >> 
> >> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> >>Virus-free. www.avast.com
> >> 
> >> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> >>
> >>
> >>
> >>
> >> -- 
> >> Andrew Wetmore
> >> Technical Writer-Editor
> >> Infra
> >> *Apache Software Foundation*
> >> andr...@apache.org <mailto:andr...@apache.org>
> >>
> >>
> >>
> >> -- 
> >> Andrew Wetmore
> >> Technical Writer-Editor
> >> Infra
> >> *Apache Software Foundation*
> >> andr...@apache.org <mailto:andr...@apache.org>
> 


Re: Your project's website

2020-11-11 Thread Andrew Wetmore
This is good to hear.

Is there a Jira ticket where you all are tracking progress?

a

On Wed, Nov 11, 2020 at 1:32 PM Marion & Christophe JAILLET <
christophe.jail...@wanadoo.fr> wrote:

> Hi,
>
> I have something that seems to work pretty well on my machine.
>
> The main steps done so far are:
>
>- install pelican
>
>- move, as-is, the content of the old CMS into the content/pages/
> directory of pelican
>
>- rename .mdtext files into .md files
>  find . -name '*.mdtext' -exec sh -c 'mv "$0" "${0%.mdtext}.md"' {} \;
>
>- copy the 'simple' template from pelican
>
>- tweak the base.html and page.html from this template
>
>- move some css and images in the static/css and static/images
> directories of the theme template
>
>- move the the 'navigation.mdtext' from the template directory of the
> old CMS to the content/pages/ directory in order to keep its markdown syntax
> (I've not been able to use Markdown within the template, and I've
> adapted the solution proposed in
> https://stackoverflow.com/questions/60759348/how-to-include-a-markdown-file-in-index-html
> )
>
>- make some tweak here and there (the {.centered} in the main index.md
> file doesn't work the same for exemple)
>
> Still need some testing but the result is visually the same for what have
> looked at.
>
> To be continued.
>
> CJ
>
>
> Le 10/11/2020 à 21:21, Marion & Christophe JAILLET a écrit :
>
> Hi,
>
> I'll try to give a look at Pelican to see what I can get out of it.
> I agree with Daniel that it shouldn't be to difficult. But it may take
> some time to install/test/tweak the site as I've never used Pelican before.
>
> Moreover, we have some scripts that update the CMS when we make a release
> that will need some attention too.
>
> CJ
> Le 10/11/2020 à 15:22, Andrew Wetmore a écrit :
>
> Hi, all:
>
> Any progress on the site migration? Is there a Jira ticket for tracking
> this work?
>
> Thanks in advance.
>
> Andrew
>
> On Tue, Aug 18, 2020 at 10:59 AM Andrew Wetmore 
> wrote:
>
>> Hi:
>>
>> Any progress finding someone to handle the site migration? Initial steps
>> include:
>>
>> - deciding what technology to move to, either Pelican, Hugo, GitHub Pages
>> or some other static site generator
>> - recording a formal PMC decision to make the move
>> - opening a Jira ticket for INFRA to help us track what we need to do to
>> facilitate the move.
>>
>> Thanks!
>>
>> Andrew
>>
>> On Wed, Aug 5, 2020 at 9:17 AM Andrew Wetmore  wrote:
>>
>>> Hi:
>>>
>>> I am part of the Infrastructure team, and am writing to ask whether your
>>> project is still using the Apache CMS for your project website. As you
>>> know, the CMS is reaching end-of-life, and we need projects to move their
>>> websites onto a different option within the next few weeks.
>>>
>>> There are several alternatives available, including those listed on this
>>> page [1] on managing project websites. Infra is assembling a Wiki page [2]
>>> on migrating a website from the CMS, and is looking forward to helping
>>> projects with this transition.
>>>
>>> Please let me know whether your site is still on the Apache CMS and, if
>>> so, who will be the project point-of-contact with Infra for the migration.
>>>
>>> Thank you!
>>>
>>>
>>>
>>>
>>> [1] https://infra.apache.org/project-site.html
>>>
>>> [2]
>>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>>
>>>
>>>
>>> --
>>> Andrew Wetmore
>>> Technical Writer-Editor
>>> Infra
>>> *Apache Software Foundation*
>>> andr...@apache.org
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>  Virus-free.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>
>>
>>
>> --
>> Andrew Wetmore
>> Technical Writer-Editor
>> Infra
>> *Apache Software Foundation*
>> andr...@apache.org
>>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
>

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


Re: Your project's website

2020-11-10 Thread Andrew Wetmore
Hi, all:

Any progress on the site migration? Is there a Jira ticket for tracking
this work?

Thanks in advance.

Andrew

On Tue, Aug 18, 2020 at 10:59 AM Andrew Wetmore  wrote:

> Hi:
>
> Any progress finding someone to handle the site migration? Initial steps
> include:
>
> - deciding what technology to move to, either Pelican, Hugo, GitHub Pages
> or some other static site generator
> - recording a formal PMC decision to make the move
> - opening a Jira ticket for INFRA to help us track what we need to do to
> facilitate the move.
>
> Thanks!
>
> Andrew
>
> On Wed, Aug 5, 2020 at 9:17 AM Andrew Wetmore  wrote:
>
>> Hi:
>>
>> I am part of the Infrastructure team, and am writing to ask whether your
>> project is still using the Apache CMS for your project website. As you
>> know, the CMS is reaching end-of-life, and we need projects to move their
>> websites onto a different option within the next few weeks.
>>
>> There are several alternatives available, including those listed on this
>> page [1] on managing project websites. Infra is assembling a Wiki page [2]
>> on migrating a website from the CMS, and is looking forward to helping
>> projects with this transition.
>>
>> Please let me know whether your site is still on the Apache CMS and, if
>> so, who will be the project point-of-contact with Infra for the migration.
>>
>> Thank you!
>>
>>
>>
>>
>> [1] https://infra.apache.org/project-site.html
>>
>> [2]
>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>
>>
>>
>> --
>> Andrew Wetmore
>> Technical Writer-Editor
>> Infra
>> *Apache Software Foundation*
>> andr...@apache.org
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>> <#m_-2274869948141066594_m_127898873357530255_m_-4425529938707489318_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>


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


Re: Your project's website

2020-08-18 Thread Andrew Wetmore
Hi:

Any progress finding someone to handle the site migration? Initial steps
include:

- deciding what technology to move to, either Pelican, Hugo, GitHub Pages
or some other static site generator
- recording a formal PMC decision to make the move
- opening a Jira ticket for INFRA to help us track what we need to do to
facilitate the move.

Thanks!

Andrew

On Wed, Aug 5, 2020 at 9:17 AM Andrew Wetmore  wrote:

> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if
> so, who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_127898873357530255_m_-4425529938707489318_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


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


Your project's website

2020-08-05 Thread Andrew Wetmore
Hi:

I am part of the Infrastructure team, and am writing to ask whether your
project is still using the Apache CMS for your project website. As you
know, the CMS is reaching end-of-life, and we need projects to move their
websites onto a different option within the next few weeks.

There are several alternatives available, including those listed on this
page [1] on managing project websites. Infra is assembling a Wiki page [2]
on migrating a website from the CMS, and is looking forward to helping
projects with this transition.

Please let me know whether your site is still on the Apache CMS and, if so,
who will be the project point-of-contact with Infra for the migration.

Thank you!




[1] https://infra.apache.org/project-site.html

[2]
https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS



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

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>