[dev] Git reorganization

[Michael M Slusarz]

Going to try to sum up what I think is forming as a consensus.

* Moving applications and framework packages to separate repos seems  
to be the most supported idea.
   - GitHub allows unlimited public repos, so we are good there
   - Can maintain all history.  See  
https://help.github.com/articles/splitting-a-subpath-out-into-a-new-repo
   - Might be a bit more unwieldy to work with (current monolithic  
repo allows commits across applications; but it might be a good thing  
to require different commits for each application for a more granular  
approach at adding features/fixing bugs.)

* Talk of using git subtree(?)
   - http://log.pardus.de/2012/08/modular-git-with-git-subtree.html
   - However, this approach seems to completely neglect the current  
issue of "what should the master branch be?" or whether this question  
can even be properly solved when dealing with so many disparate pieces

* Worries about scripting to setup repos
   - Argument was made that it only takes 2 lines currently to create  
an installation.
   - However recent discussion on mailing list pointed out it is  
extremely difficult for non-developers to set up an installation using  
git.  So the current scripts aren't perfect by any means.
   - Additionally, whatever way we switch to will also need to be  
scripted so we would be in no different place than we are currently.
   - No solution is going to work out-of-the-box.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]