Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor link and markdown fixes for community-membership.md #1882

Merged
merged 2 commits into from
Feb 1, 2024
Merged

Minor link and markdown fixes for community-membership.md #1882

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cc64716
Minor link and markdown fixes for community-membership.md
svrnm Jan 19, 2024
39a0594
Merge branch 'main' into link-and-markdown-fixes
trask Feb 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions community-membership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ OpenTelemetry. The OpenTelemetry project is subdivided into subprojects under
Group). Responsibilities for most roles are scoped to these subprojects (repos).

The OpenTelemetry [Governance Committee][] owns this document and process until
delegated. They can be reached via e-mail [email protected].
delegated. They can be reached via e-mail <[email protected]>.

| **Role** | **Responsibilities** | **Requirements** | **Defined by** |
| ---------- | ----------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
Expand Down Expand Up @@ -54,7 +54,7 @@ Defined by: Member of the OpenTelemetry GitHub organization
- [Joined the Slack channel](https://cloud-native.slack.com/archives/CJFCJHG4Q)
- [Get an invite to join CNCF](https://slack.cncf.io/)
- Have read the [contributor
guide](https://github.com/open-telemetry/community/blob/master/CONTRIBUTING.md)
guide](https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md)
- Actively contributing to 1 or more subprojects.
- Sponsored by 2 approvers. Note the following requirements for sponsors:
- Sponsors must have close interactions with the prospective member - e.g.
Expand All @@ -69,7 +69,7 @@ Defined by: Member of the OpenTelemetry GitHub organization
[OpenTelemetry/community](https://github.com/open-telemetry/community) repo
- Ensure your sponsors are `@mentioned` on the issue
- Complete every item on the checklist ([preview the current version of the
template](https://github.com/open-telemetry/community/blob/master/.github/ISSUE_TEMPLATE/membership.md))
template](https://github.com/open-telemetry/community/blob/main/.github/ISSUE_TEMPLATE/membership.md))
- Make sure that the list of contributions included is representative of your
work on the project.
- Have your sponsoring reviewers reply confirmation of sponsorship: `I support`
Expand Down Expand Up @@ -259,7 +259,7 @@ to reach consensus on a technical issue. While it's healthy and appropriate to
make a sincere attempt to understand all points of view and consider the
tradeoffs, it's also healthy to occasionally "disagree and commit."

Within OpenTelemetry, SIG Maintainers are chosen specifically _because_ they
Within OpenTelemetry, SIG Maintainers are chosen specifically *because* they
are domain experts, so we would like to keep as much of the decision-making
authority with the SIG Maintainers rather than immediately "escalating" to the
overall OpenTelemetry-wide Technical Committee. As such, this is
Expand Down