issue_comments: 480063323
This data as json
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-480063323 | https://api.github.com/repos/pydata/xarray/issues/1850 | 480063323 | MDEyOklzc3VlQ29tbWVudDQ4MDA2MzMyMw== | 1386642 | 2019-04-04T21:04:37Z | 2019-04-04T21:04:37Z | CONTRIBUTOR | Thanks @rabernat that awesome list looks pretty awesome. However, I would still advocate for a more centralized approach to this problem. For instance, the NCL has a huge library of contributed functions which they distribute along with the code. By now, I am sure that xarray users have basically reimplemented equivalents to all of these functions, but without a centralized home it is still too difficult to find or contribute new codes. For instance, I have a useful wrapper to I would be more than willing to volunteer for such an effort, but I think it needs to involve multiple people. Various individuals have tried to make such repos on their own, but none seem to have reached critical mass. For example, https://github.com/crusaderky/xarray_extras https://github.com/fujiisoup/xr-scipy I think there should be multiple maintainers, so that if one person drops out, there still appears to be activity on the repo. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
290593053 |