Skip to content

Commit 5cc83a8

Browse files
committed
updated as per suggestions
1 parent 67b931e commit 5cc83a8

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

content/en/docs/contribute/participate/issue-wrangler.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,15 @@ weight: 20
66

77
<!-- overview -->
88

9-
There are many issues that need triage, and in order to reduce our reliance on formal approvers or reviewers, we have introduced a new role to wrangle issues every week.The main responsibility of this role is to bridge the gap between organizational contributor and reviewer.
10-
This section covers the duties of a PR wrangler.
9+
In order to reduce the burden on the [PR Wrangler](/docs/contribute/participate/pr-wrangler), formal approvers, and reviewers, members of SIG Docs take week long shifts [triaging and categorising issues](/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for the repository.
1110

1211
<!-- body -->
1312

1413
## Duties
1514

1615
Each day in a week-long shift as Issue Wrangler:
1716

18-
- Making sure the issue is worded and titled correctly to provide contributors with adequate information.
17+
- Triage and tag incoming issues daily. See [Triage and categorize issues](https://github.com/kubernetes/website/blob/main/docs/contribute/review/for-approvers/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata.
1918
- Identifying whether the issue falls under the support category and assigning a "triage/accepted" status.
2019
- Assuring the issue is tagged with the appropriate sig/area/kind labels.
2120
- Keeping an eye on stale & rotten issues within the kubernetes/website repository.

0 commit comments

Comments
 (0)