Roadmap for Bazaar...

[John Barstow]

On Wed, Sep 22, 2010 at 9:52 PM, John Szakmeister <john at szakmeister.net> wrote:
>
> Again, not to be a criticism, but it's something that gets in the
> way... the architecture is a bit difficult to follow.  I realize there
> are a lot of layers for testing, and being able to swap out different
> formats, etc.  But I think the complexity makes it more difficult to
> dive in and help.  I also think some documentation is missing.  For
> instance, what should a format 2a repo look like on disk?  What does a
> good graph look like?  What does it really mean to have a ghost?  I
> think bzr-svn is pushing the line a little, and doesn't match the
> intention, but there is no good way to verify that other by reading
> source. :-(
>

Currently I'm trying to close out all the existing documentation bugs,
after which I'm going to have a go at filling in obvious gaps - I have
a draft document on my hard drive that explains how to write a plugin
that talks to foreign VCS systems, for example. If there's anything
else you can add to the list above it would be great to detail them.

> Thank you.  Personally, I'd love to (I love working on tools that make
> people's lives easier), but I'm running my own company at the moment.
> I would like to contribute some solutions back though.  And I'd like
> to contribute in other ways to the community by offering training for
> Bazaar, services to help set it up or repair broken branches, and I'd
> really like to write a book... but I struggle explaining the steps
> because how you use it everyday isn't how you would start out.
>

I think the documentation needs a bit of a spring cleaning and
re-organisation. Please don't be afraid to file documentation bugs
(just tag the bug with "doc") in places where we're unclear,
confusing, silent, or jargon-y.