Thanks for the link to the talk. This was very interesting.
My perspective is:
- we need to work more on supply chain security (thanks @Khady and OCSF to support my work on conex)
- this only-growing opam-repository leads to lots of resource usage (being it on the clients, for documentation generation, but also for CI systems (revdeps runs) and manual labor (adjusting bounds, investigating failures, …)) – years ago I worked on the archiving policy Requests for comments: how does opam-repository scale? · Issue #23789 · ocaml/opam-repository · GitHub – and it looks like there’s some revision needed (see Opam repository archival, next run (scheduled 2026-01-01) DRAFT: archival process, x-maintenance-run on Dec 9th, scheduled to merge on January 1st 2026 by hannesm · Pull Request #29058 · ocaml/opam-repository · GitHub) – so there’s demand for people jumping in and contributing their time and thoughts – it sounds something time-based and on by default would be a good choice to move forward
- at least the opam-repository maintainer team is usually happy for new volunteers – at the time being there are again 50 open PRs and 140 issues that need triaging – but there are not many incentives to do this work (if you read this as an opam-repository maintainer or former maintainer or future maintainer: thank you so much for doing the work! this is highly appreciated)