Dear ESMValTool developers,
During the last monthly ESMValTool meeting (#1801), the idea came up to have another ESMValTool workshop this year. At the moment, this would probably be a remote workshop, similar to the one we had in March 2020. Here, I would like to collect possible topics for our next workshop. Ideas for topics could be (but are not limited to):
ESMValCore
ESMValTool
Please add the topics you would like to address / discuss at our next workshop here:
ESMValCore / ESMValTool:
I would like to propose that we work on getting many of the currently open pull requests merged or closed with everybody happy about the outcome. A lot of work has gone into creating these pull requests, so it would be great if we could finalize it. Having (part of) a week where we all work together, could really help to get these across the finish line!
Here is a list (authors are in no particular order):
@hb326 opened:
@valeriupredoi opened:
@BenMGeo opened:
@jvegasbsc opened:
@zklaus opened:
@ledm opened:
@mwjury opened:
@jvegasbsc and @mwjury @aperezpredictia and @zklaus worked on:
@ValerioLembo opened:
@JaroCamphuijsen, @Peter9192, @ruthlorenz
@schlunma opened:
@bettina-gier opened
@pcosbsc opened:
@koldunovn opened:
@sloosvel opened:
@Peter9192 opened:
@egalytska opened:
@bascrezee opened:
@axel-lauer opened:
@bouweandela opened:
@bjoernbroetz opened:
@LisaBock opened:
Could this be a plan? Does anyone have more ideas? @ESMValGroup/esmvaltool-developmentteam
thank you for putting this together @bouweandela :beer: - it's a very good idea and I will be there (sad it's not near a Bavarian beer garden but such is pandemic life); I've added a couple more PR's under me name in your list - specially the dependency and solving the OSX install and portability are important!
I really like the idea of focusing on getting PRs merged! How do we prioritize? Oldest first?
Another topic could be a brief summary of the work done for the ESMValTool tutorial.
A first draft agenda is now available for comments and feedback: #1866