News for hackers. Stuff that matters.
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.