specifically:
- only sigs+committees can have subprojects
- subprojects need at least one owners entry
- owners should be raw github links
I think the last one could/should change, but:
- I'm about to auto-generate links assuming this format, so I want to
verify I can assume all owners are in this format
- I am not quite sure if we should treat sigs.yaml as public api and
give notice/deprecation for field changes
* Add hugo metadata to SIG list so we can index it on k8s.dev
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Run make generate to generate the proper file
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Move hugo block above the template header
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Update generator/list.tmpl
Co-authored-by: Bob Killen <killen.bob@gmail.com>
* Run make to generate final page
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
Co-authored-by: Bob Killen <killen.bob@gmail.com>
- Add LeadershipGroup#Owners() which returns a sorted and de-duped
list of owners ([]Person) for this LeadershipGroup by combining
Chairs and TechnicalLeads
- The function is used in generator/aliases.tmpl
- Update OWNERS_ALIASES with the new results
If we end up specifying the company for emeritus leads, we could end
up stale information. Moreover, we don't gain any specific value
from company info of emeritus leads.
This commit only contains the generator changes for easier review
The bulleted list of subprojects makes it impossible to link someone to
specific info for a given subproject. Now, instead of linking someone to
sig-testing#subprojects and asking them to scroll, I link them directly
to sig-testing#kind.
While I was at this, I made the main SIG/WG/UG/Committee contact info
format match what is used for subprojects, specifically:
- display the slack channel name
- list github teams as part of contact info instead of in a table
- use - instead of * for bullets
I also removed subproject rendering from WGs, since WGs cannot own code,
and added a link to the governance definition of what a subproject is.
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.
I reviewed PRs over the last year:
- nikhita has done consistent review on almost every change
that touches this code, added a number of substantive
changes herself, and is a contribex tech lead
- pruning grodrigues3 due to lack of activity in the past year
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)
Updated minor issues in the .md file.
- Introduced working groups in the intro (the abbreviation was not introduced previously).
- Removed extra words (that).
- Added a missing comma.
Aaron Crickenberger
Nikhita Raghunath
Bob Killen
Jorge O. Castro
Lubomir I. Ivanov
Aaron Crickenberger
Kubernetes Prow Robot
Daniel Holbach
Roy Lenferink
Mike Danese
shavidissa
Wong Heung Sang
Christoph Blecker
Travis Rhoden
mahuihuang
caleb miles