Skip to content

Project Proposal: Browser Phase 1 #2751

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.

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

Merged
merged 22 commits into from
Jun 17, 2025
Merged

Conversation

tedsuo
Copy link
Contributor

@tedsuo tedsuo commented May 15, 2025

OpenTelemetry is rebooting our telemetry efforts for the browser as a sequence of small, highly focused projects. The goal of this first project will be to create instrumentation for the browser runtime and a small initial set of browser libraries, plus the prerequisite API and data modeling work needed to create this instrumentation.

Currently, the proposed meeting time is Thursdays at 8am Pacific. Comment on the doc as to whether this time works for you.

Still needed:

  • SIG Sponsor
  • Approval for meeting time
  • Project Board

@martinkuba
Copy link
Contributor

8am Pacific on Thursdays is in general fine with me 👍

@tedsuo tedsuo requested a review from a team as a code owner May 20, 2025 17:16
@tedsuo
Copy link
Contributor Author

tedsuo commented May 20, 2025

Thanks for the feedback everyone, I've updated the proposal in response.

  • Clarified intentions around the API packages
  • Clarified our goals relating to code management and existing instrumentation
  • Added more members.

I also updated the meeting time to 8:30, with a 30 min meeting being the goal. We are going to experiment with shorter meetings to see if that allows us to move faster and with clearer intentions.

I am OOO until the 27th, I will respond to further feedback at that time. If we have enough approvals, I would like to start the SIG the following week, with June 5th as the kick off meeting.

Copy link
Member

@jpkrohling jpkrohling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm supportive of this but I think it should have the same requirements as any other new project. I'm specifically looking for this, from the project template:

Industry outreach
Who (people, companies) in the industry should be aware of this effort? Was there an attempt to get them onboard? What did they say?

Copy link

@vigneshshanmugam vigneshshanmugam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excited to see the new kickoff process for the Browser SIG! I'm curious if there are any plans for collaboration with the broader web performance community particularly the W3C RUM Community Group (https://www.w3.org/community/rumcg/) and related initiatives. There’s a wealth of expertise in the RUM space within that group, and it could be a great opportunity for shared learning and alignment

@tedsuo tedsuo added the area/project-proposal Submitting a filled out project template label May 28, 2025
@github-project-automation github-project-automation bot moved this to No Status in Projects May 28, 2025
@tedsuo
Copy link
Contributor Author

tedsuo commented Jun 3, 2025

@open-telemetry/technical-committee this project needs a TC sponsor in order to be approved.

I believe that that a guiding sponsor would be ideal, but I know that the TC is short staffed at the moment. An escalating sponsor would potentially be sufficient, as the SIG does not intend to make cross-language spec changes, protocol proposals, or other work outside of browser-specific instrumentation and semantic conventions.

The one area that this SIG overlaps with open spec work is prototyping the EntityProvider, which has an active SIG that we would be collaborating with.

Given that, please advise on how you would like to proceed.

@austinlparker austinlparker added this pull request to the merge queue Jun 17, 2025
Merged via the queue into open-telemetry:main with commit 368b276 Jun 17, 2025
8 checks passed
@github-project-automation github-project-automation bot moved this from No Status to Potential Projects in Projects Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/project-proposal Submitting a filled out project template
Projects
No open projects
Status: Potential Projects
Development

Successfully merging this pull request may close these issues.