migration of ubuntu-docs to bzr?

[Jonathan Jesse]

I think this converstation comes up every new release, but what is the team's 
thoughts about moving to bzr and away from subversion.

I have recently started to work on both the Keep documentation and (yes again) 
the documentation for Adept, with a focus on the differences between 
Kubuntu's version of Adept and KDE's version.  So in my mind there will be 
multiple versions of the documentation.

Anyways, I've spent a lot of time working on Keep documenation and it is 
currently maintained in bzr and then launchpad.  Please see 
http://bazaar.launchpad.net/~jjesse/keep/keep-doc1 for the actual bzr branch.  
Also check out http://codebrowse.launchpad.net/~jjesse/keep/keep-doc1/changes 
to see a different view of the documentation that allows you to browse actual 
changes that I've been making.

Some benifits I see to using bzr and launchpad:
1.  Commit access is controlled by only allowing members of the team to upload 
to launchpad by setting the team as the owner of the branch.
2.  Notifications of changes to documentation can still happen by having 
people subscribed or subscribing the team and there can be different levels 
of subscription.
3.  One can browse the code and the changes in an easy to use way.  See 
earlier link to Keep documentation.  I think this was an earlier problem with 
migrating to bzr from subversion.
4.  No longer relying on RT for changes to passwords, etc...  I know the times 
that I've lost my password it has taken quite awhile to get a new password 
created with much hassle of the admins who deal with RT.  Now the person just 
needs to have an .ssh key uploaded to launchpad and be part of the team that 
can commit to the bzr branch.


I'm sure there are other reasons I could think of, but it has been quite easy 
to setup and maintain my own branch of documentation as I've been working on 
projects.  I would be quite interested as to what the rest of you thought 
about this.

Thanks,

Jonathan