Call For Volunteer: scenarios editor (was: Short, task-based bzr doclets for real-world use cases.)

[Karl Fogel]

Would someone like to be the overall editor for the "scenarios"
documentation we're writing to provide newcomers with some more
task-based structure?

   http://bazaar-vcs.org/Scenarios/

See also this thread:

   https://lists.ubuntu.com/archives/bazaar/2009q1/thread.html#51605

The job entails reading new scenarios as people write them, and noticing
inconsistencies.  You should be a reasonably fluent bzr user, but you do
*not* need to be a developer or even a guru.  You just need to be able
to recognize when someone is giving bad advice, or when two scenarios
give contradictory advice.  (When that happens, you may have to post to
this list to find out what the right advice should be.)

Part of the purpose of these scenarios is also to discover if there are
places where bzr puts too much complexity in front of the user, and to
take those issues to the list so developers are aware of it.  The editor
should keep an eye out for that.

When we have an editor, then I'll make a separate post soliciting
volunteers to write (say) the five most important scenarios.  I think if
we divide up this work, it won't be that hard, and it'll make a big
difference for new users eventually.

So: anyone feel like trying a hand at being overall editor?

-Karl