On Wed, May 27, 2015 at 9:04 PM, Roman Shaposhnik <[email protected]> wrote: > 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.
Meh. If it's the right thing to do to have multiple git repositories, then we should just do that. With Subversion, it's fairly trivial to create subdirs just for docs, sites, etc. that are parallel to the source tree. Git actively encourages having very small repositories. So, let's not have the SCM dictate making a horrible mess out of the source repository. (IOW, this would be a non-issue with Subversion with a "single" repository, but is extremely painful with git.) >> 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. I haven't seen a discussion yet what the versioning and lifecycle of Geode should be. What's the current thinking there? If there will be multiple concurrently supported versions, then there should be corresponding published release documentations. Some examples: httpd: http://httpd.apache.org/docs/2.4/ http://httpd.apache.org/docs/2.2/ http://httpd.apache.org/docs/trunk/ Ceph: http://ceph.com/docs/ (defaults to master, notice the selector at bottom right) If we go that route, then I don't think that it'll make sense to have all of the historical documentation versions exploded in a single folder. It should be some type of branching scheme...so, probably sitting in the source tree for each branch/tag. My $.02. -- justin
