New Merge Policy for an always-green hydra

[timokau]

@kevincox

@timokau

… Many packages have no formal maintainer. We need to decide who is responsible. One approach would be to go down the graph to the nearest maintained dependency(s).

This is a good point to bring up. I think we should probably go the other direction though. I think that if a package is broken we should try contacting the maintainers of the dependents next.

Yes, that’s what I had in mind (though not what I said ). Its still not entirely trivial, since you would have to decide which “reverse maintainers” are responsible (which might be a lot). This is not a blocker though, we would just need to decide on something.

@kevincox

This does raise the question about leaf packages. We can consider doing the following things:

• Don’t let them block and other changes, they quickly get marked as broken.

I think this is the way to go. If somebody cares about the package, they can then adopt it after they notice it has been marked as broken and doesn’t have a maintainer.

@kevincox

This also doesn’t specify how we determine if a maintainer has abandoned a package. It would be nice to have some sort of automation around this as well. However if we see they have been inactive for an extended period of time (1 month?) we can remove them from packages. Worst case they are on an extended offline period and can revert the PR to claim their packages back.

We need more defined guidelines for package inclusion might interest you.