generator: add support for committees

[nikhita]

Ref: #3298 (comment)

sigs.yaml includes all our community groups except committees. This PR adds support for committees in the generator.

Note: since committees can have private mailing lists, I have added a new field private_mailing_list in the Contacts section. PTAL.

This PR also adds the Steering Committee, the Code of Conduct Committee and the Product Security Committee in sigs.yaml. I'll cc them on the PR for approval for their respective sections once the generator changes get lgtm (but will send an email to the steering ML now to get a general ok for the change).

/assign @spiffxp
generator owner

/sig contributor-experience
/committee steering
/committee conduct
/committee product-security

[nikhita]

Had a couple of questions.

[nikhita]

/hold

[nikhita]

Sent an email to steering ML: https://groups.google.com/a/kubernetes.io/d/topic/steering/iDkt83VedfQ/discussion

[bgrant0607]

Cool! Good idea. Thanks a lot. Probably should be called subgroups.yaml at this point, but I think changing the name would be disruptive.

/approve

[timothysc]

/lgtm
/hold

^ in case anyone else had comments, otherwise cancel the hold after some timeout.

[nikhita]

cc @kubernetes/steering-committee @kubernetes/code-of-conduct-committee @kubernetes/product-security-committee

I'll take #3437 (review) as lgtm from steering but will hold for comments.

CoCC and PSC - can you PTAL at the changes and add lgtm if you are ok with it? Thanks! :)

[philips]

/lgtm

[michelleN]

/lgtm

[carolynvs]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bgrant0607, carolynvs, nikhita, timothysc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [bgrant0607,timothysc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nikhita]

I'll treat @philips's lgtm as approval from PSC (and steering) and @carolynvs's lgtm as approval from CoCC.

Will leave this open until Wednesday and then remove the hold.

[dims]

/lgtm

[spiffxp]

/lgtm

[philips]

/hold cancel

[joelsmith]

@nikhita, Do we need to go update OWNERS and OWNERS_ALIASES files that reference product-security-committee across all the repos? I see the product-security-committee alias instead of committee-product-security in these files:

https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/OWNERS
https://github.com/kubernetes/sig-release/blob/master/OWNERS_ALIASES
https://github.com/kubernetes/org/blob/master/OWNERS_ALIASES
https://github.com/kubernetes/org/blob/master/config/kubernetes/org.yaml
https://github.com/kubernetes/security/blob/master/OWNERS
https://github.com/kubernetes/security/blob/master/OWNERS_ALIASES

I'm happy to make PRs to update those 3 repos with the new name if that's the right thing to do.

[nikhita]

Do we need to go update OWNERS and OWNERS_ALIASES files that reference product-security-committee across all the repos?

TLDR: No, that's not needed. :)

I updated the alias name here because the current format works well with the go template in the generator (which generates the OWNER_ALIASES file from sigs.yaml) i.e. the only way to get the complete committee's name using the fields in sigs.yaml is to use {{.Dir}} and that uses the word committee as a prefix.