poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yegor Kozlov <yegor.koz...@dinom.ru>
Subject Re: Fixing our website to still work in 2013
Date Mon, 17 Dec 2012 07:13:39 GMT
I'm for svnpubsub, as it seems the shortest way.

As I understand, we will need to keep the generated html somewhere in
svn and then ask Infra to enable svnpubsub for our site .

Migration of the Forrest part seems easy:
1. create a new directory "site" under
https://svn.apache.org/repos/asf/poi/trunk
 2. create two sub-directories:
  site/docs      <-- Forrest .xml files, copy them from trunk/src/documentation
  /site/publish  <-- generated html
3. create a Ant script (actually a sub-set of current build.xml) that
will update  /site/publish from site/docs

To update the web site you will need to   checkout the "site" project,
edit xml, build html and commit. Then svnpubsub  will do the rest and
update the live web site.


Yegor

On Mon, Dec 17, 2012 at 4:25 AM, Nick Burch <nick@apache.org> wrote:
> Hi All
>
> For those who didn't see the emails from infra@, the current way we maintain
> our website (rsync of built files to people.a.o) will stop working on the
> 31st Dec, and we'll then no longer be able to update our site. (It'll still
> be there, just we won't be able to change it....)
>
> I raised a bug about this back in November 2010!
> https://issues.apache.org/bugzilla/show_bug.cgi?id=50235
>
> We talked about it at the time, but nothing really came of it. We need to
> either take the quick route, commit the built site to svn and use svnpubsub
> to publish, or change to using the cms for the site. The later will take
> longer, but will make it easier to edit + make it easier for people to
> contribute changes (the cms has anonymous suggested edits for example)
>
> What do we want to do? Either option will need a bit of fiddling for the
> javadocs (but infra@ has lots of suggestions from other projects on that). I
> could probably find some time later this week to do a bit of cms migration,
> but not all of it, we'd need more volunteers to help if we wanted that!
> Thoughts?
>
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Mime
View raw message