|
|
|
|
|
by bmitc
1291 days ago
|
|
> > As a user, I can't think of anything more frustrating to spend hours or even days on an issue on an open source project that "welcomes" issues and contributions and then creating a detailed GitHub Issue only for it to be responded with with author's "No" and immediately closed. > The article also discusses that They mention that but they don't really discuss it, and I disagree with the conclusion and advice. GitHub allows disabling issues altogether. Just do that snd save everyone trouble. > What are you supposed to do when it gets to the point where it's just overwhelming you to even look at the issues list? My thoughts are my overall opinion and approach: clear communication. Just update the README, appropriately comment on issues that are closed as a result, and maybe even disable issues. |
|
As if you had the right to be angry at somebody just because they had the audacity to open source code and struggling with maintaining it.
Of course it is simple to say "communicate this clearly" in hindsight. And I kind of did that. Still there are users who expect more from me than I can give.