Standup summary: 2025‐07‐17

Progress

PR #435 is the priority. Once this is on, @hiker will resolve any conflicts and unblock the remaining PRs against the vn2.0 milestone.

General agreement to try to get a change to relocate the fab-workspace directory in place and an updated version of the fab command line tool in place before the vn2.0 release.

Problems with testing PR #431 are well understood and issue #441 has been opened to investigate the underlying cause. There may be underlying issues with myp testing and/or type hinting.

Questions

FCM allows disparate branches to merged together at compile time. How should fab handle this? Suggestion is that the user defines a base branch and others are merged on top. The functionality is still required - the current draft Big Fortran working practices are intended to be fairly similar to the existing FCM ones. This probably needs to be clarified with the git WPs group.

Is it possible to delegate approvals for site-specific directories? It would be useful to have a way to allow partner sites to update their own configuration files without requiring a Met Office reviewer. It's not clear whether github supports this.

Actions

• Get working directory change - issue #338 - in place ahead of vn2.0
• Get a rough version of the improved command line utility in place ahead of vn2.0
• Switch meetings to 30 minutes every two weeks
• Cancel the monthly meetings and ensure all attendees are invited to the fortnightly meetings
• Finish curating the issues list
• Create a kanban board showing active work - e.g. planning/ready-to-go, in progress, in review - to allow support routine
• Ask git working practices group about requirements for branch mergers