kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update some contributor page

This commit is contained in:
Sean Wei 2022-09-20 00:21:27 +08:00
parent baf378ea19
commit 36899cd93c
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/contribute/new-content/blogs-case-studies.md
View File

@ -85,8 +85,8 @@ To submit a blog post, follow these steps:
- If you are looking for greater coordination on post release dates, coordinating with - If you are looking for greater coordination on post release dates, coordinating with
[CNCF marketing](https://www.cncf.io/about/contact/) is a more appropriate choice than submitting a blog post. [CNCF marketing](https://www.cncf.io/about/contact/) is a more appropriate choice than submitting a blog post.
- Sometimes reviews can get backed up. If you feel your review isn't getting the attention it needs, - Sometimes reviews can get backed up. If you feel your review isn't getting the attention it needs,
you can reach out to the blog team via [this slack channel](https://kubernetes.slack.com/messages/sig-docs-blog/) you can reach out to the blog team on the [`#sig-docs-blog` Slack channel](https://kubernetes.slack.com/messages/sig-docs-blog/)
to ask in real time. to ask in real time.
- Blog posts should be relevant to Kubernetes users. - Blog posts should be relevant to Kubernetes users.

4
content/en/docs/contribute/new-content/new-features.md
View File

@ -32,7 +32,7 @@ After you've chosen a feature to document or assist, ask about it in the `#sig-d
Slack channel, in a weekly SIG Docs meeting, or directly on the PR filed by the Slack channel, in a weekly SIG Docs meeting, or directly on the PR filed by the
feature SIG. If you're given the go-ahead, you can edit into the PR using one of feature SIG. If you're given the go-ahead, you can edit into the PR using one of
the techniques described in the techniques described in
[Commit into another person's PR](/docs/contribute/review/for-approvers/#commit-into-another-persons-pr). [Commit into another person's PR](/docs/contribute/review/for-approvers/#commit-into-another-person-s-pr).
### Find out about upcoming features ### Find out about upcoming features
@ -117,7 +117,7 @@ When ready, populate your placeholder PR with feature documentation and change
the state of the PR from draft to **ready for review**. To mark a pull request the state of the PR from draft to **ready for review**. To mark a pull request
as ready for review, navigate to the merge box and click **Ready for review**. as ready for review, navigate to the merge box and click **Ready for review**.
Do your best to describe your feature and how to use it. If you need help structuring your documentation, ask in the `#sig-docs` slack channel. Do your best to describe your feature and how to use it. If you need help structuring your documentation, ask in the `#sig-docs` Slack channel.
When you complete your content, the documentation person assigned to your feature reviews it. When you complete your content, the documentation person assigned to your feature reviews it.
To ensure technical accuracy, the content may also require a technical review from corresponding SIG(s). To ensure technical accuracy, the content may also require a technical review from corresponding SIG(s).

8
content/en/docs/contribute/review/for-approvers.md
View File

@ -81,14 +81,14 @@ Prow Command | Role Restrictions | Description
:------------|:------------------|:----------- :------------|:------------------|:-----------
`/lgtm` | Organization members | Signals that you've finished reviewing a PR and are satisfied with the changes. `/lgtm` | Organization members | Signals that you've finished reviewing a PR and are satisfied with the changes.
`/approve` | Approvers | Approves a PR for merging. `/approve` | Approvers | Approves a PR for merging.
`/assign` | Reviewers or Approvers | Assigns a person to review or approve a PR `/assign` | Anyone | Assigns a person to review or approve a PR
`/close` | Reviewers or Approvers | Closes an issue or PR. `/close` | Organization members | Closes an issue or PR.
`/hold` | Anyone | Adds the `do-not-merge/hold` label, indicating the PR cannot be automatically merged. `/hold` | Anyone | Adds the `do-not-merge/hold` label, indicating the PR cannot be automatically merged.
`/hold cancel` | Anyone | Removes the `do-not-merge/hold` label. `/hold cancel` | Anyone | Removes the `do-not-merge/hold` label.
{{< /table >}} {{< /table >}}
See [the Prow command reference](https://prow.k8s.io/command-help) to see the full list To view the commands that you can use in a PR, see the
of commands you can use in a PR. [Prow Command Reference](https://prow.k8s.io/command-help?repo=kubernetes%2Fwebsite).
## Triage and categorize issues ## Triage and categorize issues