l10n process for help content (WAS: [PATCH] Update help fdo#31652)

l10n
#1

Hello all,

Sorry, this breaks the string freeze in 3-3, 3-4 and 3-4-1. Translators
expect that strings don't change in stable brances. I would say, it is
easier for everyone, if we change strings in master only.

Seems nuts to me that its better to keep translations of incorrect help
content in sync than to have at least some of them right, but *shrug*,
whatever's easiest to manage.

Currently there are many help contents that obsolete or inaccurate.
But wrt the string freeze, we couldn't release the fix of them
(because they all must happen in master), and user have to wait for
the next 3.x major release to have them correct, which is every
too-long six months.

So, IMO
- may we freeze only UI string, but not help? (but it's harder to
manage, though)
- or update the wikihelp more frequently? (but this doesn't update
localhelp, which maybe essential for some users)
- or just leave it as is?

What is the process for other projects?

Best Regards,

#2

Hello,

Currently there are many help contents that obsolete or inaccurate.
But wrt the string freeze, we couldn't release the fix of them
(because they all must happen in master), and user have to wait for
the next 3.x major release to have them correct, which is every
too-long six months.

So, IMO
- may we freeze only UI string, but not help? (but it's harder to
manage, though)
- or update the wikihelp more frequently? (but this doesn't update
localhelp, which maybe essential for some users)
- or just leave it as is?

What is the process for other projects?

Our processes are based on consensus. We can amend our processes, when
a new consensus is reached. I would accept string changes (only from
bugfixes, not from cosmetics, rewording etc.) before RC1, so
translators have the chance to update their translations before RC2.
But let's wait for others' opinions, too.

Best regards,
Andras

#3

A suggestion, would it be possible to relax string freeze on only a certain part of help while the other parts remain in freeze? (We're not currently translating help so I'm not directly affected.)

#4

The "master copy" of translations is with each l10n team and is not in
git or Pootle. That means we can back-port or fix anything in git or
Pootle, but translators can overwrite it with an older copy. So the
real challenge it to have something fixed at the translators' master
copy, which could be in Pootle, or a in a custom l10n system, or in
files on translator's hard disk etc.

Cheers,
Andras