I like option 2. I know we were originally planning on hosting the recipe files on some sort of apache repo in the future (CLIMATE-836), but in hindsight this is probably the best approach. I actually knew of the conda-forge but initially thought the hassle of needing to make a github PR in order to update the packages might be too much of a hinderance when attempting to prepare for new releases. However I really like that the build process itself is automated through CI services which would ultimately make maintaining the packages much easier since the only thing we actually need to maintain is the meta.yaml file for ocw (and any other dependencies not already on the conda-forge). I believe the build is automatically done for both python2 and 3 as well. The initial PRs to upload our recipes will probably take some time but it seems in practice they are very fast about merging PRs for simple updates.
Let me know if you agree, and if so I'd be glad to set this all in motion. I was originally going to make the python3 packages today for my anaconda channel but if this is not urgent, we can automatically defer this until after our recipes are pushed to conda-forge. Let me know your thoughts Lewis John McGibbney.