Currently, everytime the verify job is run, API calls are made
to github to fetch kubernetes release information since verify
calls generate first.
The issue with this is that everytime this runs in the CI, eventhough
we only generate annual reports when ANNUAL_REPORT env is set, the
API calls are made and if they are rate limited (since we don't use
a token here), the job will fail without a legitamate reason.
Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
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.