News for hackers. Stuff that matters.
Re:Signal community: Reminder: Please be nice by oefrha on Wednesday January 13, 2021 @01:27AM (#25758884)
I have a slightly different experience. I find aggressive users very easy to ignore. What does drive me mad is that some non-hostile users put zero value on my time.

I’ve painstakingly implemented debug logs and carefully prepared issue templates yet I still get these “does not work (EOM)” (effectively) issues. In the back-and-forth that ensues, sometimes it takes three or four attempts of asking the same question to get what I need, possibly separated by a day each time. Sometimes they’ll eventually realize what they missed was documented in the first place and would have been obvious if they followed the issue template to begin with.

Then there are users expecting me to help with an incomplete, out of context code snippet, or quite the opposite, with their 5k LoC repository, hoping I’d fish out the 50 or 5 lines that are actually relevant on my own.

These users are not outright assholes, so it’s somewhat harder to justify passive-aggressiveness against them. And they may have actual issues locked behind three or four back-and-forths.

(For the record, I got maybe a total of $10 in donations from thousands of hours of FOSS work. Actually a high profile project I worked for did receive sponsorship, but nothing went into my pocket for obvious reasons.)

Re:Signal community: Reminder: Please be nice by asiachick on Wednesday January 13, 2021 @04:22AM (#25759887)
Maybe some one (who's good at writing) could make a closedforreasons.org and you could just put the link in and close the issue anytime someone posts such an issue.

The site could try to be as polite as possible, explaining that your time isn't free. You're not there to cater to them or give them free labor. You are interested in bug reports but only if they contain a minimal complete repo and explain what minimal means, what complete means, and what repo means. There could be common links like closedforreasons.org/mcve closedforreasons.org/rude closedforreasons.org/nofreelabor closedforreasons.org/notyouremployee closedforreasons.org/outofscope closedforreasons.org/askingfortutorial etc...

It will certainly piss some people off but maybe after a hopefully short while it would be seen as a gentle nudge by everyone that's been through it.

Re:Signal community: Reminder: Please be nice by andrewaylett on Wednesday January 13, 2021 @09:19AM (#25762206)
Your wish is my command: https://closedbecause.xyz/

Source here: https://github.com/andrewaylett/closedbecause.xyz, suggestions for reasons welcome, PRs even more welcome.

Re:Signal community: Reminder: Please be nice by dastx on Wednesday January 13, 2021 @10:19AM (#25763018)
How can you have a closed because site without being able to write a custom reason, with custom parameters, and on top of that, it doesn't make my coffee. Ridiculous.

(Joke obvs. Sorry, couldn't resist.)

Re:Signal community: Reminder: Please be nice by cyberfart on Wednesday January 13, 2021 @02:36PM (#25766937)
A relevant post, "Open Source is Not About You" by Rich Hickey.

https://gist.github.com/richhickey/1563cddea1002958f96e7ba95...

Re:Signal community: Reminder: Please be nice by _underfl0w_ on Wednesday January 13, 2021 @10:01AM (#25762768)
It would be neatly recursive if someone opened an incomplete/nonsense PR on the repo for this site, prompting a link to the site itself.
Re:Signal community: Reminder: Please be nice by dumpsterdiver on Wednesday January 13, 2021 @08:32PM (#25770608)
Appropriate use of an xyz domain IMO, it's catchy. Bravo.
Re:Signal community: Reminder: Please be nice by worik on Wednesday January 13, 2021 @02:13PM (#25766656)
Well done!!
Re:Signal community: Reminder: Please be nice by blargpls on Wednesday January 13, 2021 @06:26AM (#25760736)
There's something similar to what you're proposing: https://idownvotedbecau.se/. It's tailored to Stack Overflow and the Stack Exchange network, but a lot of it overlaps with your proposal.
Re:Signal community: Reminder: Please be nice by andrew_ on Wednesday January 13, 2021 @06:54AM (#25760943)
Having robust reply templates is pretty key. If the templates explain why a thing was closed, there isn't much for the user to refute. They can always fume, but fuming on a closed ticket is like screaming into the void. Leveraging bots helps as well. e.g. if an issue template isn't followed, removed, or omits key required info the issue is closed by a bot and a reply is dropped letting the user know that their attempt to circumvent the requirements means they get no support.
Re:Signal community: Reminder: Please be nice by gitgud on Wednesday January 13, 2021 @09:00AM (#25762018)
Bots are good in moderation, but in some cases bots can annoy everyone involved...

For example; the Angular repository has a "stale bot", which closes and locks the issue after a certain amount of time of inactivity.

This sounds great on the surface, however it's insane in practice. The users constantly need to recreate duplicate issues, as the original issue is locked. Most of the duplicates are not linked, so maintainers can't determine which issues are duplicates. And it also increases the friction of users notifying that the issue is still occurring.

Basically the result of "stale bots" is more duplicate issues and less engagement on old issues (as they're locked)

Moral of the story, use bots in moderation

Re:Signal community: Reminder: Please be nice by andrew_ on Wednesday January 13, 2021 @09:22AM (#25762238)
I manage a couple of high volume projects on a few open source initiatives. Stalebot is a sanity saver. Users are always welcome to trigger the bot to reopen. I won't presume your experience on open source projects of a big size, but when you're dealing with dozens of new issues daily, and have hundreds of issues that go back five years with no activity, the stalebot saves the day.

That speaks to another issue of open source - it's more common than not for a user to report an issue with no intention of following up, nor helping to triage (let alone contributing). Drive-by issues are noise and take precious time away from maintainers. There again, stalebot steps in to help. YMMV but my personal experience is that we don't get too many reopens, and we don't get too many duplicates from closed issues.

Re:Signal community: Reminder: Please be nice by remram on Wednesday January 13, 2021 @09:23PM (#25771033)
Only the original reporter gets to bump/reopen. Which they are sure to give up doing after a few iterations.

In addition, it's just plain rude. If you don't have time to fix it, that's valid, but what makes you presume you community has time to deal with constant bot reminders on order to keep the bug open?

You don't have to deal with it, that's fine, leave it there. Or get some more maintainers on board to help with triage.

Re:Signal community: Reminder: Please be nice by andrew_ on Wednesday January 13, 2021 @11:01PM (#25771795)
This comment reflects what's wrong with open source. It's bitter, entitled, and devalues the time and effort of project maintainers.
Re:Signal community: Reminder: Please be nice by account42 on Thursday January 14, 2021 @03:38AM (#25773750)
I think you are also being a bit entitled here. Bug reports absolutely do take effort to file, especially good ones. Automatically closing bugs for inactivity shows that you don't value that effort. Personally, that would mean every future bug report to your project would receive minimal effort. If you don't like bug reports then you should not have a bug tracker at all. If you do have a bug tracker, try seeing it as a mutually beneficial exchange that is not free for either side.
Re:Signal community: Reminder: Please be nice by andrew_ on Thursday January 14, 2021 @10:16AM (#25777263)
Unless someone is contributing, it's not at all a mutually beneficial exchange. If someone reports a bug that affects only them (e.g. edge cases) then that ticket benefits only them. The -vast majority- of tickets files on large projects are for the benefit of single users. The tertiary benefit to users that might come along later with that same edge case or edge feature need are moot. It doesn't benefit the maintainers. If someone reports a bug and leaves out critical info because "they know better" than the maintainers, and that causes additional work for the maintainers that creates burden. Maintainers are already giving their time freely to produce something for users to use freely. The scales are always tipped in maintainers' favor.

https://liberamanifesto.com/

We owe you nothing. You owe us nothing.

Play by the rules set in the project, fork, or don't play. The choice is yours.

Re:Signal community: Reminder: Please be nice by remram on Thursday January 14, 2021 @01:46PM (#25780390)
Exactly. I'm not asking you anything here, I understand you don't have time to fix it, but leave it up so another contributor can find it. I'm literally asking you to not do something instead of doing something (closing).
Re:Signal community: Reminder: Please be nice by kelnos on Wednesday January 13, 2021 @11:44PM (#25772135)
I don't really like something like stalebot from both the maintainer and user side. As a maintainer, I don't want a legitimate issue to get closed just because it's not (yet?) a high priority for me, and I let it go for a while. And as a user, if I've provided sufficient information to reproduce the issue, and the issue is valid, it's really demotivating to have that issue closed by a bot.
Re:Signal community: Reminder: Please be nice by remram on Thursday January 14, 2021 @01:51PM (#25780484)
I think stalebot works so long as maintainers commit to marking issues as "confirmed" after a while, or if enough people +1. However too often that is not the case.

Multiple times have I filed an issue, that collects many people's "me too" and workarounds for over a year. And every month, stalebot comes and mentions everybody, so that I have to go and type in that stalebot command.

Until one day I give up, because I don't want to get those notifications anymore, or because I move to a more active project. The issue gets closed even though multiple people are affected, and all they can do is open a new one, link to the workarounds somehow, and take over the duty of fighting the bot.

Why make everyone do this? You say you don't owe me anything, but that's different from taking active step to hurt your community.

(and by you I mean stalebot users like andrew_)

Re:Signal community: Reminder: Please be nice by switchbak on Wednesday January 13, 2021 @10:29AM (#25763165)
Drive by issues are noise? So if I say "library X fails with this input" and don't follow up/triage/commit code, then this is a waste of time?

I strongly disagree. Follow-up and collaboration are great, but someone taking the time to write a decent bug report is also valuable.

Re:Signal community: Reminder: Please be nice by detaro on Wednesday January 13, 2021 @10:33AM (#25763210)
Presumably if it's a "decent bug report", needing additional feedback etc is less likely, and I assume GP is more talking about bug reports that are not really usable without further information. (Although even if you are careful at providing information, you can easily hit cases where more information is needed)
Re:Signal community: Reminder: Please be nice by andrew_ on Wednesday January 13, 2021 @11:04PM (#25771830)
This presumes that all opened issues are decent. It also presumes that the author of the issue responds to feedback. What I would quantify as drive-by issues include poorly written, lacking information, or providing information that results in a follow up reply from other users or maintainers with a fix or ask for more information that goes unanswered.

"library X fails with this input" is great, unless the input is wrong, the usage is wrong, or the environment is awry - and those issues are useless if the author doesn't reply to follow up replies.

Re:Signal community: Reminder: Please be nice by account42 on Thursday January 14, 2021 @03:41AM (#25773776)
Closing bugs because they don't contain enough info and the reporter is not responsive to providing the required info is commpletely fine. Closing based on inactivity alone is just rude.

> "library X fails with this input" is great, unless the input is wrong, the usage is wrong, or the environment is awry - and those issues are useless if the author doesn't reply to follow up replies.

They could still be a hint that the documentation or reported error could be clearer.

Re:Signal community: Reminder: Please be nice by andrew_ on Thursday January 14, 2021 @10:08AM (#25777148)
We disagree. My experience with several extremely large projects has yielded the judgement that closing tickets which are years old without activity is prudent, as is setting a reasonable time frame in which an issue is too stale.
Re:Signal community: Reminder: Please be nice by necrotic_comp on Wednesday January 13, 2021 @07:43AM (#25761295)
I quite like the idea of using bots - that way there's no human making a decision, and since we've already internalized bots as cold and unfeeling, no one's feelings are hurt.

IIRC, Gentoo does this, and my first patch was rejected multiple times. But because it was a bot that responded,I just felt like I had made a mistake, whereas with a human in the mix I probably would've asked a bunch of a questions and wasted her time and mine.

Re:Signal community: Reminder: Please be nice by mlindner on Wednesday January 13, 2021 @06:42PM (#25769606)
I'm going to disagree as someone who reports issues to open source. Often the templates request info I know as an experienced user of the software to be completely irrelevant to the issue, and if provided would only confuse the cause of the problem. Templates often assume a stupidity level of issue submitters. If there is a github template, I'll usually heavily modify the template and delete sections, which then gets flagged by a bot if such a bot exists. This only slows down the process of getting something fixed, not speed it up.
Re:Signal community: Reminder: Please be nice by andrew_ on Wednesday January 13, 2021 @11:07PM (#25771850)
Frankly; it's not up to you to determine what info maintainers need - thinking otherwise is an entirely entitled point of view. That's why the project members and maintainers ask for what they need to triage not just your issue, but all issues from a wide variety of users on any variety of platforms.

If you can't take a few extra seconds to enter information in a template, why on earth should maintainers donate their time to you to triage what you're reporting?

Re:Signal community: Reminder: Please be nice by tga_d on Thursday January 14, 2021 @01:39AM (#25772947)
While I agree with the point you're making, I'd like to point out the tone of your wording. It's not cruel or anything, but there are some pretty easy changes to it that could have made it an explanation instead of an argument.

As for the original point: I suspect every developer has encountered a bug in their code that couldn't possibly be caused by something, but ultimately was. Getting all the information requested up front in a regularly structured way, even when we think it's irrelevant, can make tracking these problems much easier.

Re:Signal community: Reminder: Please be nice by roryokane on Wednesday January 13, 2021 @07:01PM (#25769795)
A compromise could be to have a bot to check the issue template, but to make the bot aware of users' contribution histories. The bot would skip checking the format of someone's issue if, for example, they had already reported at least three bugs or gotten one patch merged.
Re:Signal community: Reminder: Please be nice by dmckeon on Wednesday January 13, 2021 @12:46PM (#25765459)
Came across this explainer site the other day: Short, Self Contained, Correct (Compilable), Example http://sscce.org/
Re:Signal community: Reminder: Please be nice by emilecantin on Wednesday January 13, 2021 @10:00AM (#25762756)
Great idea! I was looking for a side-project I could do in a week or so, so I just bought the domain and I'll build it.
Re:Signal community: Reminder: Please be nice by exikyut on Wednesday January 13, 2021 @05:59AM (#25760518)
This idea seems really interesting/promising. Here are three considerations I've thought of while thinking about how it might be implemented:

1. Many years ago (I only saw this here and there myself) a particular essay on Asking Smart Questions that would sometimes be linked whenever a suboptimal(ly worded) query was posted on a mailinglist or newsgroup or forum. http://www.catb.org/~esr/faqs/smart-questions.html

It's quite the wall of text, because it's thorough. This produces an unfortunate effect: everyone who reads the article, digests it, and applies what it says "disappears" into the bigger picture of people who ask good questions; while people who don't have the time to read an issue template properly have their eyes glaze over and they add the URL to their mental list of "evil entitled webpages that demand too much of my time" and go on filling the internet with noise.

TL;DR, a webpage this big: --> <-- works for just about everyone, but the "TLDR dropoff" is disillusioningly exponential beyond 0 bytes.

2. Taking as an example the common use case of people at the stage of learning about software development, there's a specific point in that learning process where everything seems possible... too possible. Of course it's possible to merge the Linux and Windows kernels. Of course it's possible to "just rewrite the codebase" to make the two mutually incompatibly designed components work together. One place that comes to mind that this sort of thing can concentrate is in game modding communities. It's not uncommon for there to be one or two "dev" type positions that are basically hacking it but have enough figured out to be competent, with a bunch of other users surrounding them that have no idea what they're doing and asking for the impossible. The net result is 500+ issues or forum posts, with only one or two ((ahem, achievable)) items slowly being acknowledged worked on, and the rest basically ignored for the sake of efficiency. The people that all have no idea what they're doing collectively think each others' ideas are great and if only the devs would actually listen to them the project might actually get somewhere.

TL;DR, accessibility and intuitivity are hard.

3. There are thousands of devs out there in situations where they simply don't have time to answer every possible question. They may honestly have a massive workload and are doing triage on top of that, they might be maintaining a minimum-viable free user support forum for a commercial product, they might be a time-poor OSS contributor, they may have laziness issues :P (independent of any other points here), they may have communication issues, ...

Again, there are thousands of devs out there who would be looking for a TLDR for their circumstance.

A large proportion of those that choose to use a template-as-a-service website to optimize their time can only pick from the best possible option from the available choices, even where the choices that are available aren't an exact fit, because this is a common pattern when optimizing.

Considering all of the above together, *you are going* to have circumstances where angry users will feel snubbed by suboptimally-chosen messages, and the challenge with a site like this would be to figure out how to reduce the chances that...

- almost-but-not-100% templates are chosen by time-poor devs for lack of better options, which will lead to poor reception of the site by end users

- the message is too long or complicated for the user to read and act on (can the user read English easily? Do they have intellectual issues (autism and ADD are particularly common, and drastically underaddressed) that make it hard for them to break work down into chunks and focus on it? Does the text of the template help the user to feel supported so they can calm down and focus on the work they must now do? Etc)

A couple of other points:

- Analytics would definitely be a good idea, as would actually looking through the supplied referers (that you can actually open).

- An "I didn't find anything appropriate for [URL]" option with a free-text "description" box would deliver a lot of helpful signal to further refine the options available

- Editing everything on GitHub or similar would make it straightforward for people to simply just contribute direct improvements (the "nothing appropriate" submission box would not be public)

Re:Signal community: Reminder: Please be nice by geoduck14 on Wednesday January 13, 2021 @09:00AM (#25762014)
.
Re:Signal community: Reminder: Please be nice by YorickPeterse on Wednesday January 13, 2021 @05:17AM (#25760234)
Over the years I've learned there's a class of users that simply don't read.

Example: for GitLab we stopped using the repository that used to host the code for GitLab CE. All issues were closed, and when you create a new issue there's a template active that basically says "Don't create issues here". In spite of that, people still create issues here, and in some cases don't even bother changing that template.

Re:Signal community: Reminder: Please be nice by smeej on Wednesday January 13, 2021 @06:45AM (#25760874)
I've spent more than a decade in customer/user-facing roles, and that class of users is actually "almost all of them."

But it's worse than that. Most people do not have the reading fluency to read more than a few words in a sentence without getting frustrated and confused. If your work peers and social groups consist of the 3-5% of people who aren't in that category, it can be easy to forget that.

Any time you can make something's function clear with one or two words and design, opt for that over explanation.

Re:Signal community: Reminder: Please be nice by dumpsterdiver on Wednesday January 13, 2021 @08:48PM (#25770751)
Then you get people like me who prefer to read words, but are utterly baffled by the user experience on modern social platforms... like, how do I log out? Oh, the smiley button, duh.
Re:Signal community: Reminder: Please be nice by BurningFrog on Wednesday January 13, 2021 @09:40AM (#25762488)
And this is why UI/UX experts are so valuable in software projects!
Re:Signal community: Reminder: Please be nice by crznp on Wednesday January 13, 2021 @12:46PM (#25765465)
If "almost everyone" fails some expectation, is the problem with the people or the expectation?

The average user might not be super invested in the application, they just know that something doesn't work, which is frustrating. If their only outlet for that is a bug report, the developers get overwhelmed with bad bug reports and users get the expectation that the developer is going to fix all their problems for them.

If the outlet is a feedback form instead, maybe the user can feel listened to in a small way and move on. The developer doesn't have to sift through a bunch of issues, they can just follow up if there seem to be any hot-spots that are causing a lot of frustration.

Re:Signal community: Reminder: Please be nice by kelnos on Thursday January 14, 2021 @02:01AM (#25773092)
Exactly; the problem here is that there's a repository that allows issues to be filed, when the owners don't want issues reported there. Issues should just be turned off on that repository (and if you can't do that, I'd consider that a big missing feature).

You need to guide people to do the right thing based on the interface itself; people overwhelmingly don't read instructions.

Re:Signal community: Reminder: Please be nice by smeej on Wednesday January 13, 2021 @08:40PM (#25770685)
That's my point. Things have to be designed with the understanding that "people who won't read the instructions" are the rule, not the exception. That has to be the expectation if anything is ever going to improve.

Unless you know you're dealing with a very specific subset of the general population who loves reading, design around things that don't need to be read.

Re:Signal community: Reminder: Please be nice by Arnavion on Wednesday January 13, 2021 @07:12PM (#25769910)
I don't see how replacing "sift through a bunch of issues" with "sift through a bunch of feedback forms" makes the developer's job any easier.
Re:Signal community: Reminder: Please be nice by enriquto on Wednesday January 13, 2021 @05:39AM (#25760362)
This sounds like an UI problem. Why can't the system just disable the issue creation button?
Re:Signal community: Reminder: Please be nice by kubanczyk on Wednesday January 13, 2021 @09:05AM (#25762058)
Yeah. It's literally one checkbox lacking on GitHub.

So (1) Scrape the old, closed issues to a static website, link it from README.md. (2) Disable Issues in GitHub's repo settings.

Part 1 is somewhat complicated, because issue-to-issue linking.

Re:Signal community: Reminder: Please be nice by areactnativedev on Wednesday January 13, 2021 @09:00AM (#25762023)
Same feeling, the fact that one has to assume people will not take 5s to read and understand a message has nothing to do with the project being open-source & free or not.

I feel that it must be even more annoying when you're offering free great work to these people. But I believe it to be a fact about all users (I include myself, though I'm trying to work on it).

Re:Signal community: Reminder: Please be nice by opportune on Wednesday January 13, 2021 @02:30AM (#25759255)
I understand when writing paid software with support expectations/contracts, sometimes you have to engage with the teeth-pulling exercise that is “does not work”. But why do you in FOSS? Can’t you just close the ticket and say “not descriptive enough” and move on?
Re:Signal community: Reminder: Please be nice by hombre_fatal on Wednesday January 13, 2021 @03:34AM (#25759615)
To do that, you need a healthy brutal self-respecting trait that I think most of us admire.

The rest of us feel bad doing that, especially towards someone trying to use something we built ourselves that holds some measure of our own pride or even self-worth, it feels closer to obligation. So we waste our time trying to help the characters that deserve our help the least, and we learn to develop a resentful version of that trait over a period of decades.

Re:Signal community: Reminder: Please be nice by pbhjpbhj on Wednesday January 13, 2021 @05:36AM (#25760348)
Sounds like a good way for someone without coding skills to help a project, bug/message triage.

But then, a good bug-reporting system should be able to do such filtering?

I'm wondering if detecting abusive communications is/could be part of it, bit of ML seems like it would fit, even just some Bayesian filtering might do.

One could also train an NN to recognise images of the app (or simpler: OCR|grep) and require a screenshot with any submission.

But I guess automated triage mightn't be the best route. It seems very much a delicately balanced people problem.

Re:Signal community: Reminder: Please be nice by kelnos on Thursday January 14, 2021 @02:04AM (#25773108)
I don't think you even need to be that brutal. Just have a file on your hard drive with a canned response that instructs the reporter that they need to provide more information, and how to provide it. Every time you run into a weak bug report, copy-paste that response into the issue comments. If the extra info gets provided, great, now it's a useful bug report. If not, you can close the issue, and not feel anywhere near as bad about doing so.
Re:Signal community: Reminder: Please be nice by matz1 on Wednesday January 13, 2021 @09:37AM (#25762439)
Like anything else, the more you do it the easier it gets. Its not going to be instant but you'll get used to it.
Re:Signal community: Reminder: Please be nice by proactivesvcs on Wednesday January 13, 2021 @03:48AM (#25759701)
The Syncthing project will often apply this trait and you're right - it's admirable as well as pragmatic.
Re:Signal community: Reminder: Please be nice by madeofpalk on Wednesday January 13, 2021 @07:09AM (#25761047)
It's a skill probably worth practicing.
Re:Signal community: Reminder: Please be nice by StavrosK on Wednesday January 13, 2021 @02:42AM (#25759322)
You can and I regularly close tickets for not following the template that says at the very top "tickets not following this template will be closed with no reply".

It's even better if you can get a bot to automatically reply and close it.

Re:Signal community: Reminder: Please be nice by Tehnix on Wednesday January 13, 2021 @09:09AM (#25762101)
I was thinking about how one could automate this when reading.

Not a foolproof way, but add a string in your Issue Templates that is required to be there, e.g. <!-- AUTOMATIC-CHECK -->.

If this is not present in the issue, the GitHub action just closes the issue with a message to please fill in the template if they wish to create an issue.

Doesn't catch nearly everything, but should get some and it's easy to set up. Could be interesting to go further with the idea and maybe check if each section contains text or something like this, hmm...

Re:Signal community: Reminder: Please be nice by a1369209993 on Wednesday January 13, 2021 @09:01PM (#25770869)
Another, somewhat more underhanded trick: add a string that is required to not be there, e.g. "Please remove this line entirely.", halfway through the template, and mention it nowhere else.
Re:Signal community: Reminder: Please be nice by StavrosK on Wednesday January 13, 2021 @09:17AM (#25762193)
I've seen this in repos, I'm pretty sure there are bots who implement it. I'd guess it catches more than 90% of cases, especially if you put the string at the bottom of the template.
Re:Signal community: Reminder: Please be nice by oefrha on Wednesday January 13, 2021 @02:44AM (#25759329)
You can. You can do anything, really, including not reading issue reports at all. But you set out to be helpful anyway, so it’s about finding a cutoff where you don’t want to help anymore. As I said, it’s simply harder than ignoring assholes. (Plus you may get a bad rep.)
Re:Signal community: Reminder: Please be nice by teekert on Wednesday January 13, 2021 @04:29AM (#25759931)
Honestly sometimes the amount of things that you need to fill out just makes me use other software. I.e. kmail would never remember that I want my email threads expanded (this example is not real, the kmail devs were very helpful with minimal info in this case). Does this really require I hunt down all this info from all around the place? Sometimes I don't even know where to get the info.

What helps immensely (and I saw this in the Geyser MC project), the software can produce a snippet with all info the devs want with one command, and it even exports to pastebin taking out sensitive info. If you paste such a link in their Discord it even makes an overview with syntax highlighting in the chat. That really helps a lot on my (bug reporter) side. And thus on the dev side.

Re:Signal community: Reminder: Please be nice by pbhjpbhj on Wednesday January 13, 2021 @05:43AM (#25760382)
KDE, and it's related apps, is an interesting one. For a long time you could get the version info from a menu item (Help>About or something) in any of the K apps. But then they changed it to give no version info ... then the bug report tool asks up front what version you're using ...

One of the great things with Steam when I started running it on Linux was it's debugging info that gathered details of your system so you didn't have to.

Re:Signal community: Reminder: Please be nice by bmn__ on Wednesday January 13, 2021 @07:40AM (#25761264)
> But then they changed it to give no version info

This is still the case. Every KDE application has the menu entries Help → About $APPNAME and Help → About KDE which both show the relevant version numbers. I'm overwhelmingly certain this feature never went away because I am on a rolling distro and upgraded through pretty much all versions and I figure I would have noticed the absence of these menu entries.

> then the bug report tool asks up front what version you're using

That's incorrect. The menu entry Help → Report Bug… opens a dialog with version information that has a button Launch Bug Report Wizard which produces a link like e.g. `https://bugs.kde.org/enter_bug.cgi?format=guided&product=kon...`. Consequently in the bugtracker, the available information is already filled in.

----

By the way, this post is an example for the bullshit asymmetry principle, and I resent that I had to spend a magnitude more time to correct your misinformation than it took you to produce it. Please be a better netizen.

Re:Signal community: Reminder: Please be nice by pbhjpbhj on Wednesday January 13, 2021 @10:37AM (#25763286)
Ok, I'm a 20y user of KDE, and a massive supporter. I still got the app version from apt (apt-get at the time) and framework version and still submitted bug reports - after registering and installing symbols to get decent backtraces. I even helped some people improve their forum posts by showing them how to get the relevant version numbers.

There was a change, it was unhelpful. There were reasons, it was to do with changes in versioning on plasma frameworks - I could look up the details, but that isn't really important a few years hence.

The jist of my comment is that structures within an application can help us non-programmers to make useful bug submissions; I cited 2 examples from my real life experience.

Hopefully we agree on the basic premise I set out at least?

Re:Signal community: Reminder: Please be nice by teekert on Wednesday January 13, 2021 @12:11PM (#25764963)
Yeah this was also the gist of my comment(s).
[dead]
Re:Signal community: Reminder: Please be nice by teekert on Wednesday January 13, 2021 @07:01AM (#25760990)
I understand the -1, but you have to understand that to a user the choice is sometimes between:

1. Create crappy bug report and move on quickly to get things done or:

2. Do not create a bug report and move on immediately, to get things done

I try to file whenever I can but when it's getting late and I want to go to bed I choose option 1 sometimes. Maybe I should choose option 2?

For example, take the Nextcloud bug filing template on GitHub [0]. It's quite a long read but sure, worth the effort for free software I agree (Nextcloud is my favorite project, my life is in there, on my server)! However, I may not know exactly where these things are:

    ```
    #### Web server error log
    <details>
    <summary>Web server error log</summary>

    ```
    Insert your webserver log here
    ```
    </details>
    
    #### Nextcloud log (data/nextcloud.log)
    <details>
    <summary>Nextcloud log</summary>
    
    ```
    Insert your Nextcloud log here
    ```
    </details>
    
    #### Browser log
    <details>
    <summary>Browser log</summary>
    
    ```

    Insert your browser log here, this could for example include:
    
    a) The javascript console log
    b) The network log
    c) ...
    ```
They also want config.php, contents of `sudo -u www-data php occ app:list`, ask you to do this:

    Login as admin user into your Nextcloud and access 
    http://example.com/index.php/settings/integrity/failed
Also all versions:

    ### Server configuration
    
    \*Operating system:\*
    
    \*Web server:\*
    
    \*Database:\*
    
    \*PHP version:\*
    
    \*Nextcloud version:\* (see Nextcloud admin page)
    
    \*Updated from an older Nextcloud/ownCloud or fresh install:\*
Moreover, I'm quite afraid to put my domain names or even more sensitive info onto a public website if I just copy and paste. All I'm saying is that a big button that generates everything a dev needs with sensitive stuff redacted (which should be doable here and yes maybe I should make a PR for that) will make the experience a lot nicer for the reporter and the dev.

As said, the Geyser MC project [1] can do exactly this and to me it is a game changer, the whole process was fast and pleasant and it was easy to test the automated builds they made in the branch based on my issue and report back in context on GitHub. Pasting the JSON their report feature generates into their Discord channel together with your question and their ability to just !docs/something point you to relevant docs with a small command feels like magic. I found the whole process inspirational.

I love all FOSS devs. You are my heroes.

[0]: https://github.com/nextcloud/server/issues/new?assignees=&la...

[1] https://github.com/GeyserMC/Geyser

[dead]
Re:Signal community: Reminder: Please be nice by dumpsterdiver on Wednesday January 13, 2021 @09:00PM (#25770853)
> But "it's getting late" is not an excuse; it's getting later for people who need to read your crappy bug report.

First of all, I applaud your proper use of the semicolon in a sentence. As someone who should probably step away from my computer a lot more though, I've got to disagree that "it's getting late" isn't a valid excuse, because I use it all the time and I mean it when I say it (i.e. it's 4am and I have to wake up for work in 6 hours).

Re:Signal community: Reminder: Please be nice by oefrha on Thursday January 14, 2021 @12:52PM (#25779575)
No one’s forcing you to submit a ticket at 4am, full stop. You can do it the next day, or you can simply not do it. You’re the initiator of the interaction, and if you intentionally half-ass it you’re not respecting the other side. Not sure what that snarky (?) remark on semicolon usage was about. We’re not grade school pupils here so no point in applauding or criticizing punctuation usage; doing so only raises eyebrows.
Re:Signal community: Reminder: Please be nice by dumpsterdiver on Thursday January 14, 2021 @08:54PM (#25785956)
> Not sure what that snarky (?) remark on semicolon usage was about.

I definitely wasn't intending to be snarky, my compliment was genuine. I don't see people use semicolons properly in sentences often, or much at all outside of coding. I meant no offense, I was giving you an honest compliment.

Re:Signal community: Reminder: Please be nice by dumpsterdiver on Thursday January 14, 2021 @11:43PM (#25787096)
Hey, I also just wanted to say that I know you FOSS folks are overworked and under-appreciated, and a lot of us really do appreciate you. I know you all get bombarded with all kinds of BS all the time, and I'm thankful that my patience hasn't been tested to such an extent. Thank you.
Re:Signal community: Reminder: Please be nice by teekert on Wednesday January 13, 2021 @07:32AM (#25761196)
Fair enough. It helps if at least the communciation is clear: Like "Fill it all or don't file" or "Try to file as much as you can".

I really don't want to make it later for devs that give me so much. I'd be ok with: "Closed: Too little info" from a bot. I may decide to have another crack at it later when I have more time.

Edit: Btw, I'm using software for fee but, I'm also beta-testing for free. It's not just a one-way street: "I derive value from a free product so I should never complain." Is that really true?

I also invest time beta-testing (some times for products that make money on support or are open-core or are a gateway to paid software). Sure there are trolls, but there are also many users that make crappy reports that really want to help but just don't understand how (or why their report is a waste of everyone's time).

Re:Signal community: Reminder: Please be nice by kelnos on Thursday January 14, 2021 @02:17AM (#25773183)
> I'm using software for fee but, I'm also beta-testing for free.

Assuming you're talking about a beta release for some open source software package, versus a full release, I don't think the distinction matters. You're using software that you got for free. It doesn't matter if it's beta- or release-quality. You aren't entitled to different/better support for it just because the developer chose to put out a version they admit isn't quite release-quality[0]. You're entitled to exactly the same amount of support as for a release version: none whatsoever.

> "I derive value from a free product so I should never complain."

I think that's framed the wrong way. I do agree that you should probably never complain about something you got for free; that smacks of undeserved entitlement. But constructive criticism and useful bug reports are (usually, depending on the maintainer) welcome.

[0] A developer might put out a beta version for a variety of reasons. One reason, yes, might be because they intend to jump on support requests faster in order to shape things up for a proper release. But another reason might be because they simply wanted to share with people as soon as possible.

Re:Signal community: Reminder: Please be nice by joncampbelldev on Wednesday January 13, 2021 @09:59AM (#25762738)
TFA and the person you're replying are not suggesting you can never complain (at least I don't think they are).

There is a difference between not complaining vs raising issues constructively and valuing the maintainers time at least as much as you value your own time.

Re:Signal community: Reminder: Please be nice by bxnkL on Wednesday January 13, 2021 @04:00AM (#25759767)
Depends on the project. If it is governed by bureaucrats and you do that too often, you'll be accused of "not being inclusive".

The modern version of "Boxer the work horse should work harder".

Re:Signal community: Reminder: Please be nice by LoSboccacc on Wednesday January 13, 2021 @07:48AM (#25761323)
this is extremely frustrating for the users.

there's a game I used to play fairly often before updates simply broke it. like mission items were replaced with random fires floating in water. many users with the same issue reported it, and some like me even provided a save (which was never even downloaded)

all such tickets were closed with "cannot reproduce"

I'm not (their) tester, I don't have time to fully reproduce issues step by step, and I don't have access to a debug build anyway to figure out the bug trigger condition

"does not work" is the best I can say here.

Re:Signal community: Reminder: Please be nice by joncampbelldev on Wednesday January 13, 2021 @09:51AM (#25762637)
Was the game free? And did the people working on the game contribute a lot of their time to it for free?

If not then I can see the reason for your frustration, however it is not the same as free software being worked on (at least partly) by volunteers receiving the same lack of effort (or in signal's case nastiness) in bug submissions.

Re:Signal community: Reminder: Please be nice by LoSboccacc on Wednesday January 13, 2021 @10:14AM (#25762939)
paid
Re:Signal community: Reminder: Please be nice by philliphaydon on Wednesday January 13, 2021 @07:51AM (#25761363)
> I’ve painstakingly implemented debug logs and carefully prepared issue templates yet I still get these “does not work (EOM)” (effectively) issues.

I’ve gone to a few GitHub repos to report bugs only to be met with a novel length template and just left.

Got no issue following a template to provide enough info to help solve a bug. But damn nothing worse than having a giant template with 20 questions.

Re:Signal community: Reminder: Please be nice by AnIdiotOnTheNet on Wednesday January 13, 2021 @08:16AM (#25761564)
Yeah, as much as parent complains about users not believing their time is valuable, my time is valuable too. I might not get back to you for a day or more because I have other shit to do.

Generally speaking, I don't even bother to file bug reports anymore. 70% of the time my issue is already in your issue tracker, sometimes has been for years, and nothing has been done about it despite multiple users giving you the logs and whatnot you've asked for anyway. I could be all "me too" in a vein attempt to convince you you really should fix this thing, but you're just as likely to be annoyed by the complaint and further deprioritize it in your mind.

Re:Signal community: Reminder: Please be nice by Abhinav2000 on Wednesday January 13, 2021 @03:17AM (#25759508)
> (For the record, I got maybe a total of $10 in donations from thousands of hours of FOSS work. Actually a high profile project I worked for did receive sponsorship, but nothing went into my pocket for obvious reasons.)

Can you expand on the last bit? Is it common for sponsorship not to go to the actual developers working on the project and getting eaten by middle layers of bureaucracy?

Re:Signal community: Reminder: Please be nice by oefrha on Wednesday January 13, 2021 @03:22AM (#25759538)
I never saw a dime and never looked into spending details, but to the best of my knowledge, sponsorship money largely went to hardware for infrastructure; then some went to sponsoring physical meetups, e.g. reimbursing travel expenses of team members who attended FOSDEM. It’s not a lot of money so if everyone gets paid I suppose it would only be a token amount.
Re:Signal community: Reminder: Please be nice by Abhinav2000 on Wednesday January 13, 2021 @03:34AM (#25759611)
Thanks!
Re:Signal community: Reminder: Please be nice by rootusrootus on Wednesday January 13, 2021 @11:28AM (#25764205)
I'd like an option to pay for prioritization, or pay outright for fixes. "Pay $100 to raise the priority of this issue X points" or something like that. Wouldn't be that hard to sell to my management when we're running up against a bug that affects us directly but perhaps doesn't have a huge impact on the community at large.
Re:Signal community: Reminder: Please be nice by dane-pgp on Wednesday January 13, 2021 @10:36PM (#25771563)
> Pay $100 to raise the priority of this issue X points

That could lead to some perverse incentives, but it points in the right direction. Some "mechanism design" / "reverse game theory"[0] needs to be applied, to turn the problem of frustrated users into a net benefit for the software, rather than escalating the conflict between developers and users.

For example, if a user provides incomplete information about a bug, you could respond with a message like:

"Thanks for your interest in the app and the information you have provided so far. We're currently deciding on bug fixes that will be in the next release, which should come out 3 months from now. Our decision will be influenced by the number of votes for the issue, the clarity of the bug report, and the amount of money pledged. Please head over to our forum to find other users of the software who might vote for this issue or might provide the missing information, and head to our Bountysource page to pledge a financial incentive for the fix."

[0] https://en.wikipedia.org/wiki/Mechanism_design

Re:Signal community: Reminder: Please be nice by nousermane on Wednesday January 13, 2021 @07:22AM (#25761128)
What you are describing is a perfectly typical (and expected) behavior for a user of a commercially-licensed library/server software.

Many developers/admins use both FOSS and COTS, and feel the same low-effort interaction with upstream is okay in both cases. It's possible to educate a small number of your users (and to a some extent, you should try - for example your post here is a small step in that direction!), but that work is even lower-reward than answering those half-baked reports.

To deal with low-effort, good-faith user reports, in COTS scenario, you'd hire a support/TAC person (a team, eventually). For a popular/accessible FOSS project, it is possible to have something similar on a volunteer basis:

- set up IRC channel/slack/forum/mailing list for that;

- display a prominent banner asking to "please try support forum first" on your bug submission page;

- encourage people who want to contribute, but are not quite acing your codebase (yet), to hang around in the forum, help others.

Re:Signal community: Reminder: Please be nice by oefrha on Wednesday January 13, 2021 @07:30AM (#25761180)
For very popular community projects, you can indeed solve the problems by throwing some manpower at it.

However, there's this uncanny valley of somewhat popular, mostly solo maintainer projects where you get a steady stream of tickets (say one or two a week) yet there's no community to speak of, so everything falls onto you. It gets pretty annoying when you have a couple of these uncanny valley projects.

Re:Signal community: Reminder: Please be nice by vidanay on Wednesday January 13, 2021 @01:14PM (#25765872)
> I still get these “does not work (EOM)” (effectively) issues

Over the last 20 years, I have received more than my fair share of bug reports just like this from well paid, trained, educated, internal engineers who's entire purpose is to support our software product.

When I complain to management, I get "does not play well with others" type comments.

Re:Signal community: Reminder: Please be nice by raxxorrax on Wednesday January 13, 2021 @05:51AM (#25760449)
I think a problem is the social integration of sites like Github (I assume you have your project there). Traditionally low-effort questions were filtered out because many users didn't want to get into the trouble of contacting developers directly. Although it wasn't unheard of, but there was probably significantly less noise.
Re:Signal community: Reminder: Please be nice by imtringued on Wednesday January 13, 2021 @03:30AM (#25759582)
You need a consistent process that you can point your users to. If they don't follow the process then politely explain that this will save time for both parties.
Re:Signal community: Reminder: Please be nice by oefrha on Wednesday January 13, 2021 @03:32AM (#25759598)
I do. It’s in the issue template, it’s in the wiki (pointed to by issue template), and commonly seen error messages may even point to the relevant wiki page. People who don’t care don’t care.
Re:Signal community: Reminder: Please be nice by sampo on Wednesday January 13, 2021 @05:45AM (#25760393)
Could issue boards have volunteer community moderators, like Reddit and StackOverflow have?
Re:Signal community: Reminder: Please be nice by saargrin on Wednesday January 13, 2021 @03:27AM (#25759562)
you are a true hero :)