-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Putting together an internationalization team #3986
Comments
The members of this team would be open to set policies as they see fit, but for reference here are my philosophies on i18n:
I also wrote up some more specific guidelines back in the day on #1318. Personally, I'm happy to help maintain the Japanese translation. |
I would be willing to contribute to Slovak translations. It's the least I can do for this project. |
My native language is french, I am interested in maintaining the french translations. |
I am not able to commit the time required for fully creating and maintaining Dutch translations. But I am willing to help as part of a team. |
Thanks to everyone for speaking up - but finding people to contribute to individual translations is not what I'm looking for in this issue. |
Looking for some motivated contributors to take the lead on a permanent i18n team, whose responsibilities will include finding and managing the translators for various languages and organizing work to translate the README, wiki, and man pages - and keep them up to date. This could also involve setting up sway sub-communities in various languages, such as language-specific IRC channels and support mediums. The goal is to establish a team which is as disciplined and motivated in keeping the translations high-quality and up-to-date as the engineering team is with the code.
Is anyone up for the task?
The text was updated successfully, but these errors were encountered: