html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/1850#issuecomment-360031739,https://api.github.com/repos/pydata/xarray/issues/1850,360031739,MDEyOklzc3VlQ29tbWVudDM2MDAzMTczOQ==,2443309,2018-01-24T06:15:08Z,2018-01-24T06:15:08Z,MEMBER,"My 2-cents. I think we could consider setting up an `xarray-contrib` organization. I don't see how a `xr.contrib` namespace buys us all that much, except for some additional book-keeping in the core xarray package. My thought would be to let individual projects decide 1) if they want to reside inside the xarray-contrib organization, and 2) whether or not to use the accessor api available in xarray now. We could easily add a page to the xarray docs that points to a collection of projects.

*Side note, we don't have to use it but I did grab the [`xarray-contrib` organization](xarray-contrib
) name just in case.*","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,290593053