I won't report bugs in paid software/services because it's not my job, I'm not paid for it, I'm user of the service, not free workforce so they can reduce amount of QA staff or skip it completely. Give me a discount and then maybe , just maybe I'll think twice about reporting something. Bugs renders your soft unusable? Fine, there is plenty of competition out there who will do it right.
I just reported a bug on Kobo app and got a thanks and a discount on my next purchase.
I also just got a first response about a bug I reported 5 months ago,
Bugdrop won't work for most users, since they don't real tooltips. 1. I load https://bugdrop.app/ 2. The site days 'try bugdrop' and points to the left bottom corner. 3. I click the bug. Nothing happens. On further inspection, there is sometimes a tooltip that tells me clicking won't work and I need to drag the bug over the part of the UI that failed, but I didn't read that when I first used it and I won't use it a s…
Thank you, Nailer. I'll definitely be doing some tweaking around that part.
Thanks! Pardon if my feedback sounded direct, I wanted it to be impactful. I’m imagining somebody will click on the bug, you will show them very visibly that they need to drag the bug to where they need. When they drop it, they can fill in the form or move it somewhere else.
Most recently, a github user opened a issue on one of my projects and asked "Why should I use this instead of Y". As a developer sharing my code online, I don't even know where to begin answering that. This is typical non-tech spam.
No this is a valid request. If a user wants to use a piece of software to do A and several different pieces of code do that - why should they choose yours. What is your selling point. Especially if they have been using the other product why should they switch to yours?
If I'm writing FOSS and someone asked me that, I'd just reply with ¯\_(ツ)_/¯
I'm not making money from it, so trying to convince some random individual to use it is a waste of my time. Sure, I'll describe the features in the README and possibly include comparisons to other software, but I won't go out of my way to convince a specific rando just because they asked.
The thing I dislike the most about the Linux world is how free software/developers are somehow exempt from any kind of criticism because it is "developed by volunteers."
Criticism is fine, as long as it's constructive and not to the tune of "these volunteers are not volunteering to my satisfaction".
I completely agree with you. It's generally bad form to complain about something that is provided to you free of charge but sometimes even then criticism can be warranted. There is a tendency to immediately swat away any kind of criticism of a project or even just a particular developer's behavior with "how dare you complain about free software!!!".
Love this! That said, wanted to try it on your website, can't report a bug that the bug reporting doesn't work on Safari MacOS... the submit button does not do anything.
Seems it needs some text to submit ( and entering just spaces doesn't count ) - ideally the Submit button shouldn't enable until there is valid text?
I added that when moving the bug around on macOS Safari it highlights weird sections of the web page, which isn't great.
Love this! That said, wanted to try it on your website, can't report a bug that the bug reporting doesn't work on Safari MacOS... the submit button does not do anything.
Seems it needs some text to submit ( and entering just spaces doesn't count ) - ideally the Submit button shouldn't enable until there is valid text?
The submit button is not clickable until there is a text now. Thanks for the suggestion.
I have seen OpenZFS adopt one, but whenever I have seen a bug that has merit closed by the stale bot, it is reopened by a contributor and a not-stale flag is added to prevent it from being automatically closed again. Note that I am a contributor, but I am not one of the ones who is reopening bugs and marking them as not stale. The few times I saw such a bug and would have done it, someone else beat me to it. The stal…
I think that once a bug has been verified and keeps getting likes, it should not be closed. If the user never responded to further questions, then absolutely. What I see however is that maintainers themselves fight the bot removing the label and reopening issues. Over and over. Until they miss the notification.
Once the not-stale label is set, the bot ignores the issue and will not close it again. At least, that is how it works for the OpenZFS bug tracker.
Nice, I hope you are spending 1h per month for each customer as well advising them how the can get the most out of your service and/or improve their integration - otherwise it would seem like you are expecting unpaid work from your customers, which is ridiculous.
I hired a house cleaner. I didn't tell them what to do because figuring that out is their job. They didn't do the things I wanted and they even missed some spots on what they did do. I didn't tell them about that either. It's they're job. So I fired them and switched to another. Repeat. Maybe eventually one of them will figure it out.
You hired a house cleaner, you told him everything he needs to know, he did a good job. Next time unfortunately he arrives with broken vacuum cleaner, he has another one, smaller, less powerful takes him longer to do the job but it's still done, not spotless but it's fine, he is a nice guy, has good attitude.
Another time and he arrives with faulty steam cleaner, again , work is done but takes longer, not ideal outcome. This is happening again and again, he even asks you sometimes to wiggle the cord, push some buttons and try to troubleshot, you know, improving the vendor and stuff.