I agree on splitting the docs out into their own repo that pull requests can be sent to as bugs in the docs are found or different installations are tested and documented.
With the current state of the docs being one of the greatest barriers to entry for new CloudStackers, or even when running into problems while trying to upgrade, I think it's a problem that can't wait to be solved months from now in a 4.3 release. I've spent weeks breaking and fixing various combinations of CS 4.0.2 -> 4.1.1, CentOS and Ubuntu, XenServer and KVM, NFS and local storage, and Basic and Advanced networking just to learn how to install and setup a working CS environment because Everyone knows there's a doc shortage, lets fix it. The fact that the mailing list(s) gets the same questions about SSVM and CPVM not spinning up a few times per week and the complexity of setting up the different network types should be enough to want to create very detailed documentation for different setups with a prominent troubleshooting section. Using something like GitHub issues would allow people to create issues that can be closed out with a PR/commit that updates the docs to address problems as opposed to saturating the mailing list with the same questions. And it would give others trying to help a place to point people for answers. Travis On Sep 4, 2013, at 9:22 AM, Chip Childers <chip.child...@sungard.com> wrote: > On Wed, Sep 04, 2013 at 12:26:36AM +0000, Animesh Chaturvedi wrote: >> [Animesh>] Any change should be done post 4.2 >> > > Actually, now's the time IMO. Master is the 4.3 target at this point, so > shouldn't we make larger changes now? (moving docs to their own repo and > re-designing any tooling choices seems like a large change)
