Skip to content
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

[ja] Translate content/en/docs/reference/glossary/cidr.md into Japanese #45112

Closed
Okabe-Junya opened this issue Feb 13, 2024 · 4 comments · Fixed by #46267
Closed

[ja] Translate content/en/docs/reference/glossary/cidr.md into Japanese #45112

Okabe-Junya opened this issue Feb 13, 2024 · 4 comments · Fixed by #46267
Assignees
Labels
area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Okabe-Junya
Copy link
Member

This is a Feature Request

What would you like to be added

Translate content/en/docs/reference/glossary/cidr.md into Japanese

Why is this needed

There is no Japanese translation for this page

Comments

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

@Okabe-Junya Okabe-Junya added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 13, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 13, 2024
@Okabe-Junya
Copy link
Member Author

/area localization
/language ja
/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@Okabe-Junya:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/area localization
/language ja
/good-first-issue

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.

@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. language/ja Issues or PRs related to Japanese language help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 13, 2024
@nasa9084
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 11, 2024
@hihumikan
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/localization General issues or PRs related to localization good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants