From 5ba03c2a4619a84d385c6d60abb6d25c31146545 Mon Sep 17 00:00:00 2001 From: Naomi Parsons Date: Mon, 10 Aug 2026 15:39:43 +0100 Subject: [PATCH 1/2] Minutes from July 2026 meeting --- Steering Group/Minutes/20260728.md | 89 ++++++++++++++++++++++++++++++ Steering Group/README.md | 1 + 2 files changed, 90 insertions(+) create mode 100644 Steering Group/Minutes/20260728.md diff --git a/Steering Group/Minutes/20260728.md b/Steering Group/Minutes/20260728.md new file mode 100644 index 0000000..aabf70d --- /dev/null +++ b/Steering Group/Minutes/20260728.md @@ -0,0 +1,89 @@ +# 2026-07-28 Steering Group Meeting + +Present: + - Birgit Hassler (chair) + - Axel Lauer + - Julien Lenhardt + - Ranjini Swaminathan + - Romain Beucher + - Supriyo Ghosh + +Apologies: + - Alistair Sellar + - Bouwe Andela + - Naomi Parsons (minutes, produced from recording) + +## Agenda + +1. **Standing items:** + a) Actions from previous meetings (see below) + b) Updates on funding proposals + c) Updates from (ESMValTool and wider) community discussions + d) Next workshop +1. **AOB** + + +## Meeting notes + +### 1. Standing items + +#### a) Actions from previous meetings + +**Alistair to set-up a kick-off meeting for the ENES-RISe evaluation work package.** +This has been held. + +**Axel (with Ranjini) to set up a meeting for September regarding ESA strategy.** +Initial discussions have been held, some details are still to be decided. + +**Ranjini to arrange a meeting with Doug and Julien to discuss recipe issues.** +Julien has merged the diagnostic into the REF, but more feedback is still needed. + +**Ranjini to check whether Leicester would still be willing to host next in-person workshop.** +This might be a good option for the _following_ year, but it was proposed that **DLR would be a good venue** for the next in-person workshop. + +**Ranjini to continue to share summaries of any future conversations held by the model benchmarking task team regarding observational uncertainty [ongoing].** +There has been nothing relevant to report. + +**Romain to contact Manuel and the tech lead team to see if July is feasible for the next release.** +Romaine, Manuel and Felicity have been working hard on this, the release is very nearly done. + +**Everyone to try to remember who was due to host the next virtual workshop.** + - Action: We still need to think of someone to do this. + - Action: Birgit to liaise with Alistair on dates in the interim. + +**Everyone to consider whether anyone in your organisation might be suitable to join the User Engagement Team [ongoing].** +There have been people attending UET meetings. Also in terms of user engagement, **Birgit has created an ESMValTool LinkedIn account**. It was discussed who else would like admin rights. + + +#### b) Updates on funding proposals + +Brief discussions were held. + + +#### c) Updates from (ESMValTool and wider) community discussions + +1) The REF is a priority and it is possible that some aspects will benefit from extra effort soon. There have a been a few technical difficulties getting it working for some people and guidance was given by Julien about the cloning and forking process. It was noted that issues should be opened on the REF repository when asking for help, rather than on ESMValTool. Some new diagnostics may be added through ESMValTool for use with the REF though, and these pull requests *will* be on the ESMValTool repo. + +2) Tutorials are now going to be written in .rst format, including one upcoming new episode. + +3) Birgit thanked everyone for contributing to the ESMValTool paper. There is still time to contribute. + - Action: Birgit to liaise with Julien to arrange a date for the next steps. + - Action: Everyone to add anything they still want to add. + +4) A clean up of ESMValTool consortium repositories is planned for September, alongside lists of current authors / contributors and other documentation. + + +## Resulting actions + +#### Birgit +- Liaise with Alistair on dates for the hybrid ESMValTool workshop. +- Liaise with Julien about dates for the next steps of the ESMValTool paper. + +#### Everyone +- Think of someone to host the next virtual workshop. +- Add anything that's missing to the ESMValTool paper. + +#### Ongoing: + +- **Ranjini** to continue to share summaries of any future conversations held by the model benchmarking task team regarding observational uncertainty. +- **Everyone** to consider whether anyone in your organisation might be suitable to join the User Engagement Team. diff --git a/Steering Group/README.md b/Steering Group/README.md index d032821..565a66d 100644 --- a/Steering Group/README.md +++ b/Steering Group/README.md @@ -16,3 +16,4 @@ The Steering Group succeeded the [proto-Steering Group](../Steering%20Group/prot - [2026-01-27](Minutes/20260127.md) - [2026-03-31](Minutes/20260331.md) - [2026-05-26](Minutes/20260526.md) + - [2026-07-28](Minutes/20260728.md) From 258222c21649db89b593c3edff24d9fda0db8c57 Mon Sep 17 00:00:00 2001 From: Naomi Parsons Date: Mon, 10 Aug 2026 15:41:41 +0100 Subject: [PATCH 2/2] spacing --- Steering Group/Minutes/20260728.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/Steering Group/Minutes/20260728.md b/Steering Group/Minutes/20260728.md index aabf70d..1a4ac46 100644 --- a/Steering Group/Minutes/20260728.md +++ b/Steering Group/Minutes/20260728.md @@ -20,8 +20,7 @@ Apologies: b) Updates on funding proposals c) Updates from (ESMValTool and wider) community discussions d) Next workshop -1. **AOB** - +2. **AOB** ## Meeting notes @@ -54,12 +53,10 @@ Romaine, Manuel and Felicity have been working hard on this, the release is very **Everyone to consider whether anyone in your organisation might be suitable to join the User Engagement Team [ongoing].** There have been people attending UET meetings. Also in terms of user engagement, **Birgit has created an ESMValTool LinkedIn account**. It was discussed who else would like admin rights. - #### b) Updates on funding proposals Brief discussions were held. - #### c) Updates from (ESMValTool and wider) community discussions 1) The REF is a priority and it is possible that some aspects will benefit from extra effort soon. There have a been a few technical difficulties getting it working for some people and guidance was given by Julien about the cloning and forking process. It was noted that issues should be opened on the REF repository when asking for help, rather than on ESMValTool. Some new diagnostics may be added through ESMValTool for use with the REF though, and these pull requests *will* be on the ESMValTool repo. @@ -72,7 +69,6 @@ Brief discussions were held. 4) A clean up of ESMValTool consortium repositories is planned for September, alongside lists of current authors / contributors and other documentation. - ## Resulting actions #### Birgit