1# SIG cli maintainers Guide
2
3## Sustaining engineering tasks
4
5The following tasks need to be performed consistently as a part of maintaining the health
6of SIG cli. We will be developing an oncall rotation for working on these tasks, where
7the oncall is responsible to doing each task daily.
8
9### Issue triage
10
11Routinely monitor the newly filed issues and triage them to make sure we identify regressions.
12
13[Kubectl repo](https://github.com/kubernetes/kubectl/issues)
14
15[Kubernetes repo](https://github.com/kubernetes/kubernetes/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Asig%2Fcli)
16
17Look for:
18
19- Requests for help
20 - Don't spend a lot of time on these, but answer and close them if it is easy
21- Regressions and bugs
22 - Find the root cause
23 - Triage the severity
24 - Issues only occurring in old versions but not in new versions are less severe
25- Simple issues for new contributors
26 - Label these with "for-new-contributors"
27 - Give them a priority
28 - Make sure they are
29 - Small
30 - Well scoped
31 - In areas of code with minimal technical debt
32 - In areas of code with strong ownership already
33- Feature requests
34 - Do one of
35 - Close them with an explanation along the lines of "Don't have capacity right now, try reopening in 6 months"
36 - Label them with a "priority"
37
38### Test triage
39
40Monitor [test grid](https://testgrid.k8s.io/sig-cli-master)
41and make sure the tests are passing.
42
43If any tests are failing, debug them and send a fix. Ask for help if you get stuck.
44
45### PR review
46
47Make sure PRs aren't getting stuck without attention. If reviewers routinely don't respond
48to PRs within a few days, we should take those reviewers out of the list.
49
50Look through the PR list with [SIG cli](https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aopen%20label%3Asig%2Fcli)
51
52## New contributor assistance
53
54- Look through issues labeled "for-new-contributors" that are assigned, and make sure they are active.
55 If they haven't had activity in a couple days, ping the assignee and ask if help is needed.
56- Identify issues for new contributors to pick up
57- Figure out a progression for new contributors to become reviewers
58
59## Per-release tasks
60
61### At the start of the dev cycle
62
63- Write planned features for each release
64 - Use the [template](../template.md)
65
66### During code-freeze
67
68- Daily look at issues labeled with [sig/cli in the milestone](https://github.com/kubernetes/kubernetes/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Asig%2Fcli%20milestone%3Av1.9%20) and make sure they are owned and make progress
69 - **Note:** You will need to update the milestone in the link to the current milestone
70
71## Every 3-6 months tasks
72
73### (3 months) Report about SIG cli at the community meeting
74
75TODO: fill this in
76
77### (6 months) Setup a SIG cli face-to-face
78
79TODO: fill this in
View as plain text