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 >
