initial documentation

[keewis]

Initial skeleton of the documentation. I'm using my (unreleased) sphinx-autosummary-accessors project to format the accessor pages properly, which seems to work just fine.

[keewis]

It seems we need to merge this before we can get PR builds with RTD.

@TomNicholas: The only thing I'd need you to review for now is the use of sphinx-autosummary-accessors. That project is close enough so I can't see much harm in installing it from github.

Also, if you sign up for RTD (using github, if you want), I can add you as a maintainer – you don't have to, there's not much to maintain anyways.

[keewis]

merging. If there's something wrong, we can always open a new PR.

[keewis]

actually, it seems RTD didn't trigger because it didn't receive any authentication for the webhook.

@TomNicholas: what do you think about moving this to a different organization, e.g. xarray-contrib?

[TomNicholas]

Thanks for this!

what do you think about moving this to a different organization, e.g. xarray-contrib?

I'm happy for it to live anywhere. Seeing that xarray-contrib now contains cf-xarray, then it seems like a good place? My only question would be how do the permissions work then? We probably want to give access to people already in xarray-contrib and any of the pint contributors/people contributing here who are interested.

[keewis]

That should be possible. All members of an organization automatically have access (Member), and we can also invite people to maintain a single repository (Collaborator).

[TomNicholas]

Okay, in that case I suggest we ask about it in the xarray community meeting this afternoon.

[TomNicholas]

Okay, in that case I suggest we ask about it in the xarray community meeting this afternoon.

"Yes please!" said Stephan. I'll see if I can do that now.

[TomNicholas]

@keewis I just moved it - access seems to be as expected. I also sent an invite to @jthielen for write access

[jthielen]

@TomNicholas Got it, thanks!