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/1447#issuecomment-497113360,https://api.github.com/repos/pydata/xarray/issues/1447,497113360,MDEyOklzc3VlQ29tbWVudDQ5NzExMzM2MA==,26384082,2019-05-29T21:20:14Z,2019-05-29T21:20:14Z,NONE,"In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the `stale` label; otherwise it will be marked as closed automatically
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,234658224
https://github.com/pydata/xarray/issues/1447#issuecomment-309461142,https://api.github.com/repos/pydata/xarray/issues/1447,309461142,MDEyOklzc3VlQ29tbWVudDMwOTQ2MTE0Mg==,6200806,2017-06-19T14:42:35Z,2017-06-19T14:42:35Z,CONTRIBUTOR,"One other thought for `x` rather than `xr`: to me at least, the `x`-prefixed package names just sound cool 😄 ","{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 1, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,234658224
https://github.com/pydata/xarray/issues/1447#issuecomment-309392780,https://api.github.com/repos/pydata/xarray/issues/1447,309392780,MDEyOklzc3VlQ29tbWVudDMwOTM5Mjc4MA==,4160723,2017-06-19T09:51:39Z,2017-06-19T09:51:39Z,MEMBER,"I like the idea of using only the `x` prefix for both the package-import name and the accessor. `xr` doesn't look very nice as a prefix with no underscore. Maybe having the `x` prefix for the accessor as well would also differentiate 3rd-party accessors from xarray-specific accessors like `dt`?

I don't have strong opinions on this either.
  ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,234658224
https://github.com/pydata/xarray/issues/1447#issuecomment-308914123,https://api.github.com/repos/pydata/xarray/issues/1447,308914123,MDEyOklzc3VlQ29tbWVudDMwODkxNDEyMw==,4992424,2017-06-16T02:14:31Z,2017-06-16T02:14:31Z,NONE,"For [xbpch](https://github.com/darothen/xbpch) I followed a similar naming convention based on @rabernat's [xmitgcm](https://github.com/rabernat/xmitgcm). Brewing on the horizon is an xarray-powered toolkit for [GEOS-Chem](http://acmg.seas.harvard.edu/geos/) and while it'll be a stand-alone library, I imagine it'll belong to this confederation of toolkits and provide an accessor or two for computing model grid geometries and related things on-the-fly. I'd also +1 for an `xarray` prefix (so, `xbpch` -> `xarray-bpch` and `xmitgcm` -> `xarray-mitgcm`?)","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,234658224
https://github.com/pydata/xarray/issues/1447#issuecomment-308823486,https://api.github.com/repos/pydata/xarray/issues/1447,308823486,MDEyOklzc3VlQ29tbWVudDMwODgyMzQ4Ng==,2443309,2017-06-15T18:08:54Z,2017-06-15T18:08:54Z,MEMBER,"@benbovy - 

I don't have really strong opinions here but I can tell you what I've done with [xmap](https://github.com/jhamman/xmap). I basically tried to keep it simple and use the same name for all three (package full name, package import name, and the accessor name). My thoughts on how to handle longer names are generally the same, the package-full name could be anything (I'd be okay switching to `xarray-mapping`) and I like the idea of having an identifiable collection of extensions (+1 for `xarray` prefix). My gut reaction to `xrsignal` is to drop the `r` (`xsignal`) and perhaps to use `xsignal` as the accessor name as well. Just some thoughts and like I said, no strong opinions here.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,234658224