From 0485e07b851564a4cbb955032b79245fa6bac13a Mon Sep 17 00:00:00 2001 From: Cijo Thomas Date: Thu, 6 Jun 2024 17:34:50 -0700 Subject: [PATCH] Update gc-check-ins to add link to liaison Plus fix a typo --- gc-check-ins.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gc-check-ins.md b/gc-check-ins.md index abcc7ce53..9fabe8b94 100644 --- a/gc-check-ins.md +++ b/gc-check-ins.md @@ -8,8 +8,8 @@ As defined in the [charter of the GC](./governance-charter.md#regular-check-ins- The check in process is as follows: -* For each SIG a GC member is appointed as a GC liaison. The name of that person will be listed publicly. -* 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. +* 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). +* 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. * If a GC member is the maintainer themselves, they are by default the GC liaison for this SIG. * 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. * 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.