> > -re-architect the repo > -create the proper cnames to be in accordance with trademark guidelines > -we can decide what content to keep or not and convert what we keep. > -decide how we organize the content > -start accepting pull requests (noting that pages can be edited directly from > github) > -make a first release of this new doc site at the same time than 4.3 release. > > > Thoughts, flames ? > >
So I was the one that picked Publican for CloudStack in the pre-ACS days. I like publican, it generally makes sense to me, seems to work well, and despite the fact that it's DocBook XML with specialized tools for generating finished documentation, it does the job very well. That said, I see a few problems with publican; namely: * DocBook XML is something folks have to learn before being able to contribute (e.g. the barrier to participate is higher) * The build/publish process is difficult at best. Currently I think that only Joe Brockmeier and I know how to do so. (we are SPOFs) I actually looked (at Joe's suggestion) for something else many months ago; and there didn't seem anything that was close to competent for generation of PDFs and EPUBs. I reluctantly tried RTD when Sebastien showed it to me - and was literally blown away - formatting/syntax is simpler, publishing is dead easy; and not dependent on an individual. I am +1 for this change; I think it makes life simpler for anyone who wants to work on docs, and changes next to nothing for the folks who only consume them. --David
