Assign a maintainer to every recipe

mattiarighi commented 5 years ago

As the number of diagnostics in tool is growing, it is necessary to share the effort of testing the recipes each time significant changes to the core are implemented (like #649, #753, or #755).

To that purpose, it would be convenient to define a maintainer (not necessarily the author), who takes care of running such tests whenever required.

In the recipe, that would look like:

# recipe_perfmetrics_CMIP5.yml
---
documentation:
  description: |
    Recipe for plotting the performance metrics for the CMIP5 datasets,
    including the standard ECVs as in Gleckler et al., and some additional
    variables (like ozone, sea-ice, aerosol...)

  authors:
    - fran_fr
    - righ_ma
    - eyri_ve

  maintainer:
    - righ_ma

Ideally, members of the @ESMValGroup/esmvaltool-coreteam or other very active developers should be chosen as maintainers.

Related to #316.

valeriupredoi commented 5 years ago

hey @mattiarighi this is a very good idea indeed - but there is one major problem that we need to address first: the data availability ie the OBS, obs4mips...: whereas the CMIP5 data is largely available on DKRZ, BADC etc (and we have to chose a maintainer that has access to these types of data repos), the restricted availability of the OBS data makes maintenance impossible for some recipes; so let's reformat all the OBS data first, mirror it on BADC (jasmin) then I will volunteer to maintain a whole bunch of recipes :grin:

mattiarighi commented 5 years ago

The maintainer should be someone who has full access to all data required to run the recipe (s)he is supposed to maintain.

mattiarighi commented 5 years ago

Here is my suggestion, please check the box if you agree to be maintainer for the given recipe, or comment to suggest someone else:

[x] examples/recipe_concatenate_exps.yml (@schlunma)
[ ] examples/recipe_correlation.yml (@bouweandela)
[x] examples/recipe_ncl.yml (@mattiarighi)
[x] examples/recipe_preprocessor_derive_test.yml (@mattiarighi)
[x] examples/recipe_preprocessor_test.yml (@mattiarighi)
[x] examples/recipe_python_object_oriented.yml (@schlunma)
[x] examples/recipe_python.yml (@schlunma)
[ ] examples/recipe_r.yml (@bouweandela)
[ ] examples/recipe_TestMaskThreshold.yml (is this still relevant?)
[x] recipe_autoassess_landsurface_permafrost.yml (@valeriupredoi)
[x] recipe_autoassess_landsurface_snow.yml (@valeriupredoi)
[x] recipe_autoassess_landsurface_soilmoisture.yml (@valeriupredoi)
[x] recipe_autoassess_landsurface_surfrad.yml (@valeriupredoi)
[x] recipe_autoassess_radiation_rms_Amon_all.yml (@valeriupredoi)
[x] recipe_autoassess_radiation_rms_Amon_obs.yml (@valeriupredoi)
[x] recipe_autoassess_radiation_rms_cfMon_all.yml (@valeriupredoi)
[x] recipe_autoassess_stratosphere.yml (@valeriupredoi)
[x] recipe_clouds_bias.yml (@axel-lauer)
[x] recipe_clouds_ipcc.yml (@axel-lauer)
[ ] recipe_cvdp.yml (@bjoernbroetz)
[x] recipe_flato13ipcc.yml (@mattiarighi @axel-lauer)
[x] recipe_lauer13jclim.yml (@axel-lauer)
[x] recipe_my_personal_diagnostic.yml (@valeriupredoi)
[x] recipe_ocean_amoc.yml (@schlunma)
[x] recipe_OceanBGC.yml (@schlunma)
[x] recipe_OceanPhysics.yml (@schlunma)
[x] recipe_OceanQuadMap.yml (@schlunma)
[x] recipe_ocean_scalar_fields.yml (@schlunma)
[x] recipe_perfmetrics_CMIP5.yml (@mattiarighi)
[x] recipe_runoff_et.yml (@mattiarighi)
[x] recipe_SeaIceExtent.yml (@schlunma)
[x] recipe_validation.yml (@valeriupredoi)
[x] recipe_williams09climdyn_CREM.yml (@axel-lauer)

mattiarighi commented 5 years ago

I created the @ESMValGroup/esmvaltool-recipe-maintainers team, to be tagged whenever extensive recipe testing by the maintainers is required.

ESMValGroup / ESMValTool

Assign a maintainer to every recipe #774