[mplanchard]

It says to use the issue tracker for bug reports and feature requests. Was there nothing in the README at that time saying anything similar?

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.

[pseudalopex]

It says the right place for bug reports and feature requests is the issue tracker. It doesn't say nothing else belongs there. Actually it says the issue tracker is the right place for any other questions about contributing too. And it just says IRC is more immediate and direct.

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...

[mplanchard]

It’s not a valid feature request when the colors are already all configurable, so anyone can change them to be however they like. The green being a little yellower than this person preferred is not a problem worthy of bothering the people who wrote the software. Non-issues like this sap the will to live of people building cool things for free on their own time.

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.

[pseudalopex]

Configurability doesn't eliminate the importance of good defaults.

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.

[mplanchard]

Again, it looking yellow is a part of the theme. The names of the terminal colors are not supposed to correspond to exact colors all the time, otherwise there would be no such thing as a theme. They are just the names of the colors used for certain kinds of output in the default theme.

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.

[pseudalopex]

Again defaults matter. Certainly no one can stop you from feeling aggrieved or reacting hostilely. Personally I find it harder to maintain enthusiasm when dealing with attitudes like yours.

[mplanchard]

I mean, that’s fine I guess? You, as a theoretical person reporting an issue, are not the one who’s got to keep the project going, and it’s not my, the theoretical maintainer’s, job to keep you enthused.