scenarios + workflows + docs

[Karl Fogel]

Ian Clatworthy <ian.clatworthy at internode.on.net> writes:
> Right. I've been thinking hard recently on how best to explain and
> simplify the whole "get me started quickly" issue. There's actually
> 2 related "dimensions" involved:
>
> 1. The workflow you want
> 2. How your workspace is organised.
>
> I'm beginning to think that the current approach I and others have typically
> taken - i.e. explaining workspace organisation as a side-effect of
> explaining the workflows - is *not* the best way. Instead, let's consider
> explaining the workspace organisation options first and then the workflows
> might flow a little easier?

That's an experiment worth trying.  People have a very concrete sense of
what a workspace is and how they'd like theirs organized; if you start
from that familiar terrain, maybe the things that follow from it will
feel less complicated.

>> Sometimes I wish those two could be unified, such that bzr (or a plugin)
>> would offer a single command that means "Set me up to follow PROJ and
>> maybe contribute patches".  As in:
>> 
>>    bzr init-repo PROJ
>>    cd PROJ
>>    bzr branch URL-TO-PROJ-MAINLINE PROJ-trunk
>>    [edit PROJ-trunk/.bzr/branch/config appropriately]
>>    bzr bind URL-TO-PROJ-MAINLINE PROJ-trunk
>>    bzr branch PROJ-trunk PROJ-dev
>> 
>> However, that's a separate issue.  For now, let's just document it...
>
> I'll throw up a web page presenting my latest thoughts on this.
> Stay tuned.

Staying tuned!...