Conversation
Add a stub readme with a link to the SIG meeting notes to fix #13.
|
I can't find a link to the meeting itself (hangout): Neither here, nor in the community README, nor in the linked Google calendar. Also I'm not sure we should duplicate the information from the community README. IMHO, only one of the two READMEs should document the specifics and there should be a link to the one that does in the other. On another note, reading "At least 1 approving review is required by reviewers with write access. ", I don't think I have write access: I'm in the OpenTelemetry org, but not in any teams. |
The hangout info is in the calendar event details:
but it sounds like we should switch this to zoom in any case. @carlosalberto do you have a link we can use while we're waiting for the CNCF zoom? I'll update the calendar event to include it.
I agree with that in principle, but I was trying to make it as easy as possible for people just browsing the repo.
I looks like I don't have admin access to give you write access... I'll follow up in person. |
* Add CODEOWNERS * Add CODEOWNERS * rename @draffensperger
Carry the final autoresearch tree as one reviewable change that includes the trace benchmark harness, SDK trace hot-path reductions, empty-context activation fast path, direct BoundedAttributes initialization, and focused validation updates. Experiments: open-telemetry#4, open-telemetry#5, open-telemetry#6, open-telemetry#7, open-telemetry#8, open-telemetry#9, open-telemetry#10, open-telemetry#11, open-telemetry#12, open-telemetry#14, open-telemetry#15, open-telemetry#16, open-telemetry#17, open-telemetry#18, open-telemetry#19 Metric: combined_mean_us 44.469470µs → 22.762846µs (-48.8%)
4 participants
Add a stub readme with a link to the SIG meeting notes to fix #13.