Fwd: [Python-Dev] Primer on distributed revision control?

[Ian Clatworthy]

raindog at macrohmasheen.com wrote:
> I will 2nd Mr. Yates' comments in that I was felt slightly lost when my work style or desired work style was not described. 
> 
> I think however the best approach is instead of rewriting the docs to be more like Hg, adding additional content to the docs to satisfy both types of audiences is the way to go.

Guys,

Thanks for the explicit feedback. I'm not going to pretend it's easy
balancing the needs of different audiences, so it great to have readers
articulate how the docs can be made better for them. Huge numbers of
developers still don't "get" DVCS. The Bazaar User Guide is almost too
terse for them, while it's overkill for those deeply familiar with
numerous DVCS tools/patterns. Different books are really needed down the
track. In the meantime, the User Guide is trying to find the right
middle ground.

I don't expect it to take much to improve the tone, generalise some
content and incorporate many of your other suggestions. The bit I find
*really* time consuming is high quality diagrams - ones that are simple
enough to be understandable yet complex enough to be useful. The
existing ones were originally put together by a community member and I
gladly used them over and over and over again. If there are diagrams
that we can incorporate from other license-compatible sources, please
suggest which ones and where in the manual you'd like them to go.

Likewise, if anyone has good diagrams they frequently use to explain
Bazaar to others, please consider sending them my way.

Ian C.