AFAICT Commons no longer uses CMS to build, so nothing needs to be done.
Sebb.
On Wed, 6 Jan 2021 at 12:51, Andrew Wetmore wrote:
>
>
> Hi, and happy New Year.
>
> Checking in on the migration of your project website from the Apache CMS to a
> different tech. Has there been progress? Have you o
Hi, and happy New Year.
Checking in on the migration of your project website from the Apache CMS to a
different tech. Has there been progress? Have you opened a Jira ticket to track
it? Is there anything Infra can help with?
A
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Fou
The main Commons site does not need any special processing.
It just needs a script to run Maven and publish the generated site.
Can we use svnpubsub, Maven and Buildbot?
If so, is there any info on how to set up Buildbot?
Buildbot is mentioned in the Pelican+Buildbot page, but there are no
detai
The main commons site does not need any special processing.
It just needs a script to run maven and publish the generated site.
What is the Infra-recommended replacement for such sites?
On Mon, 17 Aug 2020 at 14:05, Gary Gregory wrote:
>
> Hi Andrew,
>
> There is no formal agreement from the PMC
Hi Andrew,
There is no formal agreement from the PMC but it feels to me (with my
PMC hat on) that we can move forward since the underlying tool is coming to
EOL.
My components in Commons have their own Maven generated site they upload
directly.
We just need someone to step up and the main site.
Hi:
I am glad to see the project is moving forward with migration from the CMS.
Do you have a formal PMC agreement on the move, and have you opened a Jira
ticket for INFRA so we can track what we need to do?
Thanks!
Andrew
On Tue, Aug 4, 2020 at 10:40 AM Andrew Wetmore wrote:
> Hi:
>
> I am p
I meant they support building your site from source automatically via
Pelican similar to how GitHub supports Jekyll sources to generate the
HTML from. Since we generate the HTML manually from Maven, you can use
either service as they both support static contents. It's only a
difference if we were u
On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker wrote:
> See also the asf-site and asf-staging branches for an Infra-supported
> site publishing system:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> Seems to work fairly similar to a gh-pages branch, though they offe
See also the asf-site and asf-staging branches for an Infra-supported
site publishing system:
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
Seems to work fairly similar to a gh-pages branch, though they offer
Pelican instead of Jekyll. Though since Commons sites are al
HI Andrew,
I think we use both CMS and Buildbot if that makes any sense [1], but
whatever it is, it's no longer working [2][3], so I'm happy to switch.
I see GitHub pages as an option, so why not go with that.
Commons its own site obviously but it also has a lot of components each
with their own
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 sever
11 matches
Mail list logo
