Set docker image from here

[epruesse]

This isn't honored by bioconda-utils yet - but it feels like the docker image should be set from here. What do you think? @bioconda/core

[johanneskoester]

Yes, absolutely.

[epruesse]

Thinking about this more - why do we have this thing here at all? Shouldn't the configuration for building bioconda packages be all in bioconda-recipes/config.yml?

[dpryan79]

The docker settings could be in bioconda-recipes/config.yml, but the conda and bioconda-utils versions will need to be elsewhere (they could still be in bioconda-recipes/) since they're dealt with before bioconda-utils is installed. The nice thing in general about a separate repository is it facilitates making changes across repos (though we don't make use of that at the moment).

[johanneskoester]

The main reason for setting this up is that this repo can be changed quickly, without a huge test setup and branch restrictions. This was particularly useful at the time we were rapidly developing the build system. An additional benefit is that we can have separate permissions in this repo.

[johanneskoester]

But indeed, one could argue that the docker image stuff should rather go into the config yaml. I think that makes sense.

[epruesse]

We might be able to do something using .github/CODEOWNERS in the recipes repo to protect pieces that are privileged.