Hi Masakazu, I've created a test repo at https://github.com/Jennifer88huang/Pulsar_translation For details, see my test pull request at https://github.com/Jennifer88huang/Pulsar_translation/pull/1
Any other issue, feel free to contact me. Thank you very much for all your comments and help. Best Regards, Jennifer On Wed, Jul 17, 2019 at 10:33 PM Jinfeng Huang <[email protected]> wrote: > Hi Masakazu, > > Do you mean we will have a file that contains a table with those columns > and a modification against the file (table) will be shown as the diff? It > sounds like creating an Issue instead is enough to me. > https://swimlanes.io/d/8L04SRASw > > Yes, you are correct, your workflow illustrates my idea perfectly. Thank > you very much for offering the detailed workflow. > When I had the idea to create a Github repo, the first thing came to my > mind was also to create an issue. When I thought over the workflow, I > thought a PR might work more efficiently than an issue, so I came up with > the schedule table. If an issue works well for the workflow, we can surely > adopt issues. > > An example pull request may help understand the flow. Could you make it on > a test repo? > Yes, I'll make it on a test repo soon, and will provide relative link > later. > > Currently, the workflow source file is on lucidchart at > https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff. > When there is a repo, I will share the source file on the repo, and make it > editable by anyone. > > Thank you very much for all your comments and valuable advice. I hope our > discussion will help us better handle the translation project and Github > repo. > > Best regards, > Jennifer > > > On Wed, Jul 17, 2019 at 9:25 PM Masakazu Kitajo <[email protected]> wrote: > >> Hi Jennifer, >> >> On Wed, Jul 17, 2019 at 8:38 PM Jinfeng Huang <[email protected]> >> wrote: >> >>> Hi Masakazu, >>>> Thanks for your reply. >>>> >>>> It is designed to create a pull request with the schedule ("Topic, >>>> translator, reviewer, status (translated/approved)), and provide a platform >>>> for effective communication between translators and reviewers. >>>> >>> >> Do you mean we will have a file that contains a table with those columns >> and a modification against the file (table) will be shown as the diff? It >> sounds like creating an Issue instead is enough to me. >> https://swimlanes.io/d/8L04SRASw >> >> An example pull request may help understand the flow. Could you make it >> on a test repo? >> >> >>> >>>> Surely, contributors can contribute to translation guidelines, >>>> workflow, terms, and other content on GitHub later with PR, and use this >>>> repo to report translation issues. >>>> >>> The actual translation strings are still on Crowdin. >>> >>>> >>>> I've pasted the workflow below, and also sent with attachment (in case >>>> one way does not work). >>>> >>> >> Now I can see the workflow, thanks. It would be great if we could have >> the source file (ideally editable with free tools) on the repo so that >> anybody can modify it and suggest a new flow in the future. >> >> I'm sorry to bother you, but I just want to understand your proposal >> correctly. I hope this conversation will reduce future questions. >> >> Thanks, >> Masakazu >> >> >>> [image: translation-workflow.png] >>>> Best Regards, >>>> Jennifer >>>> >>>>
