Hi Masakazu,
Thank you very much for your feedback.
Indeed, there are some weakness in using pull request to track the
schedule. And thank you for your advice in using "Projects" for status
management.
We can try to run it, and improve in the process, and make it better and
efficient.
Best Regard
Yeah, nothing is perfect at the beginning. Let’s start something soon and
we can iterate the process.
Sijie
On Sun, Jul 21, 2019 at 11:19 AM Masakazu Kitajo wrote:
> Hi Jennifer,
>
> Thanks for the examples. The examples really help understanding.
>
> Weakness in using Pull Request I think are:
FYI. I first created the repo : https://github.com/apache/pulsar-translation So
we can move the discussion into actions.
We can still continue iterating and come out an efficient process for
managing pulsar translation.
- Sijie
On Sun, Jul 21, 2019 at 2:57 PM Sijie Guo wrote:
> Agreed. Nothing
Agreed. Nothing is perfect until we run it. Let's start with the proposal.
We can iterate the process from there.
- Sijie
On Sun, Jul 21, 2019 at 11:19 AM Masakazu Kitajo wrote:
> Hi Jennifer,
>
> Thanks for the examples. The examples really help understanding.
>
> Weakness in using Pull Reques
Hi Jennifer,
Thanks for the examples. The examples really help understanding.
Weakness in using Pull Request I think are:
- New schedule proposed will not be shown on the table until somebody merge
PRs -- This require checking two tables, PRs and the table
- When a status changes, somebody need t
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 R
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 m
Hi Jennifer,
On Wed, Jul 17, 2019 at 8:38 PM Jinfeng Huang 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 betwee
>
> 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.
>
> Surely, contributors can contribute to
Thanks for the explanation. It seems like the attachment was lost at
somewhere. I couldn't find the workflow.
I understand the background and I'm fine with using GitHub to improve our
translation process. I also think it doesn't have to be an established way.
We can try it. I just thought it might
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
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 t
SGTM. +1 for tracking the translation tasks under the ASF.
- Sijie
On Mon, Jul 15, 2019 at 12:19 PM Jinfeng Huang 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
> problem
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
14 matches
Mail list logo