Demonstrating this could be done, not going to enforce it for now.
There are also a number of these conventions that could probably
just be auto-generated.
The following formatting is enforced:
- Consistent identation of 2 spaces
- Keys are sorted by order of struct fields
- Lists are sorted by struct-dependent keys
- Comments are stripped
I had hopes of using yaml.Node to preserve comments, but found no
obvious way to marshal from struct to Node, meaning all data
manipulation had to be done against Nodes. This loses us all of the
benefits of using a struct: types, known fields, field order.
Given that there aren't many comments in sigs.yaml to begin with, I'm
erring on the side of dropping support for them.
Demonstrate by adding slack channels for sig-testing subprojects
that already have their own slack channels
Add a GitHub team related to conformance to sig-arch's conformance
definition subproject
GitHub teams as implemented now are very kubernetes-org centric,
I'm not trying to change that here, would suggest a followup
change to allow for the use of github teams in other orgs
(like kubernetes-sigs)
A subproject is a one-to-many mapping of a name to a list of
OWNERS urls. This allows for a subproject to be a single repo (eg:
helm), or a subproject to be a list of multiple subdirectories across
one or more repos (eg: workloads api)
SIG meetings dedicated to a single subproject moved down to subproject
meetings
Automatic merge from submit-queue. .
Update generator to use WHAT variable
Having to set two different variables is confusing. Changed this to look at the `WHAT` envvar and match on a suffix.
Fixes#1126.
cc: @jamiehannaford
Aaron Crickenberger
Nikhita Raghunath
Mike Danese
Christoph Blecker
mahuihuang
Jordan Liggitt
Aaron Crickenberger
Joe Beda
yuexiao-wang
Kubernetes Submit Queue
Matt Farina
shashidharatd
Jamie Hannaford
Vishnu Kannan