Per today's SIG-Docs meeting, we want to localize the contributor cheatsheet.
The actual content in the below link:
https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet
The translated content would be put into community repo as well.
/kind feature
+1
Per-language task issues were created:
/cc @zacharysarah
/cc @mrbobbytables
Wonderful, thank you so much! o/
+1
+1
How is localization managed inside the community repository? It is not a hugo website so I am not sure about how the different languages are managed there.
For this specifically it would probably be best to mimic the format used in the root of the website repo. Within the contributor-cheatsheet directory add a README-<ISO 639-1 lang code>.md. We can then update the welcome message bot to include links to the translated copies 😄
@chenrui333 👋 Thanks for opening this.
For English, I'd like this issue to include adding a section to this page, below Ways to Contribute:
## Feature development
You can also contribute to Kubernetes feature development. The [contributor cheatsheet](https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet) can help you get started.
Other localizations can include that section with a link to their localization-specific cheatsheet.
@zacharysarah
I see your point, I will file a PR now.
Taking the lead for the French translation https://github.com/kubernetes/community/pull/3658
Translation of the localize contributor cheatsheet in Korean is done. (ref : kubernetes/community#3660)
I'm working on Ukrainian uk localization.
/reopen
accidentally closed by https://github.com/kubernetes/community/pull/3660
@mrbobbytables: Reopened this issue.
In response to this:
/reopen
accidentally closed by https://github.com/kubernetes/community/pull/3660
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
checkin
/remove-lifecycle stale
Current state as of 15th Aug 2019(Feel free to edit when it has to be changed)
/lifecycle frozen
/priority backlog
I'm working on Ukrainian uk localization.
@bigfootlviv any progress so far? Would be glad to join forces)
Most helpful comment
Per-language task issues were created:
/cc @zacharysarah