issue_comments: 1110385272
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/pull/5787#issuecomment-1110385272 | https://api.github.com/repos/pydata/xarray/issues/5787 | 1110385272 | IC_kwDOAMm_X85CLyJ4 | 5635139 | 2022-04-27T00:43:05Z | 2022-04-27T08:23:27Z | MEMBER | @pydata/xarray I've refreshed this, since I've been spending time in the issue tracker recently and would like to systematize myself out of the "please add an MVCE" triagooor. I also added a empty binder notebook & link, so people can easily test against a current version of dependencies. I've been using this myself given my M1 has been prickly for some xarray dependencies. Binder is great. I'd be up for making it more friendly, if possible. But I do think we should be strict on issue quality. Some claims: - Most people want to[^1] invest the time to make good issues, and the existing outcomes are mostly a gap of direction & nudging - An unanswered issue (of which we have many, unfortunately) is worse than no issue at all — people feel that there's no prospect of a resolution to their concerns - Bad issues take time away from good issues, and lower maintainers' willingness to spend time in the issue tracker - Friendliness is a virtue. It's difficult to be friendly when managing bad issues, it's very easy when dealing with good issues [^1]: or at least are not adverse to :) This is the current draft:
And the checkboxes:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
994264727 |
