I agree this overlaps with Next steps for Pangeo / PyOpenSci Collaboration - #3 by TomAugspurger, and more generally with the goals of PyOpenSci. It’d be good to clarify how this tutorial would differ from the goals of something like PyOpenSci’s package guide. The way I’ve been thinking about this is to defer the majority of things to PyOpenSci, and only focus on the things that are (somewhat) unique to pangeo: geospatial things, working well on the cloud, working well with large datasets, etc. That gets more eyes and more maintainers for the general stuff.
I think many of the items in Pangeo package API design - Google Docs are good, general guidelines, but aren’t necessarily unique to pangeo. Some are (“interfacing with xarray”, for example). And so maybe our page “pangeo best practices” can have an overview like it does today, and then go into detail (tutorial style) on some more specific topics like interfacing with xarray?