REQUEST: New membership for @PlateauGao
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 1/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
Research direction
Read the community membership guidelines linked in the request and check whether the two named sponsors have replied with “I support.” The request is for organization membership as a prerequisite to becoming a code owner, so completion depends on satisfying the membership process; the payload does not mention implementation files or tests.
Written by the indexing model from the issue text.
Description
GitHub Username
@PlateauGao
Requirements
- I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/main/guides/contributor/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
- @ChrsMark
- @dashpole
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
Applying for OpenTelemetry organization membership as a prerequisite to becoming a code owner for receiver/kubeletstats in opentelemetry-collector-contrib (see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/52265#issuecomment-6689239505).
-
PRs authored (
open-telemetry/opentelemetry-collector-contrib):- https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/50050 —
[receiver/kubeletstats] Expose optional k8s.node.pid.limit and k8s.node.pid.usage - https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/49932 —
[receiver/kubeletstats] Add k8s node filesystem inode metrics - https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/48104 —
Feature/Expose new optional k8s.container.ephemeral_storage.usage metric from kubeletstats receiver - https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/47775 —
Add 3 new optional metrics for system containers (cpu.time, cpu.usage, memory.working_set) to the kubeletstats receiver
- https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/50050 —
-
PRs authored (
open-telemetry/semantic-conventions):- https://github.com/open-telemetry/semantic-conventions/pull/4040 —
Add k8s.node.pid.usage and k8s.node.pid.limit metrics - https://github.com/open-telemetry/semantic-conventions/pull/3891 —
Add system.process.limit metric - https://github.com/open-telemetry/semantic-conventions/pull/3890 —
Add new k8s.node.filesystem semantic conventions - https://github.com/open-telemetry/semantic-conventions/pull/3689 —
Add new metric.k8s.container.ephemeral_storage.usage - https://github.com/open-telemetry/semantic-conventions/pull/3556 —
Add k8s.node.system_container.* metrics
- https://github.com/open-telemetry/semantic-conventions/pull/4040 —
-
Issues / Proposals authored & participated in:
opentelemetry-collector-contrib:- https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/52265 (
receiver/kubeletstatsstability & community support) - https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/48926
- https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/47601
- https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/46703
- https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/52265 (
semantic-conventions/semantic-conventions-genai:- https://github.com/open-telemetry/semantic-conventions/issues/3859
- https://github.com/open-telemetry/semantic-conventions/issues/3858
- https://github.com/open-telemetry/semantic-conventions/issues/3681
- https://github.com/open-telemetry/semantic-conventions/issues/3531
- https://github.com/open-telemetry/semantic-conventions-genai/issues/611
-
SIG projects I am involved with:
- Collector SIG (
receiver/kubeletstats) - Kubernetes Semantic Conventions SIG
- Collector SIG (
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 326
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-telemetry/community
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
open-telemetry/community#3846 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
open-telemetry/community#3844 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
open-telemetry/community#3823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
open-telemetry/community#3821 · 3 comments ·
Maintainers usually reply within 1 day
-
GC OFFBOARDING: mtwoPossibly taken @svrnm claimed this 20 days ago. Openarea/gc-election
open-telemetry/community#3818 · 2 assignees ·
Maintainers usually reply within 1 day
All issues in open-telemetry/community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openedx/xblock-lti-consumer#765 ·
Maintainers usually reply within 1 day