REQUEST: New membership for cirilla-zmh #2598
Description
GitHub Username
Requirements
- I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md)
- I have enabled 2FA on my GitHub account. See https://github.com/settings/security
- I have subscribed to the Slack channel (use https://slack.cncf.io/ to get an invite)
- I am actively contributing to 1 or more OpenTelemetry subprojects
- I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
- I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
Sponsors
Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.
List of contributions to the OpenTelemetry project
Part of the contribution:
- Proposal: Go Compile Time Instrumentation SIG #2490 (comment) (one of the original project participants)
- fix: Kafka initialization occasionally failed due to concurrent injection of OpenTelemetryMetricsReporter (to #12538) opentelemetry-java-instrumentation#12583 (author)
- Fix panic caused by invalid spanId with b3 propagator opentelemetry-go-contrib#5754 (author)
- Add instrumentation of AWS Bedrock to use gen_ai conventions opentelemetry-java-instrumentation#13355 (reviewer)
- AI Agent Span Semantic Convention semantic-conventions#1657 (reviewer)
- Proposal: Add option to export processing spans in ForceFlush or periodically opentelemetry-specification#373 (proposer)
- What are the Best Practices for Providing Instrumentation for Spring AI. opentelemetry-java-instrumentation#12878 (author)