directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel L├ęcharny <>
Subject Re: [DISCUSS] Move Directory site from CMS/SVN to Hugo/Git
Date Mon, 24 Feb 2020 11:23:21 GMT
Hi Roy,

On 21/02/2020 19:31, Roy Lenferink wrote:
> Hi Directory community,
> I noticed Directory is still serving its site from SVN with help of the Apache CMS. At
the Apache Celix
> project we decided to move away from the CMS and move towards git for serving our website
> This because the CMS was introduced in 2010 and is currently not accepting any new projects.
> the move to Hugo we're sure that we still can update the site when the ASF CMS will be
> decommissioned.
> The master branch contains the actual website sources whereas the generated website is
> from the asf-site branch. Hugo is being used as static website generator. Content is
written in
> Markdown.
> About a week ago I started migrating the MINA site from SVN to Git [6] and today I converted
> directory site as well. An example of Hugo its output is (for demo purposes only) available
on [2].
> These are the existing markdown files with a slightly changed header.
> Moving to git can enlarge the visibility of how projects are functioning. Next to that,
new contributors
> can simply create a pull request against the website repository if they find anything
they want to
> improve (an 'Edit on GitHub' / 'Edit this page' button can be added as well, like this
> If the community is interested in this move what I propose:
> - Someone from the PMC to request a new git repository for the website (e.g. directory-site)
via [4]
> - Me creating the pull request from the repository I am temporarily using for the website
contents [5]
> to the official directory-site repository
> - Create a Jenkins job to automatically build the site after changes happen on the master
> - When the pull request is reviewed and merged ask INFRA to move over from the current
> to the gitpubsub approach and remove Directory from the Apache CMS.
> Next to that Directory is also providing javadocs on its site. My proposal for this is
to serve them from
> a separate branch (e.g. mavibot-docs / apacheds-docs etc.). This way people who only
want to clone
> the site can clone the the master branch using --single-branch and will not be bothered
with cloning
> all the javadocs.
> All the URLs are still the same so the SEO score is not influenced in any way.
> I'd like to hear some opinions/thoughts on this :)

I'm all in for such a move, but I would wait for MINA to be done, as I 
have very little time at the moment to conduct such a migration (I'm on 
MINA and Directory projects, so I'll benefit from what I have learned 
from MINA migration).

Thanks !

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message