REQUEST: New membership for NathanielRN

[NathanielRN]

GitHub Username

e.g. (at)example_user

Requirements

• I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/master/community-membership.md)
• I have enabled 2FA on my GitHub account. See https://github.com/settings/security
• I have subscribed to the Slack channel (use http://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

• @codeboten
• @lzchen

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

PRs reviewed / authored

• opentelemetry-python

  • Make Ids Generation Customizable
    • Implemented default RandomIdsGenerator + Interface
      • Links
        • Implement IdsGenerator interface for TracerProvider and include default RandomIdsGenerator opentelemetry-python#1153
      • Allow opentelemetry-sdk package to be extended
        • Before this PR, no SDK extensions could exist
      • Links
        • Setup SDK to be a Namespace Package so it can be extended opentelemetry-python#1205
  • Remove non-specification required packages from this repository
    • Removed 30,000+ lines of code in 1 PR :)
    • Seperated repos so that barrier of requirements for new packages would be a lot lower in Contrib repo! This will allow vendors to put their packages in an easy to find place for users and hopefully motivate continuous integration with OTel Python
    • Set up CI workflow that would test change across the repositories using GitHub actions for Continuous Integration
    • Preserved all the Git history in the move
    • Links
      Move non-core instrumentations/exporters/propagators out of main repo opentelemetry-python#1233
      Removes Instrumentation and Exporter Code From Core Repo opentelemetry-python#1258
      Add Contrib Repo Tests workflow on Core PRs opentelemetry-python#1357
  • Add performance tests workflow
    • Fully automated performance tests
    • Fails tests if performance gets too bad
    • Performance tests published in nice intractable graph at https://open-telemetry.github.io/opentelemetry-python/benchmarks/index.html
    • Links
      [PROPOSAL] Add Performance Testing + SDK Span Performance Tests opentelemetry-python#1443
      Use gh-pages to save performance benchmarks results opentelemetry-python#1469
      Fix Benchmarks grouping name opentelemetry-python#1473
      Add benchmarks to every type of package in build workflow opentelemetry-python#1468
  • Make auto instrumentation Ids Generator configurable

• opentelemetry-python-contrib

  • Move non-specification required packages to this repository
    • Same as above
    • Split PRs across many PRs to faciliate reviewing
    • Links
      • Move scripts to match Core at v0.15b0 opentelemetry-python-contrib#126
      • Several PRs from Move instrumentation aiohttp client opentelemetry-python-contrib#49 to [REQUIRED FIRST] Fix lint by making pkg tests folders namespace pkgs opentelemetry-python-contrib#131
  • Make botocore instrumentation comply with specifications
    • Links
      • Fixes and Improvements to botocore instrumentation opentelemetry-python-contrib#150
  • Add performance tests workflow
    • Same as above
    • Links
      • Add performance tests to AWS SDK Extension opentelemetry-python-contrib#243
      • Commit benchmark results to gh-pages branch opentelemetry-python-contrib#250

• opentelemetry-specification

  • Require SDKs to make Ids Generation Customizable
    • Managed to convince the maintainers of the urgency of requiring this change before GA so as to not break compatibility with vendors
    • Links
      • Require the SDK to provide custom ID generation opentelemetry-specification#1006

• Issues responded to

  • See above for issues!

• SIG projects I am involved with

  • https://github.com/open-telemetry/opentelemetry-python

[lzchen]

I support this.

[codeboten]

I support this as well!

[SergeyKanzhelev]

Welcome, @NathanielRN! Invite sent