Skip to content

Translation information in README.md #698

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

Merged
merged 4 commits into from
Jan 14, 2017
Merged

Conversation

gbezyuk
Copy link
Contributor

@gbezyuk gbezyuk commented Jan 11, 2017

I'm dreaming of making Translation Gang an international community of open-source translators, so there's a little bit of advertisement here, not just the information on existing translation projects.

I'm dreaming of making Translation Gang an international community of open-source translators, so there's a little bit of advertisement here, not just the information on existing translation projects.
@chrisvfritz
Copy link
Contributor

I don't mind the advertisement if it could lead to a more thriving translation community. 🙂 Can you tell me more about what you hope to do with Translation Gang? And do you want to add a contact link in that section?

@gbezyuk
Copy link
Contributor Author

gbezyuk commented Jan 12, 2017

Well, there are many amazing open-source projects worldwide, and there are many awesome people ready to help with translations of these projects` documentation. But the issue is that it's enthusiasm is not a constant thing, while good project's life is long. So, there should be an organisation "in charge", taking responsibility for both completing translations and maintaining the docs in actual condition.

I seem to have succeeded in organising Translation Gang as a translators community for Russian language and Vue-related projects: while the core library docs were translated by me almost alone, at the stage of proof-reading there were already tens of people, and Nuxt.js docs were recently translated in a matter of days with only about 10% of actual translation done by me. And we also seem to be quite good at maintaining the docs in actual condition — for most of original docs updates the latency with translation is less then a day, normally just some hours. In fact, we are even awaiting for two of original repo PRs right now, having translations already done.

So, Russian is not the only language which could benefit from the organised workflow, and Vue is not the only project we're interested in. Which means, we need more enthusiastic people =)

Also, there are good projects developed by people not so good at speaking English as writing the code. And these projects also could benefit from the involvement of the organised open-source translation community.

So, basically, I just want to make this world a bit better, if you could forgive me this high style =)

@gbezyuk
Copy link
Contributor Author

gbezyuk commented Jan 12, 2017

And about the contact link — I've simply used the VCard link as there are no private messages at GitHub AFAIK, so I guess it's better to give an interested person a way to contact me, not just a github nickname.

@chrisvfritz
Copy link
Contributor

@gbezyuk Have you added the VCard link? I'm happy to merge this after that.

@gbezyuk
Copy link
Contributor Author

gbezyuk commented Jan 14, 2017

@chrisvfritz done ;)

@gbezyuk
Copy link
Contributor Author

gbezyuk commented Jan 14, 2017

BTW, @kazupon could you please add information on Japanese translation?

@chrisvfritz chrisvfritz merged commit 57c1f29 into vuejs:master Jan 14, 2017
@chrisvfritz
Copy link
Contributor

Vuetiful! 😉

@kazupon
Copy link
Member

kazupon commented Jan 14, 2017

@gbezyuk Yes, I could add information about japanese translation!

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

Successfully merging this pull request may close these issues.

3 participants