Xylar Asay-Davis

@mark-petersen, this is a nice solution! @alicebarthel and I chatted about this branch today and came up with an alternative approach to the same block of code. We were thinking...

> The [WCRP-CMIP/CMIP6_CVs](https://github.com/WCRP-CMIP/CMIP6_CVs) license, is a default file license template for use in the netcdf global attribute license field, so isn't the kind of license that is required to create...

@mauzey1, yes, exactly. I have a recipe for doing that already here: https://github.com/xylar/staged-recipes/tree/add_cmip-cmor-tables/recipes/cmip6-cmor-tables > I'm thinking either Apache 2.0, BSD or MIT license would be proper (I'm reading on this...

@matthew-mizielinski, conda-forge can easily accommodate versioning like you suggest. A bot can automatically create a new package each time there is a new version update as long as the recipe...

How important would the CVs be for the tools that would typically use the proposed conda-forge package? It isn't necessarily a problem if that file gets updated infrequently, as long...

Okay, that's good to know. Why not do a release every time the CMIP6_CV.json file gets updated?

There is no way to do a conda-forge package from anything other than a release and it isn't a good idea to overwrite or edit files in a conda environment,...

Okay, I'll leave this to the rest of you to discuss. I know for `e3sm_to_cmip`, the current situation of each user cloning this repo is not working well. I'm happy...

That would be a question for @chengzhuzhang. It sounds like it might be worth including a `conda update` as part of the `e3sm_to_cmip` workflow to make sure the latest version...

@chengzhuzhang, another feasible approach to have `e3sm_to_cmip` clone this GitHub repo into some predefined scratch space (specific to a user, rather than shared) as the first step of running? That...