Skip to content

Latest commit

 

History

History
129 lines (74 loc) · 6.03 KB

20240227.md

File metadata and controls

129 lines (74 loc) · 6.03 KB

2024-02-27 Proto-steering group meeting

Present:

  • Alistair Sellar
  • Axel Lauer
  • Saskia Loosveldt-Tomas
  • Ranjini Swaminathan
  • Bouwe Andela

Apologies:

  • Birgit Hassler

Agenda

  1. Standing items:
    • Actions from previous meetings
    • Update on funding proposals
    • Updates from (ESMValTool and wider) community discussions
    • Next workshop
    • Consortium agreement

Agenda requests / suggestions

  1. Enacting our policy on inactive GitHub developers (no activity for more than one year): remove inactive people from all core/lead teams on GitHub (Axel to introduce)

Existing backlog of agenda items

  1. Governance checklist: https://sustainers.github.io/governance-readiness/ (Bouwe to introduce)
  2. Axel: Strategy of reclassifying tier 3 datasets to tier 2 for which we have permission from the data providers to do so
  3. Discuss practicalities for the 1 FTE commitment, recognizing that funding is unpredictable and variable in time

Action Items from Last Meeting

  1. Managing connections and dealing with knowledge gaps when personnel move: a. Sub-teams need to discuss and plan towards this. We also need to build capacity.

    Tech-lead team: This has been discussed in the tech lead team, but DLR and BSC were not present so we will have further discussions at the next meeting. User-engagement team: Ranjini feels that tasks are shared across most members of the UET so the knowledge gaps are managed that way. Science lead team: Axel feels this is less of an issue for the science lead team as there are no dedicated tasks for individual people that impact the whole community.

    b. Bouwe to invite partners from ACCESS-NRI to Tech Team meetings.

    They joined the tech lead team.

  2. ESMValTool Strategy document: everyone to provide input to the documents as well.

    Alistair: Strategy has been shared with ESA. Ranjini: Collaboration with obs4MIPs for sharing CMORized data is taking shape. Leave the action open for the next meeting because everyone is busy writing other proposal(s).

  3. Obs data versioning: Technical team to discuss GitHub issue #3452

    Bouwe: left feedback on the issue an pull request. Axel: more technical questions, Alistair suggests having a meeting to discuss this. Axel and Bouwe will have a meeting.

  4. Birgit to propose to Forrest that Ag and Carston are invited to the next fixes meeting with Carlo, et al.

    Postponed to next meeting

  5. Birgit to ask Klaus about SMHI representative on steering group

    Postponed to next meeting

  6. Alistair to contact BSC again to suggest that they propose an interim attendee at proto-Steering group meetings.

    Saskia is back

  7. (New standing action) Note-taker to share hackmd page with group for checking and then publish to https://github.com/ESMValGroup/Community (via a PR)

  8. Alistair to publish notes from previous proto-Steering group meetings

    Alistair will do this soon

Meeting notes

Update on funding proposals

Proposal on collabotion with African researchers in preparation.

Ranjini: AI4PEX project is starting in April (DLR, UREAD, SMHI)

Updates from (ESMValTool and wider) community discussions

Meeting notes are available from the community repository.

Alistair notes that it is important to consider maintainance of infrastructure (such as testing, tutorial, releases, etc) as part of proposals. Bouwe recommends writing releases as deliverables to ensure that they happen. Ranjini suggests writing guidance for writing proposals. This guidance should include any form of technical support (which almost always is necessary) even if ESMValTool personnel are primarily involved in the science diagnostic development. This guidance should include estimated PMs for task categories. Alistair, Ranjini, and Bouwe will prepare a draft.

Tech lead team has trouble finding release managers, release manager for an April release, but no release planned after that.

Next workshops

Axel: preparations for the spring workshop at DLR/hybrid are progressing nicely. It's time to start drafting the agenda. Input appreciated.

Alistair: Met Office offers to organize the next workshop in Autumn. This will be a fully remote workshop. Everyone agrees.

Consortium agreement

Alistair: finding a legal wording that all insitututes can agree with is taking time.

No longer active core-team members

Axel proposes to start enacting our no-activity policy and email people who did not contribute to ESMValTool within the last two years informing them that they will lose their tech/science/user-engagement team membership if there are no signs of life e.g. until the next release.

Bouwe suggests to remove the core team, only keep the science/tech/user-engagement teams, as these are the teams set out in our governance. Science and tech lead teams should have merge rights on ESMValCore and ESMValTool.

Bouwe suggests removing the names and email addresses from the 'esmvaltool' startup message and just replace those by the 'ESMValTool development team' and the user-engagement team email address.

Alistair suggests discussing this on GitHub. Axel will open a discussion item on GitHub to gather feedback from the community.

Actions log resulting from this meeting

  1. Alistair to invite ACCESS-NRI to the proto-steering group
  2. Everyone: ESMValTool Strategy document: everyone to provide input to the document.
  3. Birgit to propose to Forrest that Ag and Carsten are invited to the next fixes meeting with Carlo, et al.
  4. Birgit to ask Klaus about SMHI representative on steering group
  5. Alistair to schedule a meeting to write proposal guidance. (Please see discussion notes above when working on this action item).
  6. Axel: gather input to prepare agenda for spring workshop
  7. Axel: move no-longer active members discussion forward
  8. Alistair to publish notes from previous proto-Steering group meetings