On Sun, Aug 20, 2017 at 11:35 PM, Holger Wansing <li...@wansing-online.de> wrote:
> Hi Lior and list, > > Cyril Brulebois <k...@debian.org> wrote: > > > For the installer itself, I would not start before the release of > Stretch, > > > it's too late for that now. > > > My first target would be the installer for buster. > > > > I'm adding Lior in copy of this small subthread since he just approached > me > > during DebConf, as he would like to help with translation coordination. > :) > > So welcome in our new sub-team :-) > > My idea for the installer was basically, to send a call for translation > updates to all languages, which are outdated, means searching for new > translators for those languages on the relevant l10n lists. > a call for translators would be great, go for it. We also should offer it directly to people when we encounter someone who might be able to help. That's I got evolved in Debian... by being asked to translate d-i to Hebrew. However, at debconf a new intend was called out to change the whole > translation infrastructure for the installer (in the long term of course, > no quick actions to be expected IMO). > I wasn't aware of these suggestions during debconf, but we at least how have some things more easily accessible till such infrastructure would be available. I recently helped bootstrapping the translation to Albanian (sq) and want the next language to find the needed resources more easily. This is why I'm somewhat unsure how to proceed... > Should I try for recruiting new translators, even if the workflow changes > heavily some time later? > Recruiting new translators means explanation of workflow to some degree, > what > would be to no avail, if infrastructure changes. > I don't see any logic in waiting for the new infra for starting getting people involved. When we move, most will move with us. Also more people to get feedback from about the new infra. Change isn't something to be afraid of, we just need to manage it (: Kaplan
