Initial thoughts on Bzr docs

[Eugene Wee]

Hi everyone,

> Missing docs
> -------------
> 
> My main priority is to ensure that there are no major gaps in Bazaar's
> docs. You'll have seen my meeting announcement already, where I'd like
> to discuss what's missing in the docs.
> 
> However, I don't see any reason not to kick off the discussion here
> before the meetings! You guys know Bazaar much better than I do :)

I would highlight the Workflows document as something that is not 
missing, yet missing more detailed information. As a student who has 
never used Bazaar in a team, I am puzzled as to which workflow might be 
the best choice for me.

If each workflow listed comes with examples, it would be easier to 
understand just what they involve. For example, I believe java-gnome 
uses the "Decentralized with human gatekeeper" workflow, and their 
hacking doc describes how an observer might contribute:
http://java-gnome.sourceforge.net/4.0/HACKING.html

It is not clear for a newbie to Bazaar what "when a developer wants 
their work merged, they ask the gatekeeper to merge it" means, but if 
they have an example like that of java-gnome (reader: oh, the developer 
uses bzr send to ask the gatekeeper to merge it), it becomes easier to 
understand.

Thanks,
Eugene Wee

P.S.: since this is on the wiki, I might make the changes myself, but I 
am not sure how all the workflows really are supposed to work in practice.