Concrete proposal to moving to bzr

[Matthew East]

Hi,

On 21/10/2007, Dean Sas <dean at deansas.org> wrote:
> Jim Campbell wrote:
> > Were we going to go ahead with the move to bzr, and if so, how would
> > that impact updates to trunk at this point?  Should we hold off on
> > updating trunk until the move to bzr is made, or can additional changes
> > be made using subversion until we move over?  Thanks.
>
> I think the plan was to move ahead with bzr sometime after gutsy was
> released...

Yes, it's definitely time to start looking at this seriously now.

I've begun by rearranging the team structure a bit on Launchpad, as
most of you will have noticed by the vast amount of email that has
flooded in.

~ubuntu-doc is now an umbrella team for the various teams that are
involved in documentation. I've created a new team, ~ubuntu-core-doc,
for controlling who has commit access to the various bzr branches that
we might set up. I've tried to add all those who I recall as being
active contributors to the project, but if you are not in the group
and (a) have commit access to the svn repository, and (b) wish to
continue contributing, please let me know and I'll add you.

I've also added Dean, who requested access a while ago, and who I
think has contributed good quality patches over a long period for the
team.

https://launchpad.net/~ubuntu-doc
https://launchpad.net/~ubuntu-core-doc

I'd also quite like to create a team for people who want to get
involved but haven't yet been granted access - we could call it
"~ubuntu-doc-mentees", and relate it to the mentoring project.

Before we go any further, is everyone happy with the move as proposed
in my previous email of 12 September? If so, the remaining tasks are
to import the relevant branches, and to rewrite the documentation on
our wiki pages so everything is clear for new contributors.

> You should keep committing to svn trunk, bzr can import svn history.

Yes, that's fine.

-- 
Matthew East
http://www.mdke.org
gnupg pub 1024D/0E6B06FF