REQUEST: New membership for @maryliag

[maryliag]

GitHub Username

@maryliag

Requirements

• I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/main/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 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

• @pichlermarc
• @pyohannes

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
  • perf(instrumentation-pg): do not split query to determine operation name opentelemetry-js-contrib#2029
  • feat(koa): Use exported strings for attributes opentelemetry-js-contrib#2033
  • refactor(instrumentation-redis): Use exported semconv strings opentelemetry-js-contrib#2075
• PRs authored
  • feat(sdk-node): add HostDetector as default resource detector opentelemetry-js#4566
  • nodejs doc: add clarification to node.js getting started opentelemetry.io#4191
  • chore(resource-detector-alibaba): use exported strings for attributes opentelemetry-js-contrib#2046
  • chore(resource-detector-aws): use exported strings for attributes opentelemetry-js-contrib#2047
  • chore(resource-detector-azure): use exported strings for attributes opentelemetry-js-contrib#2048
  • chore(resource-detector-container): use exported strings for attributes opentelemetry-js-contrib#2049
  • chore(resource-detector-gcp): use exported strings for attributes opentelemetry-js-contrib#2050
  • chore(resource-detector-instana): use exported strings for attributes opentelemetry-js-contrib#2051
  • chore(opentelemetry-instrumentation-pg): use exported strings  opentelemetry-js-contrib#2053
  • chore: update readme for alibaba resource detector opentelemetry-js-contrib#2056
  • docs(resource-detector-azure): update readme for azure resource detector opentelemetry-js-contrib#2057
  • docs(resource-detector-aws): update readme for aws resource detector opentelemetry-js-contrib#2060
  • docs(resource-detector-container): update readme for container resource detector opentelemetry-js-contrib#2061
  • docs(resource-detector-gcp): update readme for gcp resource detector opentelemetry-js-contrib#2062
  • docs(resource-detector-instana): update readme for instana resource detector opentelemetry-js-contrib#2063
  • docs(resource-detector-github): update readme for github resource detector opentelemetry-js-contrib#2064
  • docs(resource-detector-alibaba): add Semantic Conventions to alibaba README opentelemetry-js-contrib#2077
• Issues created/replied to
  • improve resource detector documentation opentelemetry-js-contrib#2055
  • Add service.instance.id for all resource detectors opentelemetry-js-contrib#2065
  • compile and test fail with lerna deprecated attribute opentelemetry-js#4556
  • intrumentation-pg: do not infer query type in span name opentelemetry-js-contrib#2054
• SIG projects I am involved with
  • SDK JS: participating in SIG meeting and being the CODEOWNER of the opentelemetry-instrumentation-pg package

[trentm]

I support, as well. :)

[pichlermarc]

I support 🙂

[pyohannes]

I support! 🙂

[arminru]

Invite sent. Welcome, @maryliag!