Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: How to say no to a GitHub issue feature request?

news.ycombinator.com

Post reply on HN
Print view View original

151–160 of 243 posts

Re: Ask HN: How to say no to a GitHub issue feature request?

#151

Post by AH4oFVbPT4f8 »

zigzag312 wrote: post #144

One way to think about it: By making a FR, the user is providing free feedback. This feedback might be useful or not. Still, remember that the user has invested his/hers time to submit the explanation. Be nice if possible. Passionate users can be a bit extreme, so give them some slack. But if the user is not behaving politely, ignore him. The user has NO idea how expensive would it be to implement this FR. Even devel…

it would be interesting if github allowed the user to submit the feature request and commit x amount of dollars they are willing to pay to have it implemented. if the maintainer wants to entertain the offer, the two agree, and requestor submits the money to github to hold in escrow until the feature is implemented or the time has expired.

Re: Ask HN: How to say no to a GitHub issue feature request?

#152

Post by mmcnl »

To me it sounds you don't really know why it's not a good idea, but you are just annoyed by the phrasing of the feature request.

So my advice would be:

1. Relax.

2. Take the emotion out of the equation.

3. Actually try to think about the feature request and why you will or will not implement it.

4. Calmly explain your reasoning based on rational grounds.

Re: Ask HN: How to say no to a GitHub issue feature request?

#153

Post by type-r »

If I think it's actually a good idea, I tell them I'll happily accept a pull request. I've had dozens of feature requests but only once has someone actually taken me up on this.

If I don't think it's a good idea, I'll give reasoning why and close the issue. If they reopen the same thing I'll ban them. Very simple.

Re: Ask HN: How to say no to a GitHub issue feature request?

#154

Post by atoav »

tut-urut-utut wrote: post #118
Freak_NL wrote: post #89

Earlier quoted context omitted.

Along with the 'no' it may help to point out that they are free to fork the project and add the feature to their own fork, or hire someone to build it for them. That won't stop the most extreme class of complainers, but it'll shave of another few.

Why pointing out something that is a distinguishing feature of open source? I don’t need your permission to fork off the license allow me to, but telling me that I’d like putting a comment like „btw, did you know that 2+2=4“.

> Why pointing out something that is a distinguishing feature of open source?

Because users exist who are:

- clever enough to use github and open an issue

- not clever enough to know this is a possibility

- care about their problem enough to complain, but not enough to do something about it

By basically telling users "if you really care, you could do $labori tensivething" often they realize that they do in fact not care enough. And if they do, you could still use the fruit of their labour if it really turns out good.

Re: Ask HN: How to say no to a GitHub issue feature request?

#155

Post by sandreas »

nonameking2026 wrote: post #103
sandreas wrote: post #82

Earlier quoted context omitted.

If you would like to see an example of a polite and meaningful discussion I had with a maintainer declining my feature request, you could read this: https://github.com/nblumhardt/serilog-timings/issues/52 But I would not expect every requester to be polite and accept a NO...

It would be a really cool feature :)

Thanks. Hehe, yes indeed. But you can't always get what you want...

Re: Ask HN: How to say no to a GitHub issue feature request?

#156

Post by skinnymuch »

tut-urut-utut wrote: post #118
Freak_NL wrote: post #89

Earlier quoted context omitted.

Along with the 'no' it may help to point out that they are free to fork the project and add the feature to their own fork, or hire someone to build it for them. That won't stop the most extreme class of complainers, but it'll shave of another few.

Why pointing out something that is a distinguishing feature of open source? I don’t need your permission to fork off the license allow me to, but telling me that I’d like putting a comment like „btw, did you know that 2+2=4“.

You are a more advanced user. It’s obvious a lot of the users like the one in the OPs example are not. They don’t know the nuances of how things work. They may think things like people are being properly compensated in some way for open source code projects. They may not know about forking or it’s possible to hire someone to add the feature you need. Bounties etc.

Re: Ask HN: How to say no to a GitHub issue feature request?

#160

Post by jhauris »

zimbatm wrote: post #69

The best thing to do is to decide where your boundaries are, and then tell them. I was in your position many times. I was so frustrated to feel like the other person was entitled to my time. Then I had to fight my urges to tell them to fuck off, wasting even more time and energy in the process. Even if I replied, it wasn't helpful to anybody if I was being polite but passive-aggressive. Then I realized that it was a…

This is great communication advice. Your original state sounds a lot like the "asker" vs. "guesser" cultural problem [1]. I've found putting a label on those two outlooks to be very helpful.

1: https://www.theatlantic.com/national/archive/2010/05/askers-...

Post reply on HN