add SIG Security annual report template
This commit is contained in:
Ian Coldwater
parent
6601a65cee
commit
c549c5ab4b
|
|
@ -0,0 +1,78 @@
|
|||
# Kubernetes Community Group Annual Reports Template
|
||||
|
||||
|
||||
# Checklist
|
||||
|
||||
|
||||
|
||||
* [ ] [Read about the process here](https://git.k8s.io/community/committee-steering/governance/annual-reports.md#reporting-process) (https://git.k8s.io/community/committee-steering/governance/annual-reports.md#reporting-process)
|
||||
* [ ] Copy this template into a new document and share with your mailing list/slack channel/meeting on whatever platform (gdocs, hackmd, etc.) that the team prefers.
|
||||
* [ ] Remove sections that are not applicable (example: if you are a working group, delete the special interest group questions)
|
||||
* [ ] Pick graphs from [Devstats to pull supporting data](https://k8s.devstats.cncf.io/d/12/dashboards?orgId=1&refresh=15m) for your responses.
|
||||
* [ ] Schedule a time with your Steering liaison and other Chairs, TLs, and Organizers of your group to check-in on your roles as Chair or Working Group Organizer. If anyone would rather meet 1:1, please have them reach out to the liaison directly, we are happy to. We’d like to talk about: challenges, wins, things you didn’t know before but wish you did, want to continue in the role or help finding a replacement; and lastly any feedback you have for us as a body and how we can help you succeed and feel comfortable in these leadership roles.
|
||||
* [ ] PR this document into your community group directory in kubernetes/community (example: sig-architecture/)
|
||||
* [ ] by March 8th, 2021 - this needs to be this template only; final by April 8th
|
||||
* [ ] titled: annual-report-YEAR.md
|
||||
* [ ] do a call for comments period with your community for final review on your mailing list and slack channels; at least 72 hours
|
||||
* [ ] are there any responses that you’d like to share privately first? [steering-private@kubernetes.io](mailto:steering-private@kubernetes.io) or tag your liaison in for discussion.
|
||||
|
||||
# Special Interest Groups:
|
||||
|
||||
|
||||
(do not copy if you are responding for a working group)
|
||||
|
||||
Instructions for this section:
|
||||
|
||||
|
||||
|
||||
* [ ] each response should have supporting documentation, linked KEPs, graphs, data
|
||||
* [ ] err on the side of being descriptive with your responses. End users and others that read this might not know our upstream acronyms, shorthand, or where to find a reference.
|
||||
|
||||
|
||||
## Operational
|
||||
|
||||
|
||||
|
||||
* How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)?
|
||||
* TBD
|
||||
* Is your README accurate? have a CONTRIBUTING.md file?
|
||||
* TBD
|
||||
* All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sig-list.md)?
|
||||
* TBD
|
||||
* What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?
|
||||
* TBD
|
||||
* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?
|
||||
* TBD
|
||||
* Same question as above but for working groups.
|
||||
* We don’t currently have any working groups.
|
||||
* When was your last monthly community-wide update? (provide link to deck and/or recording)
|
||||
* We are a newer SIG so we have yet to do one
|
||||
|
||||
##
|
||||
Membership
|
||||
|
||||
* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?
|
||||
* Yes
|
||||
* How do you measure membership? By mailing list members, OWNERs, or something else?
|
||||
* TBD
|
||||
* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?
|
||||
* TBD
|
||||
* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?
|
||||
* TBD
|
||||
* What programs do you participate in for new contributors?
|
||||
* TBD
|
||||
* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?
|
||||
* TBD
|
||||
|
||||
##
|
||||
Current initiatives and project health
|
||||
|
||||
* [ ] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members.
|
||||
* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?
|
||||
* TBD
|
||||
* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?
|
||||
* TBD
|
||||
* What areas and/or subprojects does the group need the most help with?
|
||||
* TBD
|
||||
* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?
|
||||
* TBD
|
||||
Loading…
Reference in New Issue