Question: HTTP/2 for Argus & Colossus

Background

We have been discussing various improvements we can make to our infrastructure to make it more performant, and in this context it came up that we currently are using HTTP/1.1, which has much more limited support for simultaneously requesting assets compared to 2.0, which is very important for app screens where you have lots of images for example

To be specific, here is some context from a relevant discussion on the difference between 1.1 and 2

https://stackoverflow.com/questions/36835972/is-the-per-host-connection-limit-raised-with-http-2

Browsers impose a per-domain limit of 6-8 connections when using HTTP/1.1, depending on the browser implementation. This allows at most 6-8 concurrent requests per domain.

With HTTP/2, browsers open only 1 connection per domain. However, thanks to the multiplexing feature of the HTTP/2 protocol, the number of concurrent requests per domain is not limited to 6-8, but it is virtually unlimited.

Question

• How would we introduce HTTP/2.0 in Argus & Colossus?
• What would be a good man hours estimate for an experienced Argus & Colossus dev, and likewise for a newcomer.
• Could a newcomer do this? e.g. from the community.
• @kdembler asks I'm not sure if this will actually be Argus/Colossus and not just the proxy setup, like nginx or caddy.