Live data from Hacker News

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

news.ycombinator.com

101–110 of 243 posts

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

#101
post #99

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

That really is a great example, but it's very noticeable that you both went into it with the perfect attitude (and maintained an awareness that each had different needs & goals). It's the "Veruca Salt" case that's much more difficult to solve for.

Absolutely...

I tend to first be polite, and then after some conversation do just nothing in this case... don't feed the troll

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

#102
post #96
post #86

Earlier quoted context omitted.

Is it a product made by employees of EmailEngine or how does it work ? Intuitively I would find it super rude if commercial companies just ignore or send people away for open-source tooling that is directly used for their commercial product. Like when there are Google APIs Python Client bugs and they don't care and just say "no clue, ask someone else at Google"

Nodemailer is a project I started 11+ years ago with no backing. It gets millions of download every week and is used by hundreds of thousand of projects and developers around the world. EmailEngine is a commercial project I started a year ago and now I use the Nodemailer’s homepage to drive traffic to it. Both are my solo projects, no one else is involved.

Understood.

Your projects are so well done that they gave me the impression that EmailEngine was a VC-backed opportunistic/shark startup that had eaten an open-source project and enslaved its maintainer.

So that's a big compliment I guess :)

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

#103
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…

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 :)

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

#104
post #102
post #96

Earlier quoted context omitted.

Nodemailer is a project I started 11+ years ago with no backing. It gets millions of download every week and is used by hundreds of thousand of projects and developers around the world. EmailEngine is a commercial project I started a year ago and now I use the Nodemailer’s homepage to drive traffic to it. Both are my solo projects, no one else is involved.

Understood. Your projects are so well done that they gave me the impression that EmailEngine was a VC-backed opportunistic/shark startup that had eaten an open-source project and enslaved its maintainer. So that's a big compliment I guess :)

Thanks :D

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

#105
post #46

Hi, sorry but this is simply not something I'm interested in implementing. Further, please remember that GitHub maintainers do this for free, on their own time. Thanks! --- Anything more than that, block and move on. I've been on GH for 10 years or so and it's gotten really bad in the last few regarding pushy dickheads like this. You owe nothing to them, and if they can't behave within the OSS ecosystem then they're…

As someone who makes lots of merge requests, please don’t add the further statement. In my experience while it’s well intentioned, it (understandably) frustrates contributors because it’s making an assumption that they aren’t valuing your time, which you don’t know. Just my 2¢, at the end of the day do what feels best for you, but you may drive away some contributors.

In OP's case, it sounds like the issue submitter is already being pushy and demanding.

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

#107
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…

I think this is a good advice.

To add on, for some of my projects I explicitly list out-of-scope areas in the README to give users a better idea on where the project boundaries lies.

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

#109
post #35
post #19

This sounds like a problem you will face many times in the future and therefore you may benefit from finding a solution that will solve for both this request and all similar future requests. For example, instead of writing any customised response, you could write a blog post / make a webpage that explains your approach to these types of request and then simply link to it in a reply. Then every time this comes up you…

> simply paste in “Thank you for your request. Please see [URL]”. I think this can make people feel like you don't understand them and maybe make them angry. It feels like an automatic response you would post when you haven't even read the request. I think you should at least clearly say that you don't want the requested feature in the response, then you can link to the page.

On the flip side, people need to be okay with "No."

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

#110
I have a public roadmap, where people request new features all the time (https://trello.com/b/5i4VvOW8). All of people's features are in there, but some might indeed never happen.

When someone asks or requests, my response is: "Right now I'm working on higher priority things, but some day I might get to your request". It satisfies them all the time, since they understand I'm still improving it, just not their thing.

Post reply on HN