[josm-dev] JOSM-Tested

[Claudius]

Am 13.06.2010 16:54, Dirk Stöcker:
> Here is the major problem:
> - We do not have really anyone who is responsible or even the contact
>     addresses of translators
> - New translators are coming, others going.
> - Each translator seems to be active a short time only (except me, which
>     is tied due to other reasons to the project).
> - Most of them aren't on josm-dev.

Talking from a translator's (contributing to other projects as well 
besides JOSM) perspective: I don't see the need for a string freeze and 
am totally okay with way l10n is currently handled in a "live" manner.

There are three triggers for me to contribute to JOSM translation:
- I'm running nightly builds and if I spot an untranslated string I head 
over to launchpad
- I'm reading this dev ML; whenever Dirk announces a new stable I check 
launchpad
- every now and then I just check into JOSM's launchpad section and 
translate strings where I know the context just because I'm in the mood.

We won't reach 100% string coverage this way, but even 60% is okay if 
the main interface gets done this way. We don't need 100% with every 
exception message translated.

 From my perspective the current discussion is a non-issue.

Claudius