Firedrake meeting 2024 10 09

Date and time 2024-10-09 1600 BST (1500 UTC)

Action Items

1. Pick Chair and Minuter (JB to pick (again))
2. ALL: (ongoing) triage the open issues and confirm if they are indeed still open (and perhaps provide labels)
3. JB: Move pyop3 and TSFC to firedrake and move FInAT to FIAT
4. ALL: do things with SV's branches
5. DH: Email to Andreas to have 2 (+ others!!!) loopy PRs merged TODO: FIND OUT WHICH PRS THESE ARE
6. DH: Get Firedrake a docker open source account (link here)
7. DH: Talk to GregVernon about PR#2116.
8. JB: Enable merge queues (minutes)

Agenda

Present:

Apologies:

JB: Has spec'd some runners

JB: Triage issues in meetings?

There are a lot of open issues with no action and no triage. (Maybe some of them are 4th year/MSc projects...) Should we start triaging during meetings?

JB: Revisiting old PRs

We never off-boarded Rueben's branches and we should probably off-board Nacime's now. (And don't forget Sophia's branches!)

JB/CW/UZ: Move ngsPETSc tests out of Firedrake

JB: Pin PETSc/SLEPc forks to releases rather than arbitrary commits

Fixes are ported to releases and there is 1 minor release per month. I believe this will make installation a bit more stable in the run up to wheel. Thoughts?

Merge PRs

Note that PRs put in this section should either be trivial or already have been reviewed. Discussion-worthy PRs should be separate agenda items.

• JB: #3730 (and corresponding PyOP2 #724)
• JB/KS: Need merging in this order:
  • Firedrake PETSc #22,
  • Firedrake SLEPc #8,
  • Update IO in Firedrake for PETSc changes #3792,
  • Unpin mpi4py #3777,
  • Allow installing with Python 3.13 #3791

Date of next meeting

1600 BST (1500 UTC) 2024-10-16