Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update gc-check-ins to add link to liaison #2142

Merged
merged 1 commit into from
Jun 7, 2024
Merged

Update gc-check-ins to add link to liaison #2142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions gc-check-ins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down