I would do exactly what you have done here if I were the dev of the said app. But with the luxury of being an outsider, a user has expressed an inconvenience and it seems to make sense, then if I were to be the dev of the app here, wouldn't I go and create the ticket in whatever system with a link to this post instead of asking the user of the app to follow the red tape? I know there are places where this is not incentivised so this is a question for your org and not for you.
I see what you're saying and for simple features I agree
However Without the OP creating the ticket there can be no feedback look on the feature.
If i wanted it tested for their usecase, there input and confirmation on if its what they wanted and improvements for the workflow etc..
If I base the whole feature on this comment it could end up only doing half a job. Id rather have that communication loop open!
I tend to agree. As an open source dev myself, I avoid asking folks to create issues, as it puts a burden on the user. I’ve see some highly respected open source leads so this, and I’m
not faulting them, as I think they’re coming from a good place; it may be a difference of opinion on what’s best practice.
Not OP. My take is that if the requester can’t be bothered to create a GH issue, it’s likely that this isn’t really a problem for them. An annoyance possibly but has not risen to “pain” levels.
This is open source software sir, it needs multiple steps to ensure users actually need these features and are willing to use them.