2012/2/2 Junio C Hamano <gitster@xxxxxxxxx>: > Frederik Schwarzer <schwarzerf@xxxxxxxxx> writes: >> 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. I just sent a updated patch with the correct commit log. ;-) >> 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). > Nobody knows all languages, so a git-l10n mailing list for all translators may lead chaos. But a mailing list for l10n coordinator to notify l10n teams and for new l10n team setup maybe useful. Because this git list is some busy, may lost notifications. > 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. Yes, really needs a po/git.pot. > > (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.) It's my honor. Last three days I setup a one file repo for l10n of zh_CN, and use one wiki page (https://github.com/gotgit/git-l10n-zh-cn/wiki/TaskList) for translators to fetch/coordinate translation tasks. Now it's time to start with a new repo with full history and files, maybe git-po-zh_CN for Chinese language. > > (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. Also care about not writing commit log in native language. > > 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. notifies the l10n teams using another mailing list maybe. > (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. Use GitHub organization account is highly recommended. I wrote a open e-book (in Chinese) on this: http://www.worldhello.net/gotgithub/04-work-with-others/030-organization.html > 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. Yeah, works on the codes but not the po files still send to this list. -- Jiang Xin -- 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