This is a list of how some common scenarios would go in bzr. The idea is that when a new user shows up asking "How would I do X in bzr?", she should see a ready answer, thus reassuring her that, yes, bzr can do what she needs to do. Once this series is fleshed out, we will position these scenarios more prominently (perhaps as part of a general overhaul of the site to orient it more towards bzr newcomers).
Just to emphasize that point: merely having more documents available does not improve the newbie experience! In fact, it may make it worse :-). The key will be to present this information in the right way, once it's ready.
- As a casual contributor, fix a single bug in a project already in bzr.
- Work on a series of bugfixes or features, for a project already in bzr.
- Work on a series of bugfixes or features, for a project already in bzr on Launchpad.
- Start a new project in bzr, with intent to collaborate
- Publish my changes to project Foo, independently of Foo's maintainers
- Cooperatively maintain a web site in bzr, with automatic updates
- Review and accept changes from others, into a project that I manage using bzr
- Share a private bzr branch (or repository) with a team
- Convert a collaborative project from Subversion to bzr
- Convert a collaborative project from Mercurial to bzr
- Convert a collaborative project from Git to bzr
- Maintain local changes against an upstream source over time, when the source is NOT in bzr
- Maintain local changes against an upstream source over time, when the source IS in bzr
- Share common versioned code (e.g. standard utilities) between multiple projects
- etc, etc -- please add suggestions for new scenarios