The threads are here and, here

And, to continue in that context is a post I made (on G+) . I strongly believe that the very fact of this bug being open and yet not bringing forth a discussion is something Mozilla should think about.

If you’d like to comment I’d request that you use the G+ link above and comment there.

Incidentally, the same post from Seth provides pointers to what would be required to be done to move a locale out from beta. That’s a good list to have handy and a page that requires to be bookmarked.

Since the bn_IN team hasn’t had a cheery experience of working with the Mozilla team, Runa had requested that a few bits be cleared up. These relate to documentation especially around processes.

Quoting from the mail:

1. A pointed list of to-dos (preferably sequentially) that would allow even a seemingly new translator to complete most of the work without constant supervision/querying

2. An explanation of the automated processes (e.g. the scripts to create local workable copies) that would allow translators to troubleshoot

3. Segregating the inherent processes (like translation of UI, web-parts, getting started pages) and posting them in the aforementioned list of to-dos as part of the standard template.

4. Clear identification of the tools and methodologies (like tinderbox, dashboard, litmus etc.) used and mapping them to the monitoring processes to be followed by the translation group.

5. Identifying the process of querying about context of translatable strings. ( I generally ask on the mailing list, have not seen many queries in there)

I haven’t seen a response about this from either Simon or others from Mozilla. And, I don’t really find that strange.