Meetings agenda

• Always start the meeting asking how’s everyone doing and if they have any issues
• Does anyone want to write the meeting notes this week?
• Add any major changes (CI, new maintainers, …) to the meeting notes

For the next meeting:

• decision needed for phase 3:
  • which packages to archive (x-maintenance-intent only, or also "flags: deprecated")?
  • should there be a "x-maintained: BOOL" field (for e.g. compiler pre-releases)? -- that'd as well allow private opam-repositories/packages to declare "please don't remove this specific package/version, e.g. by putting x-maintained: true in cohttp.0.2.4.99-4 (maybe best with a comment when and why (and by whom) this was added))
  • what is the default of x-maintenance-intent? There's no documentation about it, being it "[(any)]" or "[(latest)]"? I'm all in for the latter.
  • all the three points above should be settled and then announced.
• call for more opam-repository maintainers?

Typical tasks:

• Are there been any change in the infrastructure? (opam-repo-ci, machines, Github Actions, …)
  • If so make sure they are noted in ocaml/infrastructure and in the README (such as for a change in the tested platforms)
• Are there big issues to discuss first?
• Are there upcoming surprises that we should know about?
  • e.g any upcoming big PRs (dune, JaneStreet packages, Tezos, …)?
• Progress on the documentation for maintainers
• Progress on the documentation for publishers

On quiet weeks:

• revisit long standing issues and PRs, close them if deemed necessary.