Skip to content

Commit 532eabb

Browse files
authored
Update gc-check-ins to add link to liaison (#2142)
Plus fix a typo
1 parent 8b4839f commit 532eabb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

gc-check-ins.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ As defined in the [charter of the GC](./governance-charter.md#regular-check-ins-
88

99
The check in process is as follows:
1010

11-
* For each SIG a GC member is appointed as a GC liaison. The name of that person will be listed publicly.
12-
* If a GC member was the sponsor for [the formation of the SIG](https://github.com/open-telemetry/community/blob/main/project-management.md), they are by the GC liaison for this SIG.
11+
* For each SIG a GC member is appointed as a GC liaison. The name of that person is listed [here](https://github.com/open-telemetry/community/tree/main?tab=readme-ov-file#special-interest-groups).
12+
* If a GC member was the sponsor for [the formation of the SIG](https://github.com/open-telemetry/community/blob/main/project-management.md), they are by default the GC liaison for this SIG.
1313
* If a GC member is the maintainer themselves, they are by default the GC liaison for this SIG.
1414
* The GC liaison is appointed for the duration of the project lifecycle, or until they do not get reelected into the GC. Outside of that regular duration, a GC liaison can resign by providing a named successor.
1515
* The GC liaison is responsible to check in with the maintainers at least once per month. This can either happen via a (private, non recorded) meeting or through a text-based conversation initiated by the GC liaison.

0 commit comments

Comments
 (0)