search

DjangoGirls / translation-guide

Other
6 stars 7 forks source link

Translation process description update #8

Open magul opened 4 years ago

magul commented 4 years ago

Since I remember we do not follow onboarding of new translators described in a README.md.

I don't know if anybody actively monitors translations@djangogirls.org. I believe not, as @PluckyPrecious wrote:

I’ve sent series of mail in regards to the resource below point_down , and got no response.

I also know, that:

The topic was started by @PluckyPrecious in https://github.com/DjangoGirls/tutorial/issues/1670.

CC: @PluckyPrecious @das-g

RachellCalhoun commented 4 years ago

Hiya @magul! I just wanted to pop in here to say that I check the translations email but probably not as often as I should. We get about 4 emails every few months at that address. So once a month or so I will go in and reply to all if we have any emails. Thanks for bringing it up!

I would love to update the process and add some automation! When new people want to join the translation project, I check if the project exists, if it doesn't I create it and provide an invite link to join the project.

magul commented 4 years ago

Hey @RachellCalhoun, when you say

I check if the project exists

what do you mean? Do you mean a new language on Crowdin? We can probably stick to the GitHub issues here, they will be a lot more transparent and will allow everybody, that manage Crowdin project to add target language.

RachellCalhoun commented 4 years ago

Yes, when someone emails asking to join a project that is what I have done. I check on crowdin to see if the translation project for that language exists.

I agree transparency is better on github. I think this should probably be part of the larger conversation about the process for onboarding new people.

PluckyPrecious commented 4 years ago

Hi @magul, thanks for helping out to resolve this. 🤝

Hi @RachellCalhoun, Just got your response to the mail thanks. 🤗