To play devil’s advocate here: sometimes there are genuine reasons to try and request support before making an issue. I’m not particularly smart, nor too techy. If something isn’t working, I’m just going to assume I’m an idiot and I’ve messed something up. If I can’t figure out how to make it work, my first post of call will be trying to find a community related to whatever isn’t working, or on smaller projects I might try and reach out to the Dev. Opening an issue always feels like a “hey, your program isn’t doing what it’s meant to do, here’s what’s wrong with it, please fix it” and not “I think I’ve fucked something up, can you please help?”
I suppose it depends what you’re developing though.
Yep, and if it becomes a frequent request, add clarification to the readme / wiki / documentation.
Also, if you push folks towards issues, then they become indexable by search engines! So even if you have a solved problem you can at least find that… Discord? It’s a black hole.
And then get it insta-closed withing 20 minutes saying that “this is a problem with your setup, not the software” even when “my setup” was literally setting up their project using their documentation (docker compose files).
That is how developers treat people with questions that they deem “stupid.”
It turns out their documentation was wrong and some environment variable that they said was optional, was not actually optional and the service would go into a reboot loop without it. I figured that out no thanks to the devs.
To play devil’s advocate here: sometimes there are genuine reasons to try and request support before making an issue. I’m not particularly smart, nor too techy. If something isn’t working, I’m just going to assume I’m an idiot and I’ve messed something up. If I can’t figure out how to make it work, my first post of call will be trying to find a community related to whatever isn’t working, or on smaller projects I might try and reach out to the Dev. Opening an issue always feels like a “hey, your program isn’t doing what it’s meant to do, here’s what’s wrong with it, please fix it” and not “I think I’ve fucked something up, can you please help?”
I suppose it depends what you’re developing though.
You can open an issue and say exactly that
Yep, and if it becomes a frequent request, add clarification to the readme / wiki / documentation.
Also, if you push folks towards issues, then they become indexable by search engines! So even if you have a solved problem you can at least find that… Discord? It’s a black hole.
And then get it insta-closed withing 20 minutes saying that “this is a problem with your setup, not the software” even when “my setup” was literally setting up their project using their documentation (docker compose files).
That is how developers treat people with questions that they deem “stupid.”
It turns out their documentation was wrong and some environment variable that they said was optional, was not actually optional and the service would go into a reboot loop without it. I figured that out no thanks to the devs.
Update your issue with a pull request fixing the documentation.