coot

@nfrisby has a new proposal which is related, see IntersectMBO/ouroboros-network#4770

We also don't want to prioritise disconnecting from short forks which might win or lose. Churn works on a larger time scale so that we can accommodate shorter diruptions which...

@nfrisby from our perspective this can be closed.

@input-output-hk/perf-team or maybe @karknu might be interested.

We could check the `tested-with` cabal meta data.

I cloned the same repository (with multiple cabal packages) in two different directories using `git clone`, yet there was only one cache entry.

I am more on the @andreabedini side; using `MAY` might be the right compromise for now.

It might actually depend per package. For `network` I'd prefer to have an upper bound, so that whatever the downstream is using is well tested by us (to exclude situation...

Here are some relevant links: * [Philipp Kant (@kantp) at Bobconf 2022](https://youtu.be/uedUGeWN4ZM) * [Armando Santos (@bolt12) at ZuriHac 2022](https://youtu.be/tKIYQgJnGkA)

> Who should be the maintainer? Should it be the individual(s) who currently maintain the package? Or some generic organizational name? I think we should actually put individual's who maintain...