Software building, CI and packaging

[emiliom]

A listing of resources (ODM2 accounts, etc) being used for ODM2 software continuous integration (on github), packaging, documentation, etc. Emphasis here on resources used across software/repos, not just in one of them.

• Sphinx. See ODM2 Sphinx doc system and docstring conventions documentation #1
• Travis CI: https://travis-ci.org/ODM2 (Filipe)
• AppVeyor? (Filipe)
• Docker: https://hub.docker.com/u/odm2 (Don)
• conda (Filipe)
  • ODM2 conda packages are built on conda-forge only, since early 2018. The transition is described at Move to conda-forge and deprecate ODM2 conda channel conda-recipes-ODM2#82
  • ODM2 conda channel was deprecated once we moved to conda-forge. It's not being maintained. But until we create new conda packages, this channel still provides a convenient listing of ODM2 software we've packaged in conda.
  • ODM2 conda recipes: https://github.com/ODM2/conda-recipes-ODM2. The open issues capture information about creating and maintaining these recipes
  • This presentation from Filipe describes the motivation and workflow for conda packaging for the ODM2 software ecosystem. It's old (April 2016), and its reference to the ODM2 conda channel no longer applies. But the bulk of the presentation is probably still highly relevant and helpful.
• PyPI (I'm listed at least as a maintainer in odm2api and WOFpy)
  • https://pypi.org/project/odm2api/ (note that the last build is VERY old!)
  • https://pypi.org/project/WOFpy/
  • https://pypi.org/project/YODA-Tools/
  • others?
• binder (for jupyter notebooks). I think Filipe created an account for us. It was used/setup for BiG-CZ, see https://github.com/BiG-CZ/notebook_data_demo and https://github.com/BiG-CZ/wshp2017_tutorial_content
• Anything else?

[ocefpaf]

@emiliom just a few comments:

• binder: you don't need an account, just "assemble" the URL and click, one can use this to help with that;
• Travis-CI: it has gh-org rights so it is not in anyone's account, everybody on the ODM2 org can access it;
• Appveyor: unfortunately it is not like Travis-CI b/c it is attached to an e-mail, I believe most of the instance set here are on my e-mail and we should try to move that to another one or maybe we already did that and I forgot. I'll double check and get back to you.