Jiang Xin <worldhello.net@xxxxxxxxx> writes: > 2012/2/29 Junio C Hamano <gitster@xxxxxxxxx>: > >> @@ -1,33 +1,78 @@ >> +The localization (l10n) coordinator, Jiang Xin <worldhello.net@xxxxxxxxx>, >> +coordinates our localization effort in his repository: >> + >> + https://github.com/gotgit/git-po/ > > I create a new dedicated team, named git-l10n, and transfer this repo to the > new place: https://github.com/git-l10n/git-po/ for the following reasons: > > - git-po is a long-term repo, so has a dedicated, stabilized URL is better. > The repo URL may not change if l10n coordinator change. > > - git-l10n is a github organization account, and has a dedicated owners > group, who can assign new l10n coordinator. > > - Owners group of git-l10n organization will not receive pull requests to > git-po. I add gister, avar to the owners team. > > - Members of the git-l10n-coordinators team of git-l10n organization > will receive pull requests. > > - Some Chinese guys used to send pull request to gotgit/git-po, so you > can find some closed pull requests written in Chinese. It won't happen > after the repo transfer to git-l10n/git-po. It is unclear the distinction between gotgit and git-l10n but I am guessing that (1) you feel "gotgit" is more for _your_ personal use, (2) you happen to be the volunteer coordinator right now, but (3) the team effort deserves more permanent home, detached from your identity. And if that is the case, I agree 100% with the reasoning. >> +As a contributor for a language XX, you would fork this repository, > > As a contributor for a language XX, you should first check TEAMS file in > this directory to see whether a dedicated repository for your language XX > exists. Fork the dedicated repository and start to work if it exists. > > If you are the first contributor for the language XX, please fork this > repository, That's better. >> +prepare and/or update the translated message file po/XX.po (described >> +later), and ask the l10n coordinator to pull your work. > > Shall we remind the contributors for l10n to write commit log in English, > but not language XX? It's a common mistake for translators. I would prefer to see the subject line (the first line summary) in English to say something like "Update zh_CN translation for 1.7.12". That much of English shouldn't be too much burden for language teams. On the other hand, the body of the log that describes the change _may_ be hurt if you forbid the use of language XX. The translators may want to write something like: The earlier translation used word '[%#$@$#]' for original phrase 'to distim' in English, but word '[**&*#$]' is a more appropriate language XX translation in the context the message for such and such reasons. and I suspect that "for such and such reasons" part is far easier to explain and understand if written in language XX for native speakers of language XX. Such a description often has to discuss connotations and subtle nuances of the particular word that is hard to explain. >> diff --git a/po/TEAMS b/po/TEAMS >> new file mode 100644 >> index 0000000..8ee6199 >> --- /dev/null >> +++ b/po/TEAMS >> @@ -0,0 +1,10 @@ >> +Core Git translation language teams >> +(please keep the list sorted alphabetically on language field) >> + >> +Language: is (Icelandic) >> +Leader: Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> >> + > > I think we should add the URL of the dedicated repository for language XX here. > Example: > > Language: zh_CN (Simplified Chinese) > Leader: Jiang Xin <worldhello.net@xxxxxxxxx> > Homepage: https://github.com/jiangxin/git-po-zh_CN/ Good thinking; I don't know if Homepage or Repository is more appropriate, but some URL would definitely help. > >> +Members: Yichao Yu <yyc1992@xxxxxxxxx> >> + Riku <lu.riku@xxxxxxxxx> > > Contributors and members can add to the header of the XX.po file. > Add here may cause the TEAMS file grows rapidly. Sorry, I do not understand what you are worried about here. Could you clarify a bit? In any case, the patch you are replying to is "I'd like to see *something* *like* *this*...", so feel free to take the ownership and update it. I'll try to help refining it if you send an updated draft to back the list for review. Thanks. -- 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