OSPOs to improve processes/ tools to ease translation contributions? #185
Replies: 2 comments
-
The Kubernetes project has a good framework that we could follow: See https://kubernetes.io/docs/contribute/localization/. Some key parts would be: Create a README (Kubernetes example) that tells people how to build, test, and troubleshoot the documentation. Decide upon a set of minimum required content for localized documentation to be mereged into master. I would suggest the Cilium Overivew, Cilium Installation, Community, and Development Guide sections. Make sure the docs fall back to English rather than 404 when a page has not been translated yet. Reference These two talks from Zach Corleissen are also helpful to understand how Kubernetes did it: Multilingual Kubernetes: The kubernetes.io stack, how we got there, and what it took to get there Localize your open source documentation: a Kubernetes case study |
Beta Was this translation helpful? Give feedback.
-
A few options used by others out there: http://zanata.org - Openstack, Red Hat related communities etc (also open source) |
Beta Was this translation helpful? Give feedback.
-
Sometimes, language barrier might be critical to prevent non-native English-speaking organizations (e.g APAC or European regions) to use / contribute to open source projects. IMHO, contributions to translations are important in the OSPO ecosystem to:
My question is, are there any OSPOs working to improve processes/ tools to ease translation contributions? If so, could you share any best practices?
Beta Was this translation helpful? Give feedback.
All reactions