Monthly ESMValtool meeting October

[bouweandela]

The next monthly ESMValTool meeting will be in October. The result of the poll is that it will be on

Thursday October 1 at 16:00 CEST (15:00 BST).

The duration will be one hour. Join the zoom meeting.

@ESMValGroup/esmvaltool-developmentteam

Format and agenda

• We start the meeting by doing a round where everyone gets one minute to introduce themselves and tell what they will be working on in the next month or what they would like help with.
• Using the input from the introduction round, we can decide to talk about specific topics with the entire group or make smaller breakout groups to continue the discussion there.
• If you already know that you would like to bring up a particular topic in the meeting, you can link the GitHub issue to this issue so it's easy to find for other people in the meeting and we can already start discussing there before the meeting. Just create a new GitHub issue if there is no open issue yet.
• GitHub issues are our preferred way to communicate outside the meeting and keep track of work, so any feature requests/action items/etc discussed in the meeting should ideally result in a GitHub issue.

Notes from the previous meeting can be found here: #1801 (comment)

[stefsmeets]

Issue concerning the configuration file: ESMValGroup/ESMValCore#795

[SarahAlidoost]

Issue related to the tutorial discussion ESMValGroup/ESMValTool_Tutorial#152

[bouweandela]

Thanks for attending @ESMValGroup/esmvaltool-developmentteam!

Here is a summary with some news:

• @hb326 Announced that the next workshop will be a 3-day online event, to be held in November 🥳 She will send around an email to ask for input on what the best week would be
• We talked about sharing the reviews among the contributors, so we can speed up the process of reviewing and merging pull requests. @bouweandela will work with @mattiarighi to write some guidance about our review process in https://docs.esmvaltool.org/en/latest/community/index.html. Related to issue Scientific reviewers for pull requests #1818.
• We will release v2.1 this month and this will be organized by @valeriupredoi, more information is available here: https://docs.esmvaltool.org/en/latest/community/release_strategy.html
• Several tutorials have been and will be organized, it would be good to keep track of these, see Data and Statistics on Tutorial sessions ESMValTool_Tutorial#152
• We discussed that it would be good to offer some guidance on how to go from a private diagnostic code, to publishing a paper, to making sure that diagnostic is available in the ESMValTool, see also Provide guidance on using private repositories #1578.
• @stefsmeets Would like feedback on the proposed changes to the configuration file(s) in Rethinking the configuration file ESMValCore#795, so please help him keep up the good work!
• @rswamina reported that good progress was being made by the @ESMValGroup/userengagementteam in collecting requirements for potential future versions of ESMValTool or a related tool

For reference, if you want to ask something to a group of people in the ESMValTool organization, here is the list of the teams. They can be used like this:

• @ESMValGroup/esmvaltool-developmentteam - For everyone involved with the ESMValTool
• @ESMValGroup/userengagementteam - For the user engagement team
• @ESMValGroup/esmvaltool-coreteam - For the core development team

to draw the attention of the team members to an issue or pull request. Team members will get a GitHub notification and an email, just as when tagging indivual persons like e.g. @bouweandela