Did you use another VCS tool before Bazaar?

[James Westby]

On (20/07/07 17:27), Ian Clatworthy wrote:
> OK, that's a leading question and I expect 99% of us to answer "yes". :-)
> 
> #2 on my Bazaar doco review hit list is "Switcher Guides". After a Quick
> Reference sheet, these documents are the most likely to be read. IMO,
> they need to be short (2-4 pages) and to the point. No Fluff, Just
> Stuff: Why Bazaar, repository migration, etc. can and should be covered
> elsewhere.
> 
> We have 3 Wiki pages right now in this spirit:
> 
> * http://bazaar-vcs.org/BzrForCVSUsers
> * http://bazaar-vcs.org/BzrForSVNUsers
> * http://bazaar-vcs.org/BzrForGITUsers
> 
> In several months time, I'd like to see a dozen+ of these documents
> covering all the popular tools. After all, 99% of future Bazaar users
> already know a VC tool now. The easiest way we can get them productive
> on Bazaar is a short document that *gets them going in the context of
> what they already know*. From there, they can explore help, read bigger
> docs, etc.
> 
> So, if you know another VCS tool whether that be CVS, SVN, Perforce,
> Clearcase, StarTeam, Arch, Baz, Darcs, Git, Mercurial, Monotone, SVK,
> whatever, and you can spare a few hours to help, please consider adding
> a Wiki page with the "Just Stuff" content I'm after. I'm happy to fix
> grammar if required, format it nicely, get it reviewed and merged into
> bzr.dev in coming months. But your expertise and knowledge of other
> tools is needed to get some raw content together first, particularly in
> terms of the key things users of those tools will be use to.

I think this is a good idea, and I will help out where I can. I am
probably going to be best at the git guide.

I believe that one problem we have is that the current Wiki pages have
unclear license situations. The pages say they are (C) Canonical, when
some are not.

I was looking to pull some changes from the wiki in to the docs, but
this makes it difficult. I assume the regular contributors to the code
would be happy for this to happen, but there are other people that
contributed to the docs on the wiki.

We can rewrite the wiki stuff to avoid this, but it would be good for
people who make new docs on the wiki to add a license statement, or
better to pick a license for the wiki and get people to agree to it when
they submit the changes. I don't know how this would work with existing
content though.

Thanks,

James

-- 
  James Westby   --    GPG Key ID: B577FE13    --     http://jameswestby.net/
  seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256