Hi, On Wed, Apr 14, 2021 at 1:49 AM Lucas Nussbaum <lu...@debian.org> wrote: > > C/ infrastructure that gathers the current status from all instances of > (B) and exposes it per-package, per-maintainer, per-team, etc.
For some data, such as Lintian packaging hints, there may be a powerful combination of AMQP and PostgreSQL. UDD could even provide a RabbitMQ instance as the primary interface for dynamic data collection. Very soon, UDD will collect Lintian's packaging hints (formerly known as tags) in real time. Instead of grouping data as Lintian's run, our runners could already produce rows suitable for the 'lintian' table. (Alternatively, RabbitMQ could take apart the Lintian runs and re-broadcast the data hint by hint on an adjacent channel.) In a super simple design, UDD could collect those hints and true them up with its more stable data sources like packages in the archive. That design would weigh relevance over completeness. UDD data would always be current even though occasionally a packaging hint might be lost. No sweat—the missing hint will be captured next week. The point behind this email is a hope that a conceptual insight might emerge: UDD could become an event collector. The result would be an up-to-date Lintian table that also ties to UDD's static data—which I do not believe it does currently. Kind regards Felix Lechner