Back

@ellie

> Thank you!! When is this released?

> Why is this not a priority?

> But why does it work in <software that I think is the same but isn't>

> I'd gladly implement it if you tell me how

> This is the only feature I'm missing in order to migrate from <software that I am using for similar stuff>

@imsnif @ellie I might not have the same perspective since I newly became a maintainer of a project used by many (Rustlings). But the comments you both posted are normal communication comments for me (except the "deal breaker" one, it communicates frustration, but it is too harsh). Unless they are spammed, I would give a short answer and move on.

e.g. answer "I am focusing on releasing x now and would get back to this afterwards. My estimate is about 2 weeks"

@imsnif @ellie Again, I don't want to compare with you, you maintain huge projects for a long time. I just want to understand why these comments are that annoying.

Especially if it is a PR, I remember my inpatient me who gets too excited sometimes about a contribution and can't wait for the maintainer to review it to maybe start the next one. I don't spam, but I sometimes ask kindly after about 2 weeks if there is something wrong. Sometimes things just get out of your radar.

@mo8it Your PR example makes total sense, but when it's on something like a feature request it's especially annoying

We end up getting a whole bunch of them every single week, and something that's important to that _one_ person may not be important to the pool of users as a whole.

Also it's just not fun to get a reminder than your software has problems/shortcomings for someone while you're sat watching TV or out for a walk or something. I don't need the ping for that

@mo8it Plus, there's only so many things I have the time/energy to prioritise, and they don't always line up with what a commenter thinks I should be working on