GitLab

Add bridged chats

engine: tag peers based on usefulness

* doc: add dirk as the lead maintainer

One of my tasks this quarter is to get a lead maintainer for each repo.

This patch tracks two usefulness metrics: short-term usefulness and long-term
usefulness. Short-term usefulness is sampled frequently and highly weights new
observations. Long-term usefulness is sampled less frequently and highly weights
on long-term trends.

In practice, we do this by keeping two EWMAs. If we see an interaction within
the sampling period, we record the score, otherwise, we record a 0. The
short-term one has a high alpha and is sampled every shortTerm period. The
long-term one has a low alpha and is sampled every longTermRatio*shortTerm
period.

To calculate the final score, we sum the short-term and long-term scores then
adjust it ±25% based on our debt ratio. Peers that have historically been more
useful to us than we are to them get the highest score.

reduce session contention

We're not using these synchronously so we can buffer them a bit to avoid
blocking quite as much.

This also combines all incoming channels into a single one to ensure all
operations are processed in-order. This might be overkill bit it makes reasoning
about this a bit simpler.

Fix: don't ignore received blocks for pending wants

Test: fix flakey session peer manager tests

Refactor: use global pubsub notifier

ci: allow circle to use any orb version

ci: fix badge and orb cache