It's a hack of course, but if the changes are really that occasional, the pain is negligible: all you need to do is to commit twice for every project change (once for a sub-directory containing the project repo, once for the root repo).
If a project becomes active again, simply take it out of the master repo and push it as a new repo.
It's really not that bad. But then again, things change if you have collaborators...
Re:Why I've built an alternative to Github
by lucian1900 on Sunday June 26, 2011 @06:41PM
(#2699337)
Can't you just use branches for this? Sugar code (git.sugarlabs.org) generally gets a new branch for each major release, which can be maintained separately from master.
I believe this is the kind of problem that CodePlane solves. And I agree with you that its great to see projects like this present competition and make GitHub better in the long run.