| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Signed-off-by: Eddie Zaneski <eddiezane@gmail.com>
|
|
reduce the visual noise, and make the links go to githubs UI
so: https://raw.githubusercontent.com/org/repo/branch/path/to/OWNERS
becomes:
- link text: org/repo/path/to
- link target: https://github.com/org/repo/blob/branch/path/to/ORWNERS
note: this does assume/imply we don't need to model the complexity of
subprojects owning different branches... but, we haven't found a reason
to do so in 5 years, seems a safe assumption
|
|
|
|
|
|
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.
|
|
|
|
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)
|
|
so block descriptions look the same as inline descriptions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
