Based on the comments I have received, I have updated the document.

The major changes are:

- removed l10n web page tools
- no auto-commit in any tools
- proposed changes to pootle server (based on request from andrea, to
use/change existing tools)
- added more text on the translation workflow, inkl. local teams

The document is available as pdf:
http://wiki.openoffice.org/wiki/File:L10procNew2.pdf
and (due to a polite hint) as a wiki page:
http://wiki.openoffice.org/wiki/Localization_AOO/new_proposal
Furthermore a projectplan is available as a wiki page:
http://wiki.openoffice.org/wiki/Localization_AOO/workPlan

this mail is posted on both ooo-L10n and ooo-dev, but please use ooo-dev
for discussions.

Andrea:
I hope you have time to see if your suggestions are well represented now,
so this document could be used as discussion basis when you meet the pootle
people.


Have a nice evening.
jan I.

On 21 October 2012 18:12, jan iversen <[email protected]> wrote:

> I have finally finished my proposal for a new workflow.
>
> please have a look at:
> http://wiki.openoffice.org/wiki/File:L10procNew.pdf
>
> I have tried to implement the comments (on the document describing the
> existing workflow) from the community, and at the same time avoid
> non-essential themes that seems to open discussions :-)
>
> The workflow I have proposed is based on my knowledge from large
> organizations, so I am sure it can work....but I do not know if the
> community as such want it.
>
> It has advantages for everybody:
> - developers dont really see a change
> - our release manager saves a lot of manual work
> - offline translators become a lot closer connected to the process,
> without being bugged down with technical details.
>
> My shoulders are pretty big, so please give me your opinions and
> suggestions for improvement (I am here to learn, NOT to educate). Please
> remember one thing the big silent majority does not count here.
>
> I post this mail here to give translators and NLC a change to speak their
> mind, it is also posted on dev, for the more technical parts.
>
> Once we have agreed to the content, I will undertake the development, but
> I do need heavy support from a committer (mostly to commit code and publish
> php/web pages).
>
> happy reading.
> JanI
>
>

Reply via email to