Hello, I already addressed the issue of moving the jclouds.github.com repo over in this jclouds github issue: https://github.com/jclouds/jclouds/issues/1576
My suggestion was: "Moving over jclouds.github.com will mean that we will need to run Jekyll on everything. It could just be done on Jenkins or CloudBees which would then just push the website over onto Apache's servers. We'll also need to freeze the content for the DNS time out interval so people don't see two different versions of our docs." What do you think of my suggestion? Thanks! Becca On Tue, May 7, 2013 at 5:59 AM, David Nalley <[email protected]> wrote: > On Tue, May 7, 2013 at 6:31 AM, Olivier Lamy <[email protected]> wrote: > > Hi, > > Where/how/etc.. is generated the content from http://www.jclouds.org ? > > The goal is to have it at jclouds.incubator.apache.org. > > > > Let me know and I can work on that. > > > > https://github.com/jclouds/jclouds.github.com > > (incidentally, this is a repo I did not migrate to git, despite it > being in the proposal as being part of the donation.) > > --David >
