Hydra used to ping maintainers when their packages broke. It doesn’t do that anymore, since there was an incident where it spammed every maintainer.
I would propose to start pinging maintainers once again. There seems to be some kind of consensus that maintainers should have real responsibility and I think fixing breakage is a central part of that responsibility. I have even written a script for myself that scrapes hydra and sends me emails.
For spam mitigation, it may be interesting to look into
- notifying only the maintainer of the actual broken derivation or the first maintainer(s) up the chain if there is none. This way a stdenv failure won’t spam every maintainer.
- notifying only once per week (or other timeframe) per package
I’m not sure if I’m up to hacking hydra myself, so this is mostly intended as a discussion without promise of implementation.