Project Proposal: Browser Phase 1
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:
- [x] SIG Sponsor
- [ ] Due dates for deliverables
- [x] Approval for meeting time
- [x] Project Board
8am Pacific on Thursdays is in general fine with me 👍
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.
@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.
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?
Thanks @jpkrohling. I updated the proposal to include this section.
I think this is long overdue and would be happy to sponsor. As a JS maintainer I think I am uniquely qualified to help evaluate what can be changed in the existing JS implementation vs what would need to be reimplemented.
Great! I added you as a sponsor. Given that much of this SIG is specifically focused on thorny issues related to differences between the NodeJS and Browser runtime, I agree that a sponsor such as yourself is critical to the success of this project.
I've also added @carlosalberto as an escalating sponsor to fulfill the TC requirement.