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 <[email protected]> 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 <[email protected]> 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&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#m_6941078767645363208_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
