Skip to content

Commit e0d60fd

Browse files
committed
committee-steering: remove sigs.yml link
A sigs.yml link isn't very helpful because the line numbers will keep changing. Instead suggest people link to their subprojects in the SIG README which is generated from the sigs.yml.
1 parent 189d493 commit e0d60fd

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

committee-steering/governance/sig-charter-template.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,14 @@ necessarily all of the internals.
1111

1212
### In scope
1313

14-
Link to SIG section in [sigs.yaml]
15-
1614
#### Code, Binaries and Services
1715

1816
- list of what qualifies a piece of code, binary or service
1917
- as falling into the scope of this SIG
2018
- e.g. *clis for working with Kubernetes APIs*,
2119
- *CI for kubernetes repos*, etc
2220
- **This is NOT** a list of specific code locations,
23-
- or projects those go in [sigs.yaml]
21+
- or projects those go in [SIG Subprojects][sig-subprojects]
2422

2523
#### Cross-cutting and Externally Facing Processes
2624

@@ -62,5 +60,5 @@ Pick one:
6260
2. Federation of Subprojects
6361

6462
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
65-
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454
63+
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-YOURSIG/README.md#subprojects
6664
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md

0 commit comments

Comments
 (0)