Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation process description update #8

Open
magul opened this issue Jul 16, 2020 · 4 comments
Open

Translation process description update #8

magul opened this issue Jul 16, 2020 · 4 comments

Comments

@magul
Copy link
Member

magul commented Jul 16, 2020

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

I don't know if anybody actively monitors [email protected]. 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 DjangoGirls/tutorial#1670.

CC: @PluckyPrecious @das-g

@RachellCalhoun
Copy link

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
Copy link
Member Author

magul commented Jul 16, 2020

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
Copy link

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
Copy link

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants