It wouldn't have been that hard to just ask "why?" rather than marking it as something that needs fixing.
Quote from the person who filed the issue:
> I don't understand why you think my behavior is entitled. I genuinely thought it was a bug because the colors didn't look right to me, in the sense that some of them don't match what is expected from their name. I still think that because the colors are distant from their expected neutral form this makes it a poor default theme.
https://github.com/alacritty/alacritty/issues/1561#issuecomm...
The original bug report was perfectly respectful, and this is a perfectly respectful reply to the revelation that it's "not-a-bug".
The maintainer is being aggressive and looking for a fight, venting their frustrations on some person who is trying to be helpful. All they had to say was, "Sorry, this is the default color scheme, we prefer it this way and I'm not concerned that the color isn't exactly green to everyone's eyes. Thanks for your interest!" and close the issue.
Describing someone else’s work and choices as ‘poor’, especially when you didn’t pay them anything for it, is disrespectful.
Regardless, people thinking whatever thing happened to aggravate them about a project is “a bug” is a huge and constant drain on open source maintainers. In this case, as other people have pointed out, there were other threads already where default colors were discussed that this person could have found, and even passing familiarity with terminal color schemes would show that much of the time, what the escape codes define as “green” or whatever is a very different color. That’s why the color schemes exist, so that you can redefine what “green” is for your own tastes. I can’t imagine opening an issue suggesting that a project change their default color scheme not because it’s inaccessible or illegible, but just because I don’t like it or it doesn’t look like some other project.
README.md said "If you run into a problem with Alacritty, please file an issue." at the time.[1]
I don't see where anyone pointed out what you said multiple people pointed out. The closest I see is 1 person said there are 88 color related issues now. Feel free to point out a specific issue you think the reporter should have found.
It isn't clear they expected the colors to match exactly. The default green looked yellow to them. And changing the default colors would be a valid feature request if nothing else.
[1] https://github.com/alacritty/alacritty/blob/9bc888fbe581efeb...
Edit: personally I don’t have the time to go digging through old repo issues of a project I don’t even work on for the sake of arguing about one entitled user. I do maintain several projects, and I definitely feel that these kind of aggressive non-issues are the worst.
It wasn't just a little yellower than they preferred. It looked yellow to them.
As a maintainer I definitely feel your attitude is worse than theirs.
As for my attitude, luckily as a maintainer it’s my right to have whatever attitude I choose about the software I write, and people are free to use or not use the software as they see fit. It’s also my right to make my own decisions about when I feel like people are wasting my time unnecessarily, and particularly about when they’re being jerks about it.
Personally I find it very hard to maintain enthusiasm for the actual work of building the software when having to deal with entitlement in the issue tracker.