On May 7, 2013, at 2:29 PM, David Nalley <[email protected]> wrote: > On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <[email protected]> wrote: >> Are there any specific requirements with regard to an audit trail for >> changes to the site? >> >> Do we need to be able to show commit logs etc. too, or is it OK to have >> those in GitHub and regard the Apache site as the hosting location for the >> Jekyll-generated HTML, which would be (over-)written on every merge..? >> >> +1 on the idea of running this via Jekyll. Could/should we be using Apache >> CI infrastructure to do this, or is CloudBees OK (for now)? >> >> ap > > Website requires svn (long story, but basically, svnpubsub is > required). Jekyll should be fine as a build tool (Olamy or Suresh, > feel free to correct me) - so you could theoretically do a svn->git > replication, but no real way of escaping svn for the website.
Thats right. To my knowledge we cannot get away from svn for Apache CMS. I have dealt with CMS for few projects and i will be happy to help with transition, but I am trying to understand the github site of website before I comment on migration. But so far others have good thoughts and I am learning whats out there now in git. Suresh > > --David
