Hacker News new | ask | show | jobs
by deng 130 days ago
Again: the maintainer does not say there is no bug. He says: please open a new issue, with a proper title and description for the actual underlying problem. Is that seriously too much to ask? Instead, the guy writes a whole blog post shitting on the project. Does anyone still wonder why people burn out on maintaining FOSS projects?
2 comments
bfrog 129 days ago
Open Source is not Free Support, the sooner this reality sets in (accelerated surely by AI spam) the sooner we get to the happy place.
link
halapro 130 days ago
Not great behavior I agree, but what else is there to say other than "it does not match the spec at point 1.2.3"?
link
Semaphor 130 days ago
Then opening the ticket should be easy enough?

I certainly understand the maintainer here, because that’s what I keep telling colleagues at work.

Tickets get really cumbersome if they are not clear and actionable.

link
zelphirkalt 129 days ago
> Then opening the ticket should be easy enough?

For both of them! Since both of them are aware now, either one could open that ticket. If the maintainer has very specific ideas about how a ticket should look, maybe they can do that themselves quickly, now that they are aware of not complying with the RFC. Then the ticket will perfectly match their expectations.

link
Semaphor 128 days ago
Because that's incredibly entitled. The maintainer is already the one who has to fix it.
link
zelphirkalt 128 days ago
The maintainer is usually also the one who has to trace the root cause, which in this case the issue reporter did, which is certainly more work than creating an issue according to the formatting and other requirements the maintainer may have. So in that light, the reporter of the issue already did a big chunk of work for the maintainer or the project. I wouldn't really call them acting "entitled" after that. Clearly they put in effort more than could be expected already.
link
bioneuralnet 129 days ago
Exactly, that's all his PR had to be. The history of finding the issue could be an interesting story (I bet it involves Elixir!), but in places it reads as almost malicious. If I received a PR anything like that on something I maintained, it would be received very poorly. The author comes off as overly aggressive toward the maintainers and far too sensitive to their response.
link
PunchyHamster 129 days ago
...that's what they are asking, yes.
link