{"thread":{"id":"46400","subject":"[L10N] af.po: New translation workflow","startedAt":"2017-07-16T17:37:24Z","lastAt":"2017-07-17T15:54:05Z","messageCount":2,"participants":["Jacques Viviers","Jiang Xin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"324630","messageId":"CAA=CdW25uWyZA_7RVnr35dNuK06=8_+fk_tBMt5OSf_xY4LWFA@mail.gmail.com","threadId":"46400","inReplyTo":null,"subject":"[L10N] af.po: New translation workflow","fromName":"Jacques Viviers","fromEmail":"jacques.viviers@gmail.com","sentAt":"2017-07-16T17:37:19Z","receivedAt":"2017-07-16T17:37:24Z","isPatch":false,"sender":{"key":"jacques.viviers@gmail.com","avatar":null},"body":"Hi all,\n\nI have started a new translation af.po at:\n(https://github.com/jbviviers/git-po)\n\nThe translation is far from complete. Should I wait until it is all\ndone before I submit the patch, or is it better to submit as I go\nalong?\n\nAlthough it is unlikely that someone else is busy with the same thing,\nit would still be better to somehow notify other potential translators\nthat this work is in progress.\n\nThere is a few of my colleagues that indicated they would help with\nthis translation. How does that collaboration work? Do I merge\neveryone's contributions as I see fit and then send in the set of\npatches?\n\nSome advice would be much appreciated.\n\nKind regards,\nJacques\n"},{"id":"324646","messageId":"CANYiYbFF380s2T_TUJ8Wa3pA_zkZc+L7=E-QhyFr4hycqMdmCA@mail.gmail.com","threadId":"46400","inReplyTo":"CAA=CdW25uWyZA_7RVnr35dNuK06=8_+fk_tBMt5OSf_xY4LWFA@mail.gmail.com","subject":"Re: [L10N] af.po: New translation workflow","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2017-07-17T15:53:57Z","receivedAt":"2017-07-17T15:54:05Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2017-07-17 1:37 GMT+08:00 Jacques Viviers <jacques.viviers@gmail.com>:\n> Hi all,\n>\n> I have started a new translation af.po at:\n> (https://github.com/jbviviers/git-po)\n>\n> The translation is far from complete. Should I wait until it is all\n> done before I submit the patch, or is it better to submit as I go\n> along?\n>\n\nAfter you complete most of the translations, send a PR to the l10n\ncoordinator's repo (git-l10n/git-po on GitHub).\n\n> Although it is unlikely that someone else is busy with the same thing,\n> it would still be better to somehow notify other potential translators\n> that this work is in progress.\n>\n\nA work-in-progress (WIP) branch will be created to let other guys know\nthat l10n on Afrikaans is working in progress.\n\n> There is a few of my colleagues that indicated they would help with\n> this translation. How does that collaboration work? Do I merge\n> everyone's contributions as I see fit and then send in the set of\n> patches?\n>\n\nYou can review contributions using pull requests on your GitHub repo\n(jbviviers/git-po), and squash them into one or several commits before\nsend pull request to the l10n coordinator's repo (git-l10n/git-po on\nGitHub).\n\n> Some advice would be much appreciated.\n>\n> Kind regards,\n> Jacques\n\n\n\n-- \nJiang Xin\n"}]}