3 ms·
I help with UX in a FOSS project. When it comes to comments of that kind, the problem is that they are usually quite low effort. The person thought: "X is a goo
by atoav 7y ago
I help with UX in a FOSS project. When it comes to comments of that kind, the problem is that they are usually quite low effort. The person thought: "X is a good idea" but never once considered giving proper reasons, exploring other possible solutions, thinking aboit how it should actually look like and so on.
In my opinion a good feature request does all that legwork. The goal (my goal) is to arm the maintainer with a action-plan that they can pull out of the drawer and start working on immidiately. If this doesn't work — seeing that the other side did the legwork can still be motivating and creates a good climate.
Just imagine we are not talking about code, but about cool Lego-towers for a moment. If you want the other kid to add a certain detail to the tower, the least you can do is explain it to them properly. Better is to inspire their creativity alltogether: who says your idea is the only/best way to solve the problem?
- elyobo 7y agoYes, that's a fair point. Just "me too" doesn't convey a lot of extra information. Would "me to, because this would help solve my scenario xyz" be more helpful? What about "me too, because I also have the exact problem described" (which at least conveys that they've put more thought in to it than a totally light weight "me too")?
- atoav 7y ago> Would "me to, because this would help solve my scenario xyz" be more helpful? Quite definitly. But even more helpful would be if you listed all scenarios you can think of where this would be helpful, even ones that are not useful to you, but might be to others. Then you think about how it would impact existing functionality (both positively and negatively), would it be the consistent thing to do? Where could be traps and pitfalls? Maybe even ad a mockup of hoe it would look. If you did that, the maintainer sees that you didn't just demand a feature drive-by-shooting-style, but you did the actual legwork of fleshing the thing out. Don't marry your own ideas, others might be inspired by you and have a even better way of solving this. If you are writing one sentence you are doing to little usually (in my eyes).
- gwd 7y ago> But even more helpful would be if you listed all scenarios you can think of where this would be helpful, even ones that are not useful to you, but might be to others. The danger with this is encouraging overengineering. It's easy, particularly if someone else is going to be doing the work, to say, "Maybe someone out there might someday want to do X, Y, or Z"; causing a maintainer to put a whole lot of effort and extra complexity into their code for use cases which nobody uses. In fact, when only a single person wants a feature, there's a similar risk, that I'll put a whole lot of extra effort and complexity into the code for a use case which only one person thinks they want; and that after it's implemented, they decide they don't like it and go somewhere else anyway. That's why I didn't understand why he considered "I would also use this feature" comments to be rude or unhelpful. I would think knowing that at least two (or three or four) people wanted a feature would be helpful feedback in knowing what kinds of things were worth adding extra complexity. Perhaps in his mind they took the tone of, "Hey yeah, we're all waiting for you to do this work for us for free; what's the hold-up? Get cracking!" Which of course would be a bad attitude; but looking at the exact thing he quoted, I'd say that's more about what he's reading into it than what the commenter actually said.
- deleted 7y ago[deleted]