You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
I am the diagnostics architect for .NET. I've done a lot of the design work integrating OTel into .NET runtime API and collaborate @reyang on OpenTelemetry.NET.
Most of my work occurs in the .NET repo and behind the scenes on design and coordination. These are a few examples from the OTel side of GH though:
GitHub Username
@noahfalk
Requirements
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
I am the diagnostics architect for .NET. I've done a lot of the design work integrating OTel into .NET runtime API and collaborate @reyang on OpenTelemetry.NET.
Most of my work occurs in the .NET repo and behind the scenes on design and coordination. These are a few examples from the OTel side of GH though:
open-telemetry/opentelemetry-dotnet#4874
open-telemetry/opentelemetry-dotnet#4797
open-telemetry/oteps#123
open-telemetry/opentelemetry-specification#3061 (comment)
open-telemetry/opentelemetry-specification#1753 (review)
The text was updated successfully, but these errors were encountered: