[RFC] doc directory reorganisation & I18N

[Ian Clatworthy]

Alexander Belchenko wrote:

> I just wondering: how you guys will be review and approve documentation
> translations on languages that you don't understand? Per example,
> I can translate to russian, but how my translations will be merged?
> Of course, there is several people in ML from russian-speaking countries,
> but most of them can't vote in BB.

It's a very good question and I don't have a very good answer. My guess
is that we'll ask mailing list members to vote and those with BB access
can act as proxies in terms of recording such votes. Growing the number
of contributors with voting rights is also a worthy goal.

> Another side note: the more translations we have the bigger doc/ directory
> will grow. May be it worth to extract it in separate sub-project
> (aka nested tree?).
> 
> /me just don't completely understand all formal details.
> 

I expect so once nested trees are production strength. My main point was
that I wanted a structure that could accommodate multiple languages.
English may be the source language but I want Bazaar to be truly
friendly to as many people across the world as possible and, to me, that
means treating all languages equally when we ought to.

The benefits we get by having our docs in the source tree - revision
control, review, closer sync with code changes - ought to be shared
across multiple languages in theory. In practice, I don't expect all the
doc in all languages to be changed simultaneously but I also don't
expect the doc to massively change from one release to another in the
medium term.

Ian C.