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

Rename Others tabs in the Quick-Start #9953

Closed
SD-13 opened this issue Jan 3, 2024 · 5 comments · Fixed by #10031
Closed

Rename Others tabs in the Quick-Start #9953

SD-13 opened this issue Jan 3, 2024 · 5 comments · Fixed by #10031
Assignees
Labels
area/documentation Issues or PRs related to documentation 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. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@SD-13
Copy link
Contributor

SD-13 commented Jan 3, 2024

Had a small conversation here https://kubernetes.slack.com/archives/C8TSNPY4T/p1703707530548349
In the quickstart guide, for cloud providers (at least where I faced it. For me, it was Azure) we need to follow instructions from the Others... tab. But the name Others... is not much meaningful here. Any thoughts on renaming this?

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 3, 2024
@fabriziopandini
Copy link
Member

I don't have issues with "Others..." given that those tabs are list of providers , but I'm ok in renaming it in "Other proivders..." (both two instances)
/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 Jan 18, 2024
@fabriziopandini fabriziopandini changed the title Make installation instruction clear Rename Others tabs in the Quick-Start Jan 18, 2024
@fabriziopandini
Copy link
Member

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini:
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:

/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 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. labels Jan 18, 2024
@fabriziopandini
Copy link
Member

/area documentation

@k8s-ci-robot k8s-ci-robot added the area/documentation Issues or PRs related to documentation label Jan 19, 2024
@SD-13
Copy link
Contributor Author

SD-13 commented Jan 20, 2024

Thanks @fabriziopandini, "Other proivders..." sounds better to me. I can change it.
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation 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. 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.

3 participants