This file is intended to list all the assets controlled by OpenTelemetry.

• 1Password Teams
  • Team account: https://opentelemetry.1password.com/
  • https://github.com/1Password/1password-teams-open-source#opentelemetry
  • PR: 1Password/for-open-source#364
  • Admin: Alex Boten @codeboten

Link: https://www.nuget.org/organization/OpenTelemetry

• All .NET SIG maintainers are administrators of this organization.
• Organization e-mail ([email protected]) is owned by CNCF.

Link: https://www.myget.org/feed/Packages/opentelemetry

• registered under the service account ([email protected]).
• Individual accounts of .NET SIG maintainers are administrators of the OpenTelemetry feed.
• Admin: manage members.

Link: https://www.npmjs.com/settings/opentelemetry/packages

• Ask any of the following people if you need access
• Owner: Mayur Kale @mayurkale22
• Admin: Daniel Dyla @dyladan
• Member: Bogdan Drutu @bogdandrutu

Used to provide write access to public OpenTelemertry calendar. See docs/how-to-handle-public-calendar.md.

Link: https://groups.google.com/g/opentelemetry-calendar-contributors

• Owners: @open-telemetry/governance-committee
• Members: SIG maintainers and individuals appointed by maintainers

Used to automatically invite members to all OpenTelemetry calendar events, so that time is blocked on their calendars.

Link: https://groups.google.com/g/opentelemetry-calendar

• Owners: @mtwo

• Used to register service accounts and as a NuGet OpenTelemetry organization e-mail. All .NET SIG maintainers are part of this list. Owned by CNCF.
• Admin: add member.

• Used as a service account e-mail for Ruby SIG. All Ruby SIG maintainers @open-telemetry/ruby-maintainers are moderators of this list. Owned by CNCF.
• Moderators: add member.

• Private mailing list for OpenTelemetry Governance Committee.
• All GC members AND CNCF reps (Amye Scavarda Perrin, Chris Aniszczyk, Taylor Waggoner) are on the list and are list moderators.
• Admin: add member.

Link: https://www.youtube.com/channel/UCHZDBZTIfdy94xMjMKz-_MA/videos

• Ask any of the following people if you need to manage the feed:
  • Owners: Amye Scavarda Perrin (CNCF rep), Sergey Kanzhelev
  • Managers: Alolita Sharma, Alan West, Austin Parker, Ben Sigelman, Eddy Nakamura

• Accounts
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
• Owned by: Amye Scavarda Perrin (CNCF rep)
• Admins: @austinlparker, @eddynaka, and @open-telemetry/governance-committee
• Note: while the account passwords are available in the Governance Committee 1Password, logging in from a new IP address will require being a member https://lists.cncf.io/g/cncf-otel-zoomadmins with admin rights so you can see pending (unapproved) messages and retrieve the One-Time Password that is sent when you log in. To join https://lists.cncf.io/g/cncf-otel-zoomadmins and get admin rights, open a CNCF ServiceDesk.

Link: https://splain.io/

• Used to upload Zoom meeting recordings to Youtube
• Owned by: Amye Scavarda Perrin (CNCF rep)

• Used to manage the OpenTelemetry community calendar and Zoom
• Owned by the governance committee

Link: https://project.lfcla.com/#/project/a0941000002wBz4AAE/cla

• Admins: @lizthegrey, @bogdandrutu

• We publish images from CI to Docker hub using https://hub.docker.com/u/otelbot account. The bot is registered using [email protected] email address and Technical Committee members are owners of this account. The Admin for bot security credentials for CI is @tigrannajaryan

This is a community-owned bot account that you can use when automating common GitHub tasks (e.g. release automation tasks).

Important: You do not need to (and should not) give this account any permissions to any OpenTelemetry repository.

Link: @opentelemetrybot

• Admins: @trask and @open-telemetry/governance-committee (GitHub password and associated 2FA for the @opentelemetrybot account are available in the OpenTelemetry Governance 1Password)
• Admins for the associated GitHub organization secret: @open-telemetry/technical-committee

The OpenTelemetry Bot addresses two common issues:

1. Since you can't push directly to main from workflows (due to branch protections), the next best thing is to generate a pull request from the automation and use an account which has signed the CLA as the commit author.

   The OpenTelemetry Bot account has signed the CNCF CLA, and you can assign it as the commit author in your automation:

   git config user.name opentelemetrybot
   git config user.email 107717825 [email protected]
   

   It is recommended to push to branch names that start with opentelemetrybot/, and to add a branch protection rule for opentelemetrybot/**/** with the same setup as documented for dependabot/**/**. Note that branch protection rule ordering matters, so you will need to delete the **/** branch protection rule temporarily, then add the opentelemetrybot/**/** branch protection rule, then add back the **/** branch protection rule.

2. When you use the built-in secrets.GITHUB_TOKEN to generate a pull request from inside of a GitHub Action, workflows will not run on that new pull request without closing and re-opening it manually (this limitation is in place to prevent accidental recursive workflow runs).

   The OpenTelemetry GitHub organization has a GitHub Action secret named OPENTELEMETRYBOT_GITHUB_TOKEN, which is a Personal Access Token for @opentelemetrybot with public_repo scope for the OpenTelemetry Bot that you can use to bypass this limitation.

   The personal access token also has workflow scope which is needed when merging upstream changes of .github/workflow files into opentelemetrybot's forks (these forks are used for automatically opening PRs against external repos).

   Maintainers can open an issue in the community repository to have their repository granted access to this organization secret.