Frederik Schwarzer <schwarzerf@xxxxxxxxx> writes:
Administrivia:
Kicked back to the mailing list so that Jiang and Ævar have a
chance to join the discussion.
>> [Footnote]
>>
>> *1* Ah, another thing, shouldn't the title be labelled as l10n
>> instead of i18n?
>
> l10n if translations are sent, i18n if patches to improve translation
> support in the sources are sent.
Yes, that was what I was getting at.
> But maybe a separate mailing list
> might be a good idea. So people interested could be subscribed there
> without being overwhelmed by the amount of mails in here.
I personally do not think git-l10n warrants a full mailing list dedicated
to it (but see (4) below).
Earlier I said:
> I haven't decided what to do with this, though. If we are going to get
> tons of l10n patches[*1*], it may make sense to have a separate clone of
> git.git, with possibly a maintainer other than myself, forked at v1.7.9
> and updates _only_ files in po/ hierarchy.
I actually was hoping to see somebody to step up and volunteer to be the
l10n coordinator (see git-gui/po/README, which calls this person "the
internationalization coordinator", for the responsibility of this role).
I would envision that the workflow would go like this:
(1) The l10n coordinator makes a fork of "git.git", and start his history
at v1.7.9. Let's call this the "git-po" repository.
(2) The l10n coordinator prepares po/git.pot and makes a commit in
"git-po" repository. It is l10n coordinator's responsibility to
maintain this file.
(3) There will be one l10n team for each supported locale. Jiang might
volunteer to be the team leader for zh_CN. Each team leader forks
the git-po repository. Let's call this the "git-po-zh_CN" repository
(there will hopefully be more, like "git-po-is", "git-po-pt_BR",
etc.)
(4) Members of each locale team work to advance their "git-po-$locale"
history. They make changes ONLY to po/$locale.po file and NOTHING
ELSE. Specifically, locale teams are NOT expected to touch po/git.pot
or any source files in their "git-po-$locale" repository.
How the members in a locale team coordinate their work is up to the
team. A large team might want to have their own mailing list, and I
wouldn't stop it.
(5) From time to time, each locale team asks the l10n coordinator to pull
from their history, and the l10n coordinator will pull updated
translations. Optionally, the locale team may want to clean up their
history before asking the l10n coordinator to pull their work.
(6) From time to time, the l10n coordinator will pull from "git.git" when
meaningful number of changes are made to the translatable strings. I
hope this would happen much less often than once per week, preferably
much less frequently. The l10n coordinator updates po/git.pot and
makes a commit, and notifies the l10n teams.
(7) The l10n teams will pull from "git-po" to get the updated po/git.pot
file and will work on updating their "git-po-$locale" repository (go
back to step (4) above).
(8) From time to time, the l10n coordinator will ask me to pull from
"git-po" repository.
One possible mechanism to use might be to host all of these at GitHub, to
leverage their service for all the "forking" and "requesting pull" above,
as well as intra-team communication.
And i18n patches that modify the _() markings in the source code, will
only go through "git.git" tree in the normal channel, IOW, this mailing
list.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html