I'd like to move the doc sources for the Geode User Guide from the code repo (https://github.com/apache/geode) to a separate geode-docs repo.
The primary reason is to allow docs to cycle at their own rate, rather than in lock-step with the code. The present arrangement causes problems during releases, when code is frozen (including doc sources) to prepare a release candidate. This is exactly the time when critical last-minute doc changes are needed, but such changes are forbidden due to the code freeze. I have participated in the Geode project since its inception, and can confidently state that this conflict arises with nearly every Geode release. Setting up the docs in a separate repo would alleviate this regularly-recurring, counter-intuitive situation. Of note: The docs directories and toolset are almost entirely independent of directories and tools needed for code development and release, so removal of the doc sources from the Geode code repo should be painless for developers. Observations and opinions welcome... Dave Barnes
