You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/stale.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ jobs:
27
27
timeout-minutes: 1# Default: 360
28
28
runs-on: ubuntu-latest
29
29
steps:
30
-
- uses: actions/stale@v9.0.0
30
+
- uses: actions/stale@v9.1.0
31
31
with:
32
32
repo-token: ${{ secrets.GITHUB_TOKEN }}
33
33
stale-issue-message: 'This issue/PR is stale because it has been inactive for 60 days. This issue/PR will be closed automatically with additional 20 days of inactivity. If an update/comment occur on stale issue/PR, the stale label will be removed and the timer will restart. Closed issue/PR can be reopened if necessary.'
Copy file name to clipboardExpand all lines: LOCALIZATION.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Localization
2
2
3
3
Now that the first version of the cloud native glossary is live,
4
-
we'd love to start localizing it into different languages.
4
+
we'd love to start localizing it into different languages.
5
5
6
6
-[Initiate a new localization team](#initiating-a-new-localization-team)
7
7
-[Join an existing localization team](#join-an-existing-localization-team)
@@ -18,34 +18,34 @@ Contributions to improving the following localization guides and localization po
18
18
- The Glossary project does not have a localization team for your language yet
19
19
- check the language list from [localization progress](https://github.com/cncf/glossary/projects/2) and ask in the [glossary-localizations channel in Slack](https://cloud-native.slack.com/archives/C02N2RGFXDF). There may be a group of volunteers who haven't gotten started yet.
20
20
- At least three volunteers
21
-
- At least two approvers
21
+
- At least two approvers
22
22
- two approvers must approve each term
23
-
- unanimous consent must be reached to be approved
23
+
- unanimous consent must be reached to be approved
24
24
- at least one volunteer must have basic GitHub knowledge and be willing to help the others get up to speed (such as PR, review process, branch, ..)
25
25
26
26
## Instructions to initiate a new localization
27
27
28
28
### 1. Join the Slack channel and say hello
29
29
30
-
If you're interested in creating a new localization team, whether you have a team or are on your own, please join the #glossary-localizations channel on the CNCF slack and say hi. If you have at least three volunteers and are ready to start, request a localization channel for your language (e.g., #glossary-localization-korean). If you are still looking for more volunteers, let everyone in the channel know. There may be someone in there looking for a team as well.
30
+
If you're interested in creating a new localization team, whether you have a team or are on your own, please join the #glossary-localizations channel on the CNCF slack and say hi. If you have at least three volunteers and are ready to start, request a localization channel for your language (e.g., #glossary-localization-korean). If you are still looking for more volunteers, let everyone in the channel know. There may be someone in there looking for a team as well.
31
31
32
-
### 2. Opening an issue to notify initiation of a new localization
32
+
### 2. Opening an issue to notify initiation of a new localization
33
33
34
-
[Open an issue](https://github.com/cncf/glossary/issues/new/choose)
34
+
[Open an issue](https://github.com/cncf/glossary/issues/new/choose)
35
35
and select the `Initiate a New Localization Team` template.
36
36
37
37
With this issue, new localization teams are requesting:
38
-
- their own development branch (ex: [dev-ko](https://github.com/cncf/glossary/tree/dev-ko) branch).
38
+
- their own development branch (ex: [dev-ko](https://github.com/cncf/glossary/tree/dev-ko) branch).
39
39
- permission for approving localized content
40
40
- teams will select the most suitable team members as approvers (no more than 4 per localization team)
41
41
```
42
42
l10n team approvers will have push permission to this repository.
43
43
They will manage (merge) PRs for their l10n contributions in their development branch.
44
44
However, their ability to merge PRs to the `main` branch is restricted.
45
45
Please note: although they can review and approve PRs to the `main` branch, they should not approve PRs that aren't related to their own localization teams.
46
-
```
46
+
```
47
47
48
-
Localization teams should use their assigned development branch for the following localization tasks (example of a dev branch: https://github.com/cncf/glossary/tree/dev-ko; dev-ko stands for Korean dev branch).
48
+
Localization teams should use their assigned development branch for the following localization tasks (example of a dev branch: https://github.com/cncf/glossary/tree/dev-ko; dev-ko stands for Korean dev branch).
49
49
50
50
### 3. Configuring a new language
51
51
@@ -71,7 +71,7 @@ For instance, you're adding a new block for the Korean localization. You calcula
71
71
[languages]
72
72
...
73
73
weight = 7
74
-
74
+
75
75
+[languages.ko]
76
76
+title = "클라우드 네이티브(Cloud Native) 용어집"
77
77
+description = "CNCF 클라우드 네이티브 용어집 프로젝트는 클라우드 네이티브 애플리케이션에 대한 대화를 나눌 때 공통의 용어를 참조하여 사용하도록 하는 목적을 가지고 있다."
@@ -93,7 +93,7 @@ For a new localization, add a file `i18n/<localization>.toml` based on `i18n/en.
93
93
Translated Glossary terms are saved in the appropriate language directory inside `/content/`.
94
94
95
95
Create a subdirectory in `content` and name it using the appropriate two-letter language code (`content/<localization>`).
96
-
For example,
96
+
For example,
97
97
```
98
98
contents/en
99
99
contents/ko
@@ -104,7 +104,7 @@ contents/ko
104
104
105
105
Localize content and save to `content/<localization>`.
- How to contribute: `content/en/contribute/_index.md` -> `content/<localization>/contribute/_index.md`
@@ -138,15 +138,15 @@ Once the PR is merged, the localized content will go live on its website 🎉
138
138
139
139
To join an existing team, hop on the #glossary-localizations and #glossary-localization-[language name] channels on the CNCF Slack. Introduce yourself, let the team know you want to contribute, and the team will take it from there.
140
140
141
-
If the team seems inactive (no response after several days), reach out to @Seokho Son, @Jihoon Seo, @nate-double-u, or @Noah Ispas on the #glossary-localizations channel.
141
+
If the team seems inactive (no response after several days), reach out to @Seokho Son, @Jihoon Seo, @nate-double-u, @Noah Ispas or @Junya Okabe on the #glossary-localizations channel.
142
142
143
-
---
143
+
---
144
144
145
145
# Localization team guidelines
146
146
147
147
Every localization team may have its own process of working on localizing terms. However, here are some guidelines that are common for all localization teams:
148
148
149
149
1. Only terms with the status `Completed` in the English version are ready to be localized.
150
-
2. All contributions related to localization have to be based on the `dev-xx` branch, and PRs need to target `dev-xx`.
151
-
3. Localization teams need to get changes from the `main` branch in their `dev-xx` branch from time to time. Therefore a PR should be opened where the `main` branch is merged into `dev-xx`. The glossary maintainers will then choose the rebase method to complete the PR and keep the history linear.
150
+
2. All contributions related to localization have to be based on the `dev-xx` branch, and PRs need to target `dev-xx`.
151
+
3. Localization teams need to get changes from the `main` branch in their `dev-xx` branch from time to time. Therefore a PR should be opened where the `main` branch is merged into `dev-xx`. The glossary maintainers will then choose the rebase method to complete the PR and keep the history linear.
152
152
4. A localized term does not have to match the English version completely. Also, the localized and English versions of terms can coexist independently throughout updates. Localization teams can decide to which degree localized terms have to match their English version and how to handle updates on the English term. To learn how other teams keep up to date with changes in the English version, please refer to [this discussion on the topic](https://github.com/cncf/glossary/discussions/1125).
0 commit comments