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

Follow-up suggestions to mission-vision-values.md #1855

Merged
merged 3 commits into from
Jan 8, 2025
+4 −5
Merged

Follow-up suggestions to mission-vision-values.md #1855

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4a28647
Follow-up edits to mission-vision-values.md
trask Jan 11, 2024
f4dea04
Update mission-vision-values.md
trask Jan 7, 2025
f061b2f
Merge branch 'main' into followup
trask Jan 8, 2025
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
9 changes: 4 additions & 5 deletions mission-vision-values.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,14 +144,13 @@ other community members.
It’s no secret that a good number of maintainers of the project are employed by
companies with commercial interests in OpenTelemetry, especially vendors in the
observability space. That said, we expect community members to act in the best
interests of the project. Each member’s priorities can (and should!) align with
those of their employers so that the relationship is beneficial to all parties,
but when acting as a maintainer or contributor to the project, community members
are expected to wear the project’s hat.
interests of the project. Each member’s priorities when acting as a maintainer
or contributor for the project should represent the interests of the project
and its community first before their own interests and other obligations (e.g. employer).

### Disclose potential conflicts of interest

Even within the project, people might have different hats: a Collector
Even within the project, people may have different hats: a Collector
maintainer might be part of the Governance Committee, a JavaScript maintainer
might be part of the Technical Committee, and so on. When the context of your
message can be ambiguous, make it clear which hat you are using. For instance,
Expand Down
Loading