Roadmap for Bazaar...

[Stephen J. Turnbull]

John Szakmeister writes:

 > /me agrees.  I also put something together for my workplace, but I'm
 > not that thrilled with it.  It still doesn't help with branch
 > management, nor making it easy to manipulate the access
 > controls. :-(

How about bzrosis (or "bzr-oasis"[1] -- more in keeping with the "friendly
life support system" posture of bzr; the git people are proud of being
a disease, it seems :-)?  Ie, start from gitosis.

The basic gitosis approach is to use an ini file to manage the ACLs
and create repositories.  This file is kept in a gitosis repo called
"gitosis-admin" (who'da guessed it?!)  The admin checks it out, edits
it, commits it, pushes it, and the gitosis daemon (or hooks in the
repo, I haven't looked at the implementation) handles the rest.
gitosis remote repos look like scp targets:

    gitosis at SERVER.TLD:/srv/gitosis/repositories/my-project

For Bazaar eventually you'd want a nice GUI instead of using Emacs or
nano to edit the conf file, of course.

Users are identified in the ini file by the names of the files
containing their SSH public keys:

    /srv/gitosis/keydir/USERNAME.pub

defines USERNAME and associates it with that key.

 > It'd be nice to see a complete, and well thought-out solution for the
 > masses.

gitosis is neither complete nor that well thought-out, but the model
is simple and extensible, and the code (it's Python!)  might provide a
framework for something more along the lines you're thinking of.

Footnotes: 
[1]  Feel free to use that name for a completely different
implementation; I have no personal interest in promoting gitosis or
derivatives, and for this purpose "bzr-oasis" is one of my better bon
mots even if I do say so myself.  I'd like to see it used!