Project: OpenTelemetry (Observability and Analysis / Observability)
File: gc_member_onboarding.md

name: GC Member Onboarding about: Onboard a new member of the Governance Committee title: 'GC ONBOARDING: <GH_USERNAME>' labels: area/onboarding assignees: '' <!-- Please remember to change the title of this issue by replacing <GH_USERNAME> with the actual GitHub username of the GC member to be onboarded. --> This issue should be assigned to both an existing member and a newly elected member, and the actions should be performed by both in collaboration. This ensures fluid communication and a successful onboarding into the OpenTelemetry Governance Committee. The issue should be `Closed as completed` by the new member after all steps have been completed. These assumptions ensure that the rest of the guide can be followed successfully. The existing member must: Have the necessary privileges to perform the actions listed below. The new member must: Be familiar with basic OpenTelemetry concepts 2. Have read and agreed to comply with the as per requirements to stand for election. Have an email address, Google account, and GitHub account and is willing to share those details with other GC members. Note: Google account is mainly needed for Google Docs, but one may prefer to use work email or personal email for calendar invites. This section ensures that the new member has access to all systems and has the necessary privileges to perform their role as a member of the GC. 1Password contains credentials for accounts managed by the GC as a group (i.e. not personal items). The existing member must: via email. [ ] After invite is accepted, add them to the `Owners` group as a `Manager`. The current member must: . [ ] Validate they have `Manager` access to `Owners` group, and that the group contains only current GC members. [ ] Validate they have `Full Access` to the `OpenTelemetry Governance` vault. This should be given automatically via the `Owners` group. The main async medium for GC and TC members to communicate is a set of private channels on Slack. The existing member must: [ ] Add new member to the following private channels: - The new member must: account if they do not already have one. Interactions between the OpenTelemetry GC and CNCF are mostly driven via Service Desk tickets. Members can create tickets to discuss access to systems, licensing, funds, marketing, press, etc. The existing member must: [ ] Create a Service Desk ticket to invite new member via email and add it to OpenTelemetry group. The new member must: [ ] Accept invitation to CNCF Service Desk and create an account. (see more information about Service Desk in the ). . Most of the management, enablement, support and documentation work done by GC members happens on GitHub. The existing member must: organization. team. . The following mailing lists ensure that communications reach all necessary members of this

The existing member must: [ ] Invite new member as `Moderator`, ensuring that they have the same privileges as existing members, to the following mailing lists: https://lists.cncf.io/g/cncf-opentelemetry-governance https://lists.cncf.io/g/cncf-otel-zoomadmins [ ] Open CNCF Service Desk ticket to invite new member as `Member` to https://lists.cncf.io/g/cncf-opentelemetry-maintainers The new member must: [ ] Accept invitations to mailing lists above, creating an account on https://lists.cncf.io if necessary, using their preferred email address. OpenTelemetry handles minutes and other ad-hoc documents in Google Drive. The existing member must: [ ] Give new member write access to: The new member must: [ ] Validate they have write access to the documents listed above. All OpenTelemetry public meetings are handled via Google Calendars (see for more details). People in the `opentelemetry-calendar-contributors` Google Group have write access to the OpenTelemetry public calendar. To view and manage members of this group one must use the `admin@opentelemetry.io` account. The existing member must: [ ] Add user as `Owner` of https://groups.google.com/g/opentelemetry-calendar-contributors. The new member must: [ ] Validate they have `Owner` permissions on the group above. Zapier is used to sync meeting recordings from Zoom to a publicly viewable Google spreadsheet (see https://github.com/open-telemetry/community/blob/main/docs/how-meeting-recordings-upload-works.md for more details). The new member must: [ ] Validate they can log in to https://zapier.com with the credentials in 1Password. As per GC charter, all members are expected to attend the following meetings: Governance Committee Meeting (every Thursday 11:00 Pacific Time). Governance/Technical Committee Joint Meeting (every second Thursday of the month, coinciding with the Governance Committee Meeting). The dates and times of these meetings may be discussed and updated after every election cycle to accommodate time zones and scheduling requirements of attendees. The existing member must: [ ] Invite the new member to the meetings using the new members' preferred email address. The following is a list of documents and other media that new members must familiarize themselves with. The new member must go through these media and ask any relevant questions that will aid them in understanding their role as a GC member. The existing member must assist the new member, to the best of their capacity, in finding answers to these questions. : all GC members define, evolve, and defend the Code of Conduct. : to identify items currently in progress. can help get more details if needed. : to understand the fundamentals of how projects are managed by the GC and TC. : to understand current project deliverables and the challenges they aim to solve. : including the individual project boards for each of these, they help understand the current state of the projects listed in the previous item. : for instructions on how to work with calendars, configuring repositories, uploading recordings, etc. As a GC member, it is useful to know that these docs are there when needed. : this free orientation course is designed to provide you with essential background knowledge and practical skills to create an inclusive culture in the open source community. Members of the GC may take this course in support of our community values.