REQUEST: New membership for pirgeo

[pirgeo]

GitHub Username

@pirgeo

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

• @reyang
• @jsuereth
• @jmacd

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
  Data Classifications for resources and attributes oteps#187
  Add metrics exporters spec files opentelemetry-specification#1837
  Add details for Aggregator in Metrics Spec. opentelemetry-specification#1842
  Add ExponentialHistogram to Metrics data model opentelemetry-specification#1935
  Multiple improvements to the Metrics SDK opentelemetry-specification#1958
  Fill out Summary metric details opentelemetry-specification#2002
  Spec out the metrics exporter and temporality handling opentelemetry-specification#2013
  Move Metrics API spec to Stable opentelemetry-specification#2104
  Move Metrics In-memory/OTLP/Stdout exporters to Feature-freeze opentelemetry-specification#2131
  Metrics SDK - consolidate the aggregation/aggregator term opentelemetry-specification#2153
  Change some would be -> MUST in metrics spec. opentelemetry-specification#2161
  Rename extra dimensions to extra attributes opentelemetry-specification#2162
  Clarify SDK must apply a default aggregation if not specified. opentelemetry-specification#2163
  Use RFC SHOULD NOT wording in histogram aggregation opentelemetry-specification#2164
  Fix a few typos in the datamodel specification opentelemetry-specification#1716
  Add links to all specified creation operations opentelemetry-specification#1815
  Remove metric aggregator Subtract interface opentelemetry-go#2350
  Allow duplicate metric name when meter is different opentelemetry-dotnet#2634
  Add basic docs for Metrics api and sdk opentelemetry-dotnet#2452
  Simple version of Explicit Boundary Histogram. opentelemetry-dotnet#2207
  Refactor for DataValue opentelemetry-dotnet#2093
  Adds metrics API opentelemetry-python#1887
  Adds Aggregation and instruments as part of Metrics SDK opentelemetry-python#2234
  feat: Rename Labels to Attributes opentelemetry-js#2523
  feat(api-metrics): rename metric instruments to match feature-freeze API specification opentelemetry-js#2496
  chore: Update wip metrics references opentelemetry-js#2638
  feat(metrics-sdk): bootstrap aggregation support opentelemetry-js#2634
  feat: add WIP metrics SDK opentelemetry-js#2601
  feat(api-metrics): async instruments spec compliance opentelemetry-js#2569
• Issues responded to
  Inconsistent use of units in semantic conventions opentelemetry-specification#1794
  Set preferred aggregation temporality for the periodic exporting metric reader via environment variable opentelemetry-specification#2065
  Instrument name collisions for different Meters opentelemetry-dotnet#2627
• SIG projects I am involved with
  • SIG Metrics
  • SIG Spec

[reyang]

+1, I support 👍

[jsuereth]

+1, I support

[SergeyKanzhelev]

Welcome, @pirgeo! Invite sent