Re: your project website

[Roy Lenferink]

Hi Andrew,

As confirmed by others; the website of the Directory project moved away
from the CMS about two weeks ago.

For more info:
https://github.com/apache/infrastructure-p6/commit/033a23c19c14a99eaac7190d28cb1c10702ea3e2
https://the-asf.slack.com/archives/CBX4TSBQ8/p1608915510090200

Roy

Op vr 8 jan. 2021 om 14:05 schreef Emmanuel Lécharny :

> Hi and Happy New year !
>
>
> The web site has already been migrated (thanks to Roy and Stefan hard
> work), and we are now cleaning up the few remaining broken links and
> typoes (yesterday, we had 49 broken links, most of them being defunct
> conference links and personnal web sites)
>
>
> On 07/01/2021 13:33, Andrew Wetmore wrote:
> > Hi, and happy New Year!
> >
> > Any progress on migrating your project website off the CMS?
> >
> > Andrew
> >
> > On Mon, Aug 17, 2020 at 9:20 AM Roy Lenferink  > <mailto:rlenfer...@apache.org>> wrote:
> >
> >
> >
> > Op ma 10 aug. 2020 om 19:11 schreef Shawn McKinney
> > mailto:smckin...@apache.org>>:
> >
> >
> > > On Aug 8, 2020, at 3:30 AM, Roy Lenferink
> > mailto:rlenfer...@apache.org>> wrote:
> > >
> > > I just updated https://github.com/rlenferink/directory-site
> > <https://github.com/rlenferink/directory-site> to include the
> > full svn history with the latest changes.
> > > The gen-docs are not included (yet) but they can be stored
> > on a separate branch (e.g. for contributors to do a clone with
> > --single-branch to prevent
> > > having to clone all gen-docs documentation).
> > >
> > > I am willing to take a look at this as well.
> >
> > Thanks Roy.  I’m willing to work a bit on this as well but
> > can’t commit to a timeframe just yet.
> >
> >
> > Great! Something from $work came up so unfortunately I wasn't able
> > to work on the gen-docs stuff yet.
> >
> >
> > We also need to get buy-in from the project team, as in a vote.
> >
> >
> > I'll start a vote sometime soon. For the gen-docs we can always
> > iterate till it's perfect :)
> >
> >
> > —
> > Shawn
> >
>  -
> > To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
> > <mailto:dev-unsubscr...@directory.apache.org>
> > For additional commands, e-mail: dev-h...@directory.apache.org
> > <mailto:dev-h...@directory.apache.org>
> >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org <mailto:andr...@apache.org>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
> For additional commands, e-mail: dev-h...@directory.apache.org
>
>

Re: your project website

[Emmanuel Lécharny]

Hi and Happy New year !


The web site has already been migrated (thanks to Roy and Stefan hard 
work), and we are now cleaning up the few remaining broken links and 
typoes (yesterday, we had 49 broken links, most of them being defunct 
conference links and personnal web sites)



On 07/01/2021 13:33, Andrew Wetmore wrote:

Hi, and happy New Year!

Any progress on migrating your project website off the CMS?

Andrew

On Mon, Aug 17, 2020 at 9:20 AM Roy Lenferink <mailto:rlenfer...@apache.org>> wrote:




Op ma 10 aug. 2020 om 19:11 schreef Shawn McKinney
mailto:smckin...@apache.org>>:


> On Aug 8, 2020, at 3:30 AM, Roy Lenferink
mailto:rlenfer...@apache.org>> wrote:
>
> I just updated https://github.com/rlenferink/directory-site
<https://github.com/rlenferink/directory-site> to include the
full svn history with the latest changes.
> The gen-docs are not included (yet) but they can be stored
on a separate branch (e.g. for contributors to do a clone with
--single-branch to prevent
> having to clone all gen-docs documentation).
>
> I am willing to take a look at this as well.

Thanks Roy.  I’m willing to work a bit on this as well but
can’t commit to a timeframe just yet.


Great! Something from $work came up so unfortunately I wasn't able
to work on the gen-docs stuff yet.


We also need to get buy-in from the project team, as in a vote.


I'll start a vote sometime soon. For the gen-docs we can always
iterate till it's perfect :)


—
Shawn
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
<mailto:dev-unsubscr...@directory.apache.org>
For additional commands, e-mail: dev-h...@directory.apache.org
<mailto:dev-h...@directory.apache.org>



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


-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Stefan Seelmann]

On 1/7/21 1:33 PM, Andrew Wetmore wrote:
> Any progress on migrating your project website off the CMS?

Yes, thanks to Roy it's done.

Kind Regards,
Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Andrew Wetmore]

Hi, and happy New Year!

Any progress on migrating your project website off the CMS?

Andrew

On Mon, Aug 17, 2020 at 9:20 AM Roy Lenferink  wrote:

>
>
> Op ma 10 aug. 2020 om 19:11 schreef Shawn McKinney :
>
>>
>> > On Aug 8, 2020, at 3:30 AM, Roy Lenferink 
>> wrote:
>> >
>> > I just updated https://github.com/rlenferink/directory-site to include
>> the full svn history with the latest changes.
>> > The gen-docs are not included (yet) but they can be stored on a
>> separate branch (e.g. for contributors to do a clone with --single-branch
>> to prevent
>> > having to clone all gen-docs documentation).
>> >
>> > I am willing to take a look at this as well.
>>
>> Thanks Roy.  I’m willing to work a bit on this as well but can’t commit
>> to a timeframe just yet.
>>
>
> Great! Something from $work came up so unfortunately I wasn't able to work
> on the gen-docs stuff yet.
>
>
>>
>> We also need to get buy-in from the project team, as in a vote.
>>
>
> I'll start a vote sometime soon. For the gen-docs we can always iterate
> till it's perfect :)
>
>
>>
>> —
>> Shawn
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
>> For additional commands, e-mail: dev-h...@directory.apache.org
>>
>>

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

Re: your project website

[Roy Lenferink]

Op ma 10 aug. 2020 om 19:11 schreef Shawn McKinney :

>
> > On Aug 8, 2020, at 3:30 AM, Roy Lenferink  wrote:
> >
> > I just updated https://github.com/rlenferink/directory-site to include
> the full svn history with the latest changes.
> > The gen-docs are not included (yet) but they can be stored on a separate
> branch (e.g. for contributors to do a clone with --single-branch to prevent
> > having to clone all gen-docs documentation).
> >
> > I am willing to take a look at this as well.
>
> Thanks Roy.  I’m willing to work a bit on this as well but can’t commit to
> a timeframe just yet.
>

Great! Something from $work came up so unfortunately I wasn't able to work
on the gen-docs stuff yet.


>
> We also need to get buy-in from the project team, as in a vote.
>

I'll start a vote sometime soon. For the gen-docs we can always iterate
till it's perfect :)


>
> —
> Shawn
> -
> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
> For additional commands, e-mail: dev-h...@directory.apache.org
>
>

Re: your project website

[Shawn McKinney]

> On Aug 8, 2020, at 3:30 AM, Roy Lenferink  wrote:
> 
> I just updated https://github.com/rlenferink/directory-site to include the 
> full svn history with the latest changes.
> The gen-docs are not included (yet) but they can be stored on a separate 
> branch (e.g. for contributors to do a clone with --single-branch to prevent
> having to clone all gen-docs documentation).
>  
> I am willing to take a look at this as well.

Thanks Roy.  I’m willing to work a bit on this as well but can’t commit to a 
timeframe just yet.

We also need to get buy-in from the project team, as in a vote.

—
Shawn
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Roy Lenferink]

Op vr 7 aug. 2020 om 15:00 schreef Roy Lenferink :

> Hi Shawn,
>
> Op vr 7 aug. 2020 om 14:29 schreef Shawn McKinney :
>
>>
>>
>> > On Aug 6, 2020, at 3:11 PM, Roy Lenferink 
>> wrote:
>> >
>> > Maybe you missed my message in this thread :)
>> >
>> > My response was more or less that february this year I tried converting
>> the Directory website to use a static site generator. At that moment
>> Emmanuel's response was to see how it went with MINA (already migrated off
>> the CMS) before continuing with Directory. This because the two projects
>> have more or less a similar design.
>> >
>>
>> Hi Roy,
>>
>> No I didn’t miss the message, I have viewed the artifacts, they look good
>> FWICT.
>>
>> Where my confusion lies is what are the next steps?  It appears you are
>> offering to do the conversion for us which is a very kind offer.
>>
>
> The next steps I am willing to help out with.The history is preferably
> included. That is something I am willing to do.
> Also, the changes between february and now also need to be included (and
> now overwritten).
> While working on including the history I am willing to help out with that
> as well.
>

I just updated https://github.com/rlenferink/directory-site to include the
full svn history with the latest changes.
The gen-docs are not included (yet) but they can be stored on a separate
branch (e.g. for contributors to do a clone with --single-branch to prevent
having to clone all gen-docs documentation).

I am willing to take a look at this as well.


>
>> But, what happens after that conversion?  How do we make changes, what is
>> the workflow, …?
>>
>
> The non-CMS workflow is that the generated site is available in version
> control on the 'asf-site' branch.
> The sources for generating the site are in the repository its default
> branch.
>
> For Apache Celix we created a Jenkins job which generates the site when
> changes are committed to the master branch:
> https://ci-builds.apache.org/job/Celix/job/site/job/master/
>
> The Jenkins job pushes the generated site to the 'asf-site' branch, which
> infra tooling then will pickup for serving the actual site.
>
> So in case of a new release, the simplest task is updating the version
> number here:
> https://github.com/rlenferink/directory-site/blob/master/config.toml#L36
>
> I made it configurable so that there is only a single definition of a
> subproject its version throughout the whole site.
>
> Other website content is available as it is right now as well, in Markdown:
> https://github.com/rlenferink/directory-site/tree/master/source
>
>
>>
>> Perhaps it’s not confusion as much as concerns:
>>
>> 1.  That we won’t be able to maintain, or have significant difficulty
>> maintaining, thus making it difficult to do a release.
>>
>> 2. The process to make changes to one subproject impacts another
>> subproject in unforeseen ways.
>>
>
> The layouts/designs for the different subprojects are still available:
> https://github.com/rlenferink/directory-site/tree/master/layouts
>
> This means it is still possible to change the style of a subcomponent
> without breaking the whole website.
>
> The website sources for the different subprojects are in the same
> repository but that is the same as it is right now with the CMS.
>
>
>>
>> Perhaps my concerns are unwarranted, but at this point there seems to be
>> more of a risk than reward.
>>
>
> No problem asking! Better to have things clarified upfront.
>
>
>>
>> OTOH I clearly understand the imperative to get off of an obsolete CMS.
>> So it’s not a question of if but when.
>>
>> > The following repo contains the Directory site converted to Hugo:
>> https://github.com/rlenferink/directory-site
>> >
>> > Steps that I will take before it may be useful:
>> > - Include SVN history (history is always useful, especially if someone
>> wants to see why a specific change was made)
>> > - Update to include latest SVN changes.
>> >
>> > Some threads about moving from the CMS to Git/static site generator:
>> >
>> https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
>> >
>> https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E
>> >
>> https://lists.apache.org/thread.html/rf0d4fef9b65e1ef346bc71b66253f9e54f15e048be6d011751a24ae0%40%3Cdev.community.apache.org%3E
>> >
>> https://lists.apache.org/thread.html/r2f2874ca9dc2dcf04970f59c5efdece9d14afc4b2193b4a0a108dcd9%40%3Cdev.jena.apache.org%3E
>> >
>> > Let me know if you need some additional info from my side.
>>
>>

Re: your project website

[Roy Lenferink]

Hi Shawn,

Op vr 7 aug. 2020 om 14:29 schreef Shawn McKinney :

>
>
> > On Aug 6, 2020, at 3:11 PM, Roy Lenferink 
> wrote:
> >
> > Maybe you missed my message in this thread :)
> >
> > My response was more or less that february this year I tried converting
> the Directory website to use a static site generator. At that moment
> Emmanuel's response was to see how it went with MINA (already migrated off
> the CMS) before continuing with Directory. This because the two projects
> have more or less a similar design.
> >
>
> Hi Roy,
>
> No I didn’t miss the message, I have viewed the artifacts, they look good
> FWICT.
>
> Where my confusion lies is what are the next steps?  It appears you are
> offering to do the conversion for us which is a very kind offer.
>

The next steps I am willing to help out with.The history is preferably
included. That is something I am willing to do.
Also, the changes between february and now also need to be included (and
now overwritten).
While working on including the history I am willing to help out with that
as well.


> But, what happens after that conversion?  How do we make changes, what is
> the workflow, …?
>

The non-CMS workflow is that the generated site is available in version
control on the 'asf-site' branch.
The sources for generating the site are in the repository its default
branch.

For Apache Celix we created a Jenkins job which generates the site when
changes are committed to the master branch:
https://ci-builds.apache.org/job/Celix/job/site/job/master/

The Jenkins job pushes the generated site to the 'asf-site' branch, which
infra tooling then will pickup for serving the actual site.

So in case of a new release, the simplest task is updating the version
number here:
https://github.com/rlenferink/directory-site/blob/master/config.toml#L36

I made it configurable so that there is only a single definition of a
subproject its version throughout the whole site.

Other website content is available as it is right now as well, in Markdown:
https://github.com/rlenferink/directory-site/tree/master/source


>
> Perhaps it’s not confusion as much as concerns:
>
> 1.  That we won’t be able to maintain, or have significant difficulty
> maintaining, thus making it difficult to do a release.
>
> 2. The process to make changes to one subproject impacts another
> subproject in unforeseen ways.
>

The layouts/designs for the different subprojects are still available:
https://github.com/rlenferink/directory-site/tree/master/layouts

This means it is still possible to change the style of a subcomponent
without breaking the whole website.

The website sources for the different subprojects are in the same
repository but that is the same as it is right now with the CMS.


>
> Perhaps my concerns are unwarranted, but at this point there seems to be
> more of a risk than reward.
>

No problem asking! Better to have things clarified upfront.


>
> OTOH I clearly understand the imperative to get off of an obsolete CMS.
> So it’s not a question of if but when.
>
> > The following repo contains the Directory site converted to Hugo:
> https://github.com/rlenferink/directory-site
> >
> > Steps that I will take before it may be useful:
> > - Include SVN history (history is always useful, especially if someone
> wants to see why a specific change was made)
> > - Update to include latest SVN changes.
> >
> > Some threads about moving from the CMS to Git/static site generator:
> >
> https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
> >
> https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E
> >
> https://lists.apache.org/thread.html/rf0d4fef9b65e1ef346bc71b66253f9e54f15e048be6d011751a24ae0%40%3Cdev.community.apache.org%3E
> >
> https://lists.apache.org/thread.html/r2f2874ca9dc2dcf04970f59c5efdece9d14afc4b2193b4a0a108dcd9%40%3Cdev.jena.apache.org%3E
> >
> > Let me know if you need some additional info from my side.
>
>

Re: your project website

[Shawn McKinney]

> On Aug 6, 2020, at 3:11 PM, Roy Lenferink  wrote:
> 
> Maybe you missed my message in this thread :)
> 
> My response was more or less that february this year I tried converting the 
> Directory website to use a static site generator. At that moment Emmanuel's 
> response was to see how it went with MINA (already migrated off the CMS) 
> before continuing with Directory. This because the two projects have more or 
> less a similar design.
> 

Hi Roy,

No I didn’t miss the message, I have viewed the artifacts, they look good FWICT.

Where my confusion lies is what are the next steps?  It appears you are 
offering to do the conversion for us which is a very kind offer.

But, what happens after that conversion?  How do we make changes, what is the 
workflow, …?

Perhaps it’s not confusion as much as concerns:

1.  That we won’t be able to maintain, or have significant difficulty 
maintaining, thus making it difficult to do a release.  

2. The process to make changes to one subproject impacts another subproject in 
unforeseen ways.

Perhaps my concerns are unwarranted, but at this point there seems to be more 
of a risk than reward.

OTOH I clearly understand the imperative to get off of an obsolete CMS.  So 
it’s not a question of if but when.

> The following repo contains the Directory site converted to Hugo: 
> https://github.com/rlenferink/directory-site
> 
> Steps that I will take before it may be useful:
> - Include SVN history (history is always useful, especially if someone wants 
> to see why a specific change was made)
> - Update to include latest SVN changes.
> 
> Some threads about moving from the CMS to Git/static site generator:
> https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
> https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E
> https://lists.apache.org/thread.html/rf0d4fef9b65e1ef346bc71b66253f9e54f15e048be6d011751a24ae0%40%3Cdev.community.apache.org%3E
> https://lists.apache.org/thread.html/r2f2874ca9dc2dcf04970f59c5efdece9d14afc4b2193b4a0a108dcd9%40%3Cdev.jena.apache.org%3E
> 
> Let me know if you need some additional info from my side.


-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Roy Lenferink]

Hi Shawn,

Maybe you missed my message in this thread :)

My response was more or less that february this year I tried converting the
Directory website to use a static site generator. At that moment Emmanuel's
response was to see how it went with MINA (already migrated off the CMS)
before continuing with Directory. This because the two projects have more
or less a similar design.

The following repo contains the Directory site converted to Hugo:
https://github.com/rlenferink/directory-site

Steps that I will take before it may be useful:
- Include SVN history (history is always useful, especially if someone
wants to see why a specific change was made)
- Update to include latest SVN changes.

Some threads about moving from the CMS to Git/static site generator:
https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E
https://lists.apache.org/thread.html/rf0d4fef9b65e1ef346bc71b66253f9e54f15e048be6d011751a24ae0%40%3Cdev.community.apache.org%3E
https://lists.apache.org/thread.html/r2f2874ca9dc2dcf04970f59c5efdece9d14afc4b2193b4a0a108dcd9%40%3Cdev.jena.apache.org%3E

Let me know if you need some additional info from my side.

Roy

Op do 6 aug. 2020 om 17:43 schreef Shawn McKinney :

>
>
> > On Aug 6, 2020, at 8:40 AM, Andrew Wetmore  wrote:
> >
> > There are several technologies that, once set up, make it remarkably
> easy to edit, expand, and publish your website.
>
> A bit +1 for easy!!
>
> Current process is a bit tricky.
>
> > Infra uses Pelican and Buildbot, and I find 90% of the process invisible
> and almost instantaneous. Several projects use Hugo, with the same good
> usability.
>
> Especially when it brings a good feature set.
>
> OK, I’ll do a bit of of research into these.  I have a colleague,
> Maryanne, who has also agreed to have a look and unlike me has expertise in
> CMS.  :-)
>
> > If your repository is on Git, there are good continuous-integration
> features Infra has put in place and will help you deploy.
>
> Currently, we use SVN for storing repo artifacts, although most of our
> sub-projects have long used GIT for managing their source.
>
> I’d definitely be in favor of moving to git for website artifacts.
>
> Thanks,
> —
> Shawn
> -
> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
> For additional commands, e-mail: dev-h...@directory.apache.org
>
>

Re: your project website

[Shawn McKinney]

> On Aug 6, 2020, at 8:40 AM, Andrew Wetmore  wrote:
> 
> There are several technologies that, once set up, make it remarkably easy to 
> edit, expand, and publish your website.

A bit +1 for easy!!

Current process is a bit tricky.

> Infra uses Pelican and Buildbot, and I find 90% of the process invisible and 
> almost instantaneous. Several projects use Hugo, with the same good usability.

Especially when it brings a good feature set.  

OK, I’ll do a bit of of research into these.  I have a colleague, Maryanne, who 
has also agreed to have a look and unlike me has expertise in CMS.  :-)

> If your repository is on Git, there are good continuous-integration features 
> Infra has put in place and will help you deploy.

Currently, we use SVN for storing repo artifacts, although most of our 
sub-projects have long used GIT for managing their source.

I’d definitely be in favor of moving to git for website artifacts.

Thanks,
—
Shawn
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Andrew Wetmore]

Hi, Shawn:

There are several technologies that, once set up, make it remarkably easy
to edit, expand, and publish your website. Infra uses Pelican and Buildbot,
and I find 90% of the process invisible and almost instantaneous. Several
projects use Hugo, with the same good usability. If your repository is on
Git, there are good continuous-integration features Infra has put in place
and will help you deploy.

Andrew




Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Aug 6, 2020 at 10:19 AM Shawn McKinney  wrote:

>
> > On Aug 4, 2020, at 11:34 AM, Andrew Wetmore  wrote:
> >
> > The first step for the PMC would be deciding on what replacement
> technology to use. There are several available; we have listed some on the
> pages I linked to in my first message, and of course there are many tools
> that can reliably generate a static website.
>
> Hello Andrew,
>
> Thank you for this kind offer of help, we can certainly use it.
>
> My question, after the migration, how do we manage the new website?  Will
> it become easier or harder?
>
> For me that’s the key.  As you know, we’re all volunteers, so time is
> limited.  Worse, we make changes maybe twice a year so it’s difficult to
> master a complicated workflow when it’s seldom performed.
>
> So, I suppose that’s where the marker lies for me.  Which of the choices
> laid out will be easiest to manage in the future?
>
> What do you recommend we do?
>
> —
> Shawn
>
> p.s. I am willing to help with this task once a decision has been made.
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: your project website

[Shawn McKinney]

> On Aug 4, 2020, at 11:34 AM, Andrew Wetmore  wrote:
> 
> The first step for the PMC would be deciding on what replacement technology 
> to use. There are several available; we have listed some on the pages I 
> linked to in my first message, and of course there are many tools that can 
> reliably generate a static website.

Hello Andrew,

Thank you for this kind offer of help, we can certainly use it.

My question, after the migration, how do we manage the new website?  Will it 
become easier or harder?  

For me that’s the key.  As you know, we’re all volunteers, so time is limited.  
Worse, we make changes maybe twice a year so it’s difficult to master a 
complicated workflow when it’s seldom performed.

So, I suppose that’s where the marker lies for me.  Which of the choices laid 
out will be easiest to manage in the future?  

What do you recommend we do?

—
Shawn

p.s. I am willing to help with this task once a decision has been made.


-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Stefan Seelmann]

Hi Roy,

that looks really great!

Was that done via a script so you can just re-generate it?

Can the generated site itself still be deployed to and served by the
existing Apache Webserver? I ask because we have some CGI scripts to
replace the download mirror and .htaccess files for URL rewrites.
Especially for Studio we use that to serve the XMLs for the Eclipse
update site [3][4].

Kind Regards,
Stefan

[3]
https://svn.apache.org/repos/asf/directory/site/trunk/content/studio/update/
[4] https://directory.apache.org/studio/update/compositeContent.xml


On 8/5/20 12:15 AM, Emmanuel Lécharny wrote:
> Hi Roy !
> 
> On 04/08/2020 17:48, Roy Lenferink wrote:
>> Hi Emmanuel,
>>
>> Some time ago I offered to help out migrating the site from the CMS to
>> a separate git repo [1].
>> Of course because that was a couple of months ago the latest changes
>> have not been incorporated.
> 
> 
> Hopefully, there are not that many changes. 2 months ago, a new Kerby
> release has been done, and 7 weeks ago, we have removed the last
> reference to Master/slave wording from the site. I *think* that your
> migration is very close to what we have (Kerby 2.0.1 might be the only
> important change).
> 
> So I guess you have already done the job, and I must say, hat down !
> 
> 
> I'm all in to switch to the solution you have implemented, based on
> Hugo. Still, I have to check what it means in term of day to day
> management, but this is something we can do at Directory.
> 
> 
>> I am still willing to help out with this (as I did for MINA as well).
>>
>> An example of the migrated output (dated February 2020) is still
>> available at [2]
>>
>> Let me know what the community wants.
> 
> 
> I'll wait for the other Directory members to express their opinion.
> 
> 
> Many thanks !
> 
> 
>>
>> Regards,
>> Roy
>>
>> [1]
>> https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
>>
>> [2] http://directory.roylenferink.nl/
>>
>> On 2020/08/04 15:37:21, Emmanuel Lecharny  wrote:
>>> Hi Andrew,
>>>
>>> yes, we are using the Apache CMS, and we have plenty of content...  Plus
>>> sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
>>> Scimple). That is 462 markdown pages, a few hundreds of css, xml,
>>> cgi, xsl,
>>> js, html and other files. Not expecting the migration to be a piece
>>> of cake.
>>>
>>> (FTR, MINA has the exact same constraint).
>>>
>>> We are not tens of committers able to help, and I'm afraid to be one
>>> of the
>>> few having some knowledge on how the CMS works and how the website is
>>> built. Stefan Seelmann, Colm and Shawn can probably give some hand too.
>>>
>>> Now, I'm currently extremely busy - up to a point my current
>>> contribution
>>> are almost nil - but it might not last (ie, the busy state).
>>>
>>> On the side note, I'm a bit disappointed that after having pushed the
>>> projects to migrate to the Apache CMS almost a decade ago, The ASF
>>> decide
>>> it will just shut it down and forces all the users - aka many people
>>> - to
>>> spent days in migrating the web site. I know infra resources are scarce,
>>> but trust me, project resources are even scracest. The CMS is really
>>> working smoothly, and I'm not sure it requires a lot of maintenance.
>>> But,
>>> well, I guess your voice is not really important...
>>>
>>> Emmanuel
>>>
>>>
>>> On Tue, Aug 4, 2020 at 3:51 PM 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 

Re: your project website

[Emmanuel Lécharny]

Hi Roy !

On 04/08/2020 17:48, Roy Lenferink wrote:

Hi Emmanuel,

Some time ago I offered to help out migrating the site from the CMS to a 
separate git repo [1].
Of course because that was a couple of months ago the latest changes have not 
been incorporated.



Hopefully, there are not that many changes. 2 months ago, a new Kerby 
release has been done, and 7 weeks ago, we have removed the last 
reference to Master/slave wording from the site. I *think* that your 
migration is very close to what we have (Kerby 2.0.1 might be the only 
important change).


So I guess you have already done the job, and I must say, hat down !


I'm all in to switch to the solution you have implemented, based on 
Hugo. Still, I have to check what it means in term of day to day 
management, but this is something we can do at Directory.




I am still willing to help out with this (as I did for MINA as well).

An example of the migrated output (dated February 2020) is still available at 
[2]

Let me know what the community wants.



I'll wait for the other Directory members to express their opinion.


Many thanks !




Regards,
Roy

[1] 
https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
[2] http://directory.roylenferink.nl/

On 2020/08/04 15:37:21, Emmanuel Lecharny  wrote:

Hi Andrew,

yes, we are using the Apache CMS, and we have plenty of content...  Plus
sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
Scimple). That is 462 markdown pages, a few hundreds of css, xml, cgi, xsl,
js, html and other files. Not expecting the migration to be a piece of cake.

(FTR, MINA has the exact same constraint).

We are not tens of committers able to help, and I'm afraid to be one of the
few having some knowledge on how the CMS works and how the website is
built. Stefan Seelmann, Colm and Shawn can probably give some hand too.

Now, I'm currently extremely busy - up to a point my current contribution
are almost nil - but it might not last (ie, the busy state).

On the side note, I'm a bit disappointed that after having pushed the
projects to migrate to the Apache CMS almost a decade ago, The ASF decide
it will just shut it down and forces all the users - aka many people - to
spent days in migrating the web site. I know infra resources are scarce,
but trust me, project resources are even scracest. The CMS is really
working smoothly, and I'm not sure it requires a lot of maintenance. But,
well, I guess your voice is not really important...

Emmanuel


On Tue, Aug 4, 2020 at 3:51 PM 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

http://cottage14.blogspot.com/






<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_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>



--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com


-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Andrew Wetmore]

Salut, Emmanuel!

Migration is always a big project, like moving from one home to another in
the physical world. We are trying to move the process along to minimize the
stress and keep it from feeling like an emergency.

I was not part of Infra when the decision to move on from the CMS was
taken, but I am confident it was not taken without a careful balancing of
the gains and losses involved. Infra will do all it can to smooth the path.

The first step for the PMC would be deciding on what replacement technology
to use. There are several available; we have listed some on the pages I
linked to in my first message, and of course there are many tools that can
reliably generate a static website.

Andrew

<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>

On Tue, Aug 4, 2020 at 12:38 PM Emmanuel Lecharny 
wrote:

> typo :
>
> s/your voice/our voice/
>
> On Tue, Aug 4, 2020 at 5:37 PM Emmanuel Lecharny 
> wrote:
>
>> Hi Andrew,
>>
>> yes, we are using the Apache CMS, and we have plenty of content...  Plus
>> sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
>> Scimple). That is 462 markdown pages, a few hundreds of css, xml, cgi, xsl,
>> js, html and other files. Not expecting the migration to be a piece of cake.
>>
>> (FTR, MINA has the exact same constraint).
>>
>> We are not tens of committers able to help, and I'm afraid to be one of
>> the few having some knowledge on how the CMS works and how the website is
>> built. Stefan Seelmann, Colm and Shawn can probably give some hand too.
>>
>> Now, I'm currently extremely busy - up to a point my current contribution
>> are almost nil - but it might not last (ie, the busy state).
>>
>> On the side note, I'm a bit disappointed that after having pushed the
>> projects to migrate to the Apache CMS almost a decade ago, The ASF decide
>> it will just shut it down and forces all the users - aka many people - to
>> spent days in migrating the web site. I know infra resources are scarce,
>> but trust me, project resources are even scracest. The CMS is really
>> working smoothly, and I'm not sure it requires a lot of maintenance. But,
>> well, I guess your voice is not really important...
>>
>> Emmanuel
>>
>>
>> On Tue, Aug 4, 2020 at 3:51 PM 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
>>>
>>> http://cottage14.blogspot.com/
>>>
>>>
>>>
>>>
>>>
>>>
>>> <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_6086363266142970678_m_-6935055923612873723_m_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>
>>
>> --
>> Regards,
>> Cordialement,
>> Emmanuel Lécharny
>> www.iktek.com
>>
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: your project website

[Roy Lenferink]

Hi Emmanuel,

Some time ago I offered to help out migrating the site from the CMS to a 
separate git repo [1].
Of course because that was a couple of months ago the latest changes have not 
been incorporated.
I am still willing to help out with this (as I did for MINA as well).

An example of the migrated output (dated February 2020) is still available at 
[2]

Let me know what the community wants.

Regards,
Roy

[1] 
https://lists.apache.org/thread.html/r4bb58d7f93dc547abc6c2829c1dad751a72a14089000550b37bbad6b%40%3Cdev.directory.apache.org%3E
[2] http://directory.roylenferink.nl/

On 2020/08/04 15:37:21, Emmanuel Lecharny  wrote: 
> Hi Andrew,
> 
> yes, we are using the Apache CMS, and we have plenty of content...  Plus
> sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
> Scimple). That is 462 markdown pages, a few hundreds of css, xml, cgi, xsl,
> js, html and other files. Not expecting the migration to be a piece of cake.
> 
> (FTR, MINA has the exact same constraint).
> 
> We are not tens of committers able to help, and I'm afraid to be one of the
> few having some knowledge on how the CMS works and how the website is
> built. Stefan Seelmann, Colm and Shawn can probably give some hand too.
> 
> Now, I'm currently extremely busy - up to a point my current contribution
> are almost nil - but it might not last (ie, the busy state).
> 
> On the side note, I'm a bit disappointed that after having pushed the
> projects to migrate to the Apache CMS almost a decade ago, The ASF decide
> it will just shut it down and forces all the users - aka many people - to
> spent days in migrating the web site. I know infra resources are scarce,
> but trust me, project resources are even scracest. The CMS is really
> working smoothly, and I'm not sure it requires a lot of maintenance. But,
> well, I guess your voice is not really important...
> 
> Emmanuel
> 
> 
> On Tue, Aug 4, 2020 at 3:51 PM 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
> >
> > http://cottage14.blogspot.com/
> >
> >
> >
> >
> >
> >
> > <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_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> 
> 
> -- 
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
> 

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Re: your project website

[Emmanuel Lecharny]

typo :

s/your voice/our voice/

On Tue, Aug 4, 2020 at 5:37 PM Emmanuel Lecharny 
wrote:

> Hi Andrew,
>
> yes, we are using the Apache CMS, and we have plenty of content...  Plus
> sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
> Scimple). That is 462 markdown pages, a few hundreds of css, xml, cgi, xsl,
> js, html and other files. Not expecting the migration to be a piece of cake.
>
> (FTR, MINA has the exact same constraint).
>
> We are not tens of committers able to help, and I'm afraid to be one of
> the few having some knowledge on how the CMS works and how the website is
> built. Stefan Seelmann, Colm and Shawn can probably give some hand too.
>
> Now, I'm currently extremely busy - up to a point my current contribution
> are almost nil - but it might not last (ie, the busy state).
>
> On the side note, I'm a bit disappointed that after having pushed the
> projects to migrate to the Apache CMS almost a decade ago, The ASF decide
> it will just shut it down and forces all the users - aka many people - to
> spent days in migrating the web site. I know infra resources are scarce,
> but trust me, project resources are even scracest. The CMS is really
> working smoothly, and I'm not sure it requires a lot of maintenance. But,
> well, I guess your voice is not really important...
>
> Emmanuel
>
>
> On Tue, Aug 4, 2020 at 3:51 PM 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
>>
>> http://cottage14.blogspot.com/
>>
>>
>>
>>
>>
>>
>> <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_-6935055923612873723_m_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: your project website

[Emmanuel Lecharny]

Hi Andrew,

yes, we are using the Apache CMS, and we have plenty of content...  Plus
sub-projects(ApacheDS, Studio, LDAP API, Fortress, Kerby, Mavibot and
Scimple). That is 462 markdown pages, a few hundreds of css, xml, cgi, xsl,
js, html and other files. Not expecting the migration to be a piece of cake.

(FTR, MINA has the exact same constraint).

We are not tens of committers able to help, and I'm afraid to be one of the
few having some knowledge on how the CMS works and how the website is
built. Stefan Seelmann, Colm and Shawn can probably give some hand too.

Now, I'm currently extremely busy - up to a point my current contribution
are almost nil - but it might not last (ie, the busy state).

On the side note, I'm a bit disappointed that after having pushed the
projects to migrate to the Apache CMS almost a decade ago, The ASF decide
it will just shut it down and forces all the users - aka many people - to
spent days in migrating the web site. I know infra resources are scarce,
but trust me, project resources are even scracest. The CMS is really
working smoothly, and I'm not sure it requires a lot of maintenance. But,
well, I guess your voice is not really important...

Emmanuel


On Tue, Aug 4, 2020 at 3:51 PM 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
>
> http://cottage14.blogspot.com/
>
>
>
>
>
>
> <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_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

your project website

[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

http://cottage14.blogspot.com/





<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>