Hi Masakazu, Thank you very much for your feedback. For the 2nd one, I've made a brief schedule, including "Topic, translator, reviewer, status (translated/approved)". See the attachment for the general workflow, and I'll write a detailed one so all contributors and reviewers can follow.
With the brief schedule, contributors can check which topics are not translated by others, so they can select topics and begin translation whenever possible. When they create a pull request, they are updating the translation schedule. After finishing translation, contributors will leave a message in the PR (such as, I've finished the translation, could you please help review?) When reviewers get the message, they will review the topic in Crowdin, and give feedback to the contributors in PR(good, bad, improvement, etc). If some terms need discussion, they can also discuss in this PR. Before, contributors translate as they wish, with different translation styles. They are not consistent, and sometimes they found that they were translating the same topic, so later they tried to contact me offline to select topics. While reviewing, I've tried to make comments and create discussion in Crowdin, and found few translators check my comments or discussion (The following is a discussion example https://crowdin.com/project/apache-pulsar/discussions/2/0/home). That's why I want to create a public repo, to promote consistent translation guidelines, workflow, Pulsar terms, and make schedule public to all contributors. If possible, encourage more translation contributors among the community, improve translation quality and process with the interaction with contributors on Github. So the master translation data are still on Crowdin. The Github stores Pulsar translation guidelines, workflow, translation memory, translation schedule. I've consulted Flink community, they use mailing list to assign translation tasks, and it's not quite highly efficient, they also encounter some problems in quality and tracking status. So could we try Github to improve this with Github? Best Regards, Jennifer On Tue, Jul 16, 2019 at 11:20 PM Masakazu Kitajo <mas...@apache.org> wrote: > Hi Jennifer, > > Could you share projects that do similar translation task management if you > know some? > > Ideas 1) and 3) sound good me too, but I couldn't imagine how 2) will be > like. It says contributors can submit pull requests, but what files will be > stored in the GitHub repo? I assume the master translation data is > currently on Crowdin. How will the contributions made on GitHub be brought > to Crowdin? > > It would be great if you could show us a flowchart or a swimlane. > > Thanks, > Masakazu > > On Mon, Jul 15, 2019 at 1:19 PM Jinfeng Huang <h...@streamnative.io> wrote: > > > Hi all, > > > > Currently we are using Crowdin to manage I18N for Pulsar documentation. I > > (hjf) have been managing the translation tasks on Crowdin, There are a > few > > problems when more and more contributors start contributing translation. > > > > a) There is no simple way to report documentation issues related to > > translation. For example, sometimes translation can screw up the layout > and > > format. Whoever found the issues and talked to me offline, and I fixed > > them. > > b) Contributors talked to me for requesting translation tasks offline. > The > > process for task assignment is not tracked by ASF. > > > > In order to overcome the problems, I am proposing creating a new > > `pulsar-translation` repo under ASF. The repo can be used for > > > > 1) Users can report documentation issues found in non-english > documentation > > website. > > 2) Contributor can submit pull requests for translation topics, so that > > everyone can see how topics are assigned in Github, and avoid any > > duplicated work. > > 3) Set consistent translation guidelines so contributors can follow. > > > > Any thoughts? > > > > Best Regards, > > Jennifer > > >
