Folks,
We have a new tool called "maintainers" [1] for scanning sigs.yaml in kubernetes/community and point out things that chairs and leads can update (both in sigs.yaml as well as OWNERS files under their own group as well). The idea is that when it's time for annual reports, chairs and leads can take the opportunity to revisit what's in the official records for their groups and update them as necessary. We will be moving this tool under sig-contribex (cross my fingers) and also run it periodically as well.
Right now I need your help to test drive it and help fine tune it. Steps are as follows:
1) ensure kubernetes/community and kubernetes/kubernetes is checked out under $GOPATH/src/
k8s.io3) change directory to "community" directory and run "maintainers audit sig-auth" (or your own sig) and review the output. Sample output for "sig-auth" is at [2]
4) please let me know how it goes either on slack or this email thread or an issue in the repo.
Note that anyone in the community can run this against their own groups they participate in. you can also do "maintainers audit all" to run the report for all sig/wg/ug/committees(s).
Outcomes i'd like to see:
1) ensure sigs.yaml entries are up to date for your group
2) your.chairs/leads/subprojects are well documented
3) ensure the list of owner files in your group are good
thanks,
Dims