REQUEST: New membership for MrAlias

[MrAlias]

GitHub Username

@MrAlias

Organization you are requesting membership in

@open-telemetry

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 Gitter channel
• 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
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

• @jmacd
• @lizthegrey

List of contributions to the OpenTelemetry project

• PRs reviewed / authored
  • Standardize Notation Conventions opentelemetry-specification#308
  • Move export types into trace and metric-specific subdirs opentelemetry-go#289
  • Metric SDK specification OUTLINE opentelemetry-specification#347
  • OTEP 0049: LabelSet specification (to match current Metrics spec) oteps#49
  • Move export types into trace and metric-specific subdirs opentelemetry-go#289
  • [trace] add option.Writer for stdout output opentelemetry-go#404
  • Correct http-stackdriver example module name opentelemetry-go#394
  • Refine CONTRIBUTING.md: make test is included in make precommit opentelemetry-go#416
  • Proposal: Separate Layer for Context Propagation oteps#66
  • Add comments and test for 64-bit field alignment opentelemetry-go#418
• Issues responded to
  • Add unsafe.Alignof() tests for code that depends on 64-bit atomics opentelemetry-go#341
• SIG projects I am involved with
  • https://github.com/open-telemetry/opentelemetry-go

[SergeyKanzhelev]

@jmacd please react. I don't see any problems, just need your ack.

[jmacd]

@MrAlias has my strong support!

[SergeyKanzhelev]

Welcome, @MrAlias!