[Proposal] Distribute ownership of packages owned by integrations - #3202
Merged
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
jsoriano
force-pushed
the
integrations-owners
branch
from
April 26, 2022 16:01
1927965 to
4b184c4
Compare
🌐 Coverage report
|
This was referenced Apr 27, 2022
cmacknz
reviewed
Apr 27, 2022
jsoriano
force-pushed
the
integrations-owners
branch
from
April 28, 2022 13:42
3bfdff2 to
98f7851
Compare
cmacknz
reviewed
Apr 28, 2022
|
@jsoriano I don't have the historical context of how this was working earlier but Service integrations look ok in the proposal above. |
cmacknz
approved these changes
May 2, 2022
Contributor
Author
|
@ChrsMark is it possible that you wanted to ping @mlunadia on #3202 (review)? 🙂 |
Contributor
Author
|
Given the generally positive feedback I will merge this if there is no objection by tomorrow. |
Contributor
Author
|
/test |
orestisfl
pushed a commit
to orestisfl/integrations
that referenced
this pull request
May 15, 2026
The integrations team is now distributed along different teams. Several packages are still assigned to the integrations team and responsibilities have diluted. It is not clear what current teams are taking care of them, what teams should review changes and so on. Explicitly distribute the ownership of these packages along the current teams. Changes can be summarized as: * Service integrations owned by @elastic/obs-service-integrations. * System integrations (system, windows, linux) owned by @elastic/elastic-agent-data-plane. * Input integrations (journald, log) owned by @elastic/elastic-agent-data-plane. * nginx_ingress_controller, nats and stan owned by @elastic/obs-cloudnative-monitoring.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The integrations team is now distributed along different teams. Several packages are still assigned to the integrations team and responsibilities have diluted. It is not clear what current teams are taking care of them, what teams should review changes and so on.
The proposal would be to explicitly distribute the ownership of these packages along the current teams.
Proposed changes can be summarized as:
system,windows,linux) owned by @elastic/elastic-agent-data-plane.journald,log) owned by @elastic/elastic-agent-data-plane.nginx_ingress_controllerowned by @elastic/obs-cloudnative-monitoring.Some grey areas:
stan,nats,etcdare services that can be used anywhere, but they are quite related to cloud native, so maybe they should be owned by the cloud native team.