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.

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

RFE: Send automated notifications to "soon-next-in-line" maintainers #37

Open
rlemosor opened this issue Jun 9, 2022 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@rlemosor
Copy link

rlemosor commented Jun 9, 2022

Several teams would appreciate being notified they were next in line (or soon to be) for maintaining a package whose dependency another team (so far the maintainer) had dropped. This would ideally be achieved via some automated means based on CR data.

For example: team A is the 3rd in the line of succession to maintain a package. Team Z is the current maintainer and has dropped the dependency. Accordingly, team A is now the 2nd in the line of succession for maintaining the package. Team Y is the likely new maintainer as soon as team Z negotiates it (which probably was already underway).

As such, a notification should be sent to team A alerting it of the new status quo, including the possibility of team Y also looking forward to dropping its dependency and thus request team A to own the package. Team A would then be advised to prepare for that possible state, which could encourage a possible elimination of the dependency as well.

@tstellar
Copy link

I have a similar RFE which would be for maintainers to be notified when a package that they don't want is added to the compose. Examples would included alternative runtime libraries like musl, dietlibc, libc++, etc.

@asamalik
Copy link
Collaborator

Let me see what I can do!

@yselkowitz yselkowitz added the enhancement New feature or request label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants