Re:My boundaries as an open source developer
by smashah on Wednesday March 16, 2022 @11:28PM
(#30707347)
I literally print out a mostly pre-filled github link with most repro context, all they have to do is fill the rest of it in. They still don't do it.
Nowadays a non-templated bug issue is autoclosed.
Re:My boundaries as an open source developer
by danielheath on Thursday March 17, 2022 @04:50AM
(#30708957)
I am 90% of the way to adding "You have been banned from this issue tracker for wasting maintainer time. In future, make some attempt to do your share of the work." to the autoclose.
Re:My boundaries as an open source developer
by jamie-vesoft on Thursday March 17, 2022 @12:07AM
(#30707565)
Autoclosing is a good take.
Re:My boundaries as an open source developer
by account42 on Thursday March 17, 2022 @06:54AM
(#30709683)
Depending on the userbase (e.g. end users from non-OSS ecosystems) and what you want to achieve you might just have to accept they are more used to talking to corporate support agents than filing bugs and learn to work with them. Autoclosing immediately puts the user into an adversarial position - better would be to have an automated reply for incomplete bug reports stating what is missing and that the information is needed for you to help the user to make it clear that filling it in properly is in their best interest as well.
This is the biggest annoyance for me. There's a very clear issue template on my repos. It provides concrete, reasonable requirements (for example, post the actual config that broke!) yet people frequently expect support without filling it out. Even worse, they will make drive-by comments/demands on random PRs instead of opening an issue.
It's kind of amazing how entitled people are.