You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calendar invitations to the meeting are sent to the mailing list, join it here.
Format and agenda
Anyone with an interest in ESMValTool is welcome to join and ask questions
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 choose some topics to talk about in more detail.
If you already know that you would like to bring up a particular topic in the meeting, you can mention the GitHub issue on the topic in a comment below. That will make it easy to find for the other people in the meeting and we can already start discussing there before the meeting. Just create a new GitHub issue about your topic 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 are available in #132
Updates @rswamina - will work on tutorial and user engagement @katjaweigel - will work on PRs, including IPCC plot PR. When is next release? Would help with assessing PRs. @valeriupredoi - should be real soon now, maybe this week. @ehogan - two new contributors joining from UKMO - Emma, please add Github handles for Ed (@mo-gill) and Chris (@chrisbillowsMO)? Done! 😊 @ehogan - New CMEW tool to replace AutoAssess - CMEW is a combination of CDDS and ESMValTool for model evaluation and assessment. Going public in 2024. Possible workshop? @headmetal - working on integrating ESMValTool into ACCESS-NRI workflow. see here and an annoucement here @rswamina - alternating meetings at more US- and Australia-friendly times. @ESMValGroup/esmvaltool-developmentteam - is there anyone who'd like to host?
Yes we can do that. @flicj191 should be able to help. Is there a process that has been documented somewhere?
Happy to coordinate with @catherinehardacre.
Happy to help you to arrange this if you would like. I should say that January’s meeting suggested that we could aim for the February call to be on SH-friendly time - if you start a discussion for the February meeting in the Discussions section and create a doodle, I can send it to the ESMValTool mailing list (if that helps). If February doesn’t work for you guys, it can be March!
@paultgriffiths I have started a discussion here #144. I have created a doodle poll with more friendly times for us in the Pacific region.
Let me know what you think and if we can post the invite to the mailing list.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The next online community meeting will be on
December 11th at 2pm UTC / 3pm CET
The duration will be one hour. Join the meeting
Calendar invitations to the meeting are sent to the mailing list, join it here.
Format and agenda
Anyone with an interest in ESMValTool is welcome to join and ask questions
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 choose some topics to talk about in more detail.
If you already know that you would like to bring up a particular topic in the meeting, you can mention the GitHub issue on the topic in a comment below. That will make it easy to find for the other people in the meeting and we can already start discussing there before the meeting. Just create a new GitHub issue about your topic 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 are available in #132
Beta Was this translation helpful? Give feedback.
All reactions