bzr-doc team mailing list archive

[Ian Clatworthy <ian.clatworthy@xxxxxxxxxxxxx>]

Hi everyone,

It was only 3 weeks ago that we started the bzr-doc team and already the
impact has been huge. I had a look over the bugs tagged with 'doc' today
and the number is down from 55 to 35. Simply awesome! It's also really
exciting to see the Administrator's Guide taking shape.

For those who have been sending in patches, have you found the
experience a positive and rewarding one? Are there things we could do to
improve it?

For those yet to send in patches, do you need more guidance on finding
things to work on or more help with the process? (There's certainly no
obligation to send in patches btw: I'm just keen to ensure that everyone
who wants to contribute is getting the help they need to do so.)

Looking forward, here are some of the things I'd like to see:

1. The glossary moved from the Wiki into our standard docs.
   Several of the outstanding bugs basically ask for a certain terms
   to be better explained. If we can get the glossary moved across,
   we'll have a better place holding those definitions. We'll also be
   able to add cross-references into the glossary from the rest of
   the docs.

2. More specialised tutorials. I'd like to see one oriented towards
   website maintainers say. I think Emma had some great ideas along
   these lines IIRC. Emma?

3. Break the User Reference into topics instead of one big doc.
   Many places in the User Guide (say) link into the User Reference
   so it would be good to get a better online structure for this
   document agreed to and bedded down soon (so we can fix any broken
   links well before 2.1 ships).

Does those things sound OK to everyone? If so, any volunteers to take
these tasks on?

Ian C.