Localize Kubernetes website into Arabic

[seokho-son]

This is a Feature Request

Initial minimum-viable Arabic localization.

What would you like to be added

Hope to add the first live version of Arabic localization for k8s.io
This issue is to (re)initiate Arabic localization efforts based on following actionable items.

Actionable items identified from https://kubernetes.io/docs/contribute/localization/#start-a-new-localization

• 1. Select the language code for Arabic

• ref: https://kubernetes.io/docs/contribute/localization/#start-a-new-localization

• the language code for Arabic: ar

• 2. Add a slack channel for Arabic

• https://kubernetes.io/docs/contribute/localization/#find-community

• slack channel for Arabic: #kubernetes-docs-ar

• 3. Add a label for Arabic

• https://kubernetes.io/docs/contribute/localization/#configure-the-workflow

• label for Arabic: language/ar Issues or PRs related to Arabic language

• 4. Localize the community code of conduct

• https://kubernetes.io/docs/contribute/localization/#localize-the-community-code-of-conduct

• code of conduct: https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/ar.md

• 5. Invite candidates for @kubernetes/sig-docs-ar-owners and @kubernetes/sig-docs-ar-reviews

• https://kubernetes.io/docs/contribute/localization/#add-your-localization-team-in-github

• current reviewers: @mboukhalfa, @adowair, @seifrajhi

• current approvers: @mboukhalfa, @adowair, @seifrajhi

• current team members: @mboukhalfa, @seifrajhi, @adowair, @essamgouda97, @AbdelatifAitBara

• 6. Check the all candidates are the member of the Kubernetes GitHub organization

• https://kubernetes.io/docs/contribute/localization/#join-the-kubernetes-github-organization

---

• 7. Add a development branch for Arabic localization

• https://kubernetes.io/docs/contribute/localization/#source-files

• https://kubernetes.io/docs/contribute/localization/#branch-strategy

• Note: members of @kubernetes/website-maintainers can create new localization branches to coordinate translation efforts.

• Note: Netlify preview needs to be configured for the dev branch

• Dev branch: dev-1.29-ar.1 https://github.com/kubernetes/website/tree/dev-1.29-ar.1

• 8. Open a PR to configure a localization environment

• Note: base and target branches of the PR should be the dev branch of AR.

  • Add a configuration block for the new language to hugo.toml
  • https://kubernetes.io/docs/contribute/localization/#modify-the-site-configuration
  • Add a new localization directory
  • https://kubernetes.io/docs/contribute/localization/#add-a-new-localization-directory
  • Add and localize site strings in i18n
  • https://kubernetes.io/docs/contribute/localization/#site-strings-in-i18n
  • Set up the OWNERS files based on the candidate list
  • https://kubernetes.io/docs/contribute/localization/#set-up-the-owners-files
  • Check build test and site-preview of the PR

• 9. Open PRs to localize all minimum-required-contents and a localized README file

• https://kubernetes.io/docs/contribute/localization/#minimum-required-content

  • [ar] Translate Minimum Required Documentation Pages to Arabic #37546

• https://kubernetes.io/docs/contribute/localization/#add-a-localized-readme-file

• Note: base and target branches of the PR should be the dev branch of AR.
  Note: at this moment, candidates for Arabic reviewers and approvers do not have an authority yet. However reviews on localized contents from the candidates are required. Use /lgtm to express a PR is ready to be merged.

• 10. Open a PR to merge the dev branch into

• https://kubernetes.io/docs/contribute/localization/#launch-your-new-localization

  • Check build test and site-preview of the PR

/language ar

[dipesh-rawat]

/area localization

[sftim]

/retitle Localize Kubernetes website into Arabic

[sftim]

@seokho-son we typically ask for at least draft PRs before we'd make a localization branch. This cuts down the effort to maintain branches if it turns out that the localization team doesn't sustain the work.

[sftim]

(you can change the target branch of a PR after it's opened, so the draft PRs can turn into real PRs once the branch is made).

[seokho-son]

Note: Current Status of Arabic Localization

There is a stalled issue regarding Arabic localization, #37546. I opened this issue to assist Arabic contributors in reinitiating (or making a fresh start on) contributions, focusing solely on establishing the first live version.

Additionally, there have been several attempts by various contributors in the past, but these were neither completed nor sustained.
https://github.com/kubernetes/website/pulls?q=is%3Apr+label%3Alanguage%2Far

I assume it's challenging to continue with the previous draft PRs, considering their age and the uncertainty about whether the original contributors are still willing to continue.

SIG-Docs localization subproject has recently requested assistance from some individuals to help with the initiation. I hope to use this issue to assist Arabic contributors build a team and their localization environment. I plan to invite contributors who are eager to help establish the first live version of Arabic localization and to identify potential reviewer and approver candidates.

[sftim]

If folk want advice on what those initial pull requests might look like, please reply here. We can link you up to people who can offer help.

[seokho-son]

@seokho-son we typically ask for at least draft PRs before we'd make a localization branch. This cuts down the effort to maintain branches if it turns out that the localization team doesn't sustain the work.

Hello @sftim, thank you for sharing this information. Indeed, we typically ask for at least draft PRs to the main branch before we'd make a localization branch.

While creating this issue, I looked through https://kubernetes.io/docs/contribute/localization/#start-a-new-localization and listed only the actionable tasks based on this guide. However, it seems that creating draft PRs targeting the main branch is not included in the guide. (Perhaps, updating the guide might be necessary if required.)

However, whereas creating draft PRs can help in managing dev branches, it also tends to create a slightly complex situation for teams starting their first contributions. Additionally, opening PRs targeting main can be inconvenient, as we cannot merge interim work if everything in a single PR is not perfectly completed. If there are several draft PRs (PRs to configure localization, PRs to cover minimum-required-contents, ..), contributors are hard to check preview from each PR since base localization configuration cannot be merged into the main without minimum-required-contents.

Considering that several previous attempts have also not overcome this hurdle, how about we start by creating a dev branch first this time?

[sftim]

/triage accepted
/priority backlog

[seokho-son]

SIG-Docs localization subgroup leads (myself, @a-mccarthy) are going to help alongside Arabic contributors this time and complete the tasks in the issue.

---

Hi folks! I've compiled this list from issues and PRs related to Arabic localization. I hope you are willing to help with this (re)initiation effort for Arabic!

@adowair
@mboukhalfa
@mhamdisemah
@mohamedsgap
@nofalx
@essamgouda97

Additionally, any contributors interested in helping with this issue, please let us know.

[seokho-son]

• Created a development branch for Arabic: https://github.com/kubernetes/website/tree/dev-1.29-ar.1

Please utilize the dev-1.29-ar.1 as the base branch for initiating Arabic localization.

[seokho-son]

Working on setting up Netlify for dev-1.29-ar.1

[adowair]

✅ Signing myself up to be an active contributor to this initiative. I am not yet a Kubernetes organization member.

[essamgouda97]

I would like to be an active contributor for Arabic translation. I am not yet a k8s org member.

[seifrajhi]

Additionally, any contributors interested in helping with this issue, please let us know.

Count me in please! I'm keen to contribute to the Arabic translation efforts.

[seokho-son]

Hello @adowair, @essamgouda97, @seifrajhi, and @mboukhalfa (I'm awaiting @mboukhalfa's participation in this discussion. Please leave a comment below.),
Thank you for your commitment to actively contributing to the Arabic team. 😊

When submitting a PR, please reference this Issue to help us effectively monitor our progress.

• [ar] Add and localize i18n strings to Arabic #44862 (call for review on Arabic content)
• [ar] Translate setup/_index.md #44289 (call for review on Arabic content)
• Localize home/supported-doc-versions.md to Arabic #44698 (call for review on Arabic content)
• Create basic structure and translate home for Arabic #44902 (call for review on Arabic content)
• [ar] Translate home index to arabic #45031
• ...

Also, who is interested in serving as a reviewer or an approver for Arabic? It's important to note that not all contributors are required to take on these roles, as they come with significant responsibilities. You can learn more about these roles here: Reviewers. Approvers

You can apply for both roles, but remember that the fast track is only available during the initial phase of introducing a new language. Generally, being a reviewer or an approver involves a considerable time commitment.

If you're interested in either role, please start by reviewing the Arabic content in the above PRs. Leave a comment (ex: LGTM for Arabic) if you are satisfied with Arabic content within the PR.
We will consider reviewer/approver candidates based on their review and contribution activities.

[seokho-son]

Hi @mboukhalfa

• Regarding your PR Create basic structure and translate home for Arabic #44902 , I suggest separating some contents to simply and remove duplicated works.
  • Let's remove files regarding (data) i18n/ar/* i18n strings and utilize [ar] Add and localize i18n strings to Arabic #44862 from @adowair
  • Let's remove content/ar/docs/home/supported-doc-versions.md and utilize Localize home/supported-doc-versions.md to Arabic #44698

[seifrajhi]

I reviewed this PR 44698 and it is now merged 🎉

[adowair]

Nominated Approvers and Reviewers

To achieve Step 5 above:

5. Invite candidates for @kubernetes/sig-docs-ar-owners and @kubernetes/sig-docs-ar-reviews

From our last team meeting March 13th, 2024 (minutes):

Nominated Reviewers:

• @seifrajhi
• @essamgouda97
• @adowair

Nominated Approvers:

• @mboukhalfa (already org member)
• @adowair (not org member yet)
• @seifrajhi (if needed, not org member yet)

[AbdelatifAitBara]

Hi @seokho-son,

Is there anything I can help with? I am a native Arabic Speaker.
Regards.

[adowair]

Hello @AbdelatifAitBara, thanks for joining the thread! Yes, there's a lot to help with

I see you've already joined the Slack channel. We have meetings every Wednesday at 17:00 GMT (Calendar Event, Zoom, Minutes, Recordings), and it'd be great for you to join us there to get started.

Welcome aboard!

[AbdelatifAitBara]

Thank you for all information @adowair 🥇

[adowair]

@seokho-son I believe steps 6, 7, and 8 are now complete, so we can check them off above 😄

6. @mboukhalfa, @seifrajhi, and @adowair are org members
   @essamgouda97 @AbdelatifAitBara are contributing and hope to be members soon
7. The branch dev-1.29-ar.1 exists
8. Add configuration block for Arabic to hugo.toml #44731
   Localize home/supported-doc-versions.md to Arabic #44698
   Create OWNERS for ar localization #45793 [ar] Add mboukhalfa as owner for arabic content #45541 Add adowair as owner, reviewer for Arabic content #45815

[mboukhalfa]

@seokho-son step 8 ✅ Set up the OWNERS files based on the candidate list
done here #45793

[seokho-son]

Thanks @mboukhalfa
I've checked from https://github.com/kubernetes/website/blob/dev-1.29-ar.1/OWNERS_ALIASES#L200 :)

Are there any additional reviewer or approver candidates still preparing for onboarding?

[mboukhalfa]

@essamgouda97 and @AbdelatifAitBara are progressing and planning to submit their membership requests soon!
Our team now is pretty organized we can onboard newcomers locally and nominate the potential reviewers and approvers!

[mboukhalfa]

@seokho-son Can you please link this issue #37546 with the first item on step 9