5 ms·
My impression from looking at the repo's Issues occasionally is that the maintainers seem to be permanently pissed-off and/or burned-out. They close so many iss
by frou_dh 6y ago
My impression from looking at the repo's Issues occasionally is that the maintainers seem to be permanently pissed-off and/or burned-out. They close so many issues as Duplicates but never link to what they are duplicates of, and ignore the inevitable requests for that information.
- jorams 6y agoRuthlessly closing issues seems like the only reasonable way to deal with the onslaught of low-quality issues being opened. Whenever YouTube breaks it, several issues are opened within 30 minutes, and filled with entitled, respectless complaints about it still not being fixed. I've contributed once or twice, but dealing with that issue tracker has always seemed like hell.
- frou_dh 6y agoThat's a factor but I don't think it's limited to attention deficit ingrates spamming new issues. I've seen tons of perfectly reasonable comments along the lines of "This old issue got closed as a duplicate, but after searching the tracker, I cannot find the open issue, and the problem is still present. Can you tell me where it is?" that seem to get a flat 0% response rate. I wouldn't blame them for being burned-out though. Presumably they aren't being financially compensated for maintaining it, and relative to the amount of use the project gets, there's probably not that much prestige either, because it's very "utilitarian".
- Yver 6y agoThe repository has 2,221 issues labeled as duplicates. If it takes the developers 30 seconds to close an issue, that's about 18 hours spent on handling bogus reports.
- nix23 6y agoDelete the repo, reopen it, add your code, an 18 hour safe.