On Wed, May 27, 2015 at 8:53 AM, Anthony Baker <[email protected]> wrote: > Aren’t we limited to a single repo during incubation?
Pretty much. > Within that repo we need to manage: > > - Source for geode components > - Website source > - Documentation source > > What are your thoughts for bringing in the documentation source? > Stashing it in a subproject (‘geode-docs’) on the /develop branch? > How does it get pushed out for online hosting? I guess a different way to ask this would be: what are the expectations for maintaining and releasing those docs? If the docs need to correspond to each release of Geode then maintaining them as part of the same repo is the only practical way of actually releasing them (remember ASF releases are the tarballs not what's your git repo). In that case I'd suggest geode-docs folder on /develop branch. That still doesn't answer the question of how to publish them (since they can't be served as static html pages) but we can tackle that aspect of it in parallel (I can start a thread with ASF INFRA). If that makes sense -- I'll follow up with a JIRA shortly. Thanks, Roman.
