Ask HN: How to say no to a GitHub issue feature request? • Hacker News Board

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

#241

Post by robalni » Tue, Aug 09, 2022, 8:38 AM UTC

nfhshy68 wrote: post #240

robalni wrote: post #90

Earlier quoted context omitted.

> That sounds like a them problem. Yes and it's not nice to give people problems. It can even come back to you if they don't feel like they got a clear response and continue to bother you. I like to communicate in ways that are clear, honest and complete because that way people get the information they want and we can understand each other. I think the world would be a better place if everyone did that and therefore…

I agree and if I thought I got any value out of communicating extra to them I would. Fact is, this is open source, I'm doing this for fun. I'm not here for you and I don't owe you understanding or complete information.

> Fact is, this is open source

The open source part of this doesn't matter. Open source means that the user has the right to use and modify and distribute the program; it has nothing to do with communication.

This is a communication question; it's about how to respond to people that are being annoying. It's always nice to do that in a way so that every one understands each other.

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

#242

Post by skyzyx » Tue, Aug 09, 2022, 5:18 PM UTC

The requester is wrong.

You are the project leader. You are the decider when it comes to the project. Do you think this makes your project better? If so, cool. If not, say so.

If someone is badgering you, then feel free to charge them money for your time. They can choose to sponsor the development of a feature that can be used by everybody. Or they can choose to pay you for custom development that they would own after the transaction.

One thing that I do (in the US) is I have very specific guidelines about the transfer of copyright and licensing. I own the copyright to the code, full stop. I don’t offer copyright for purchase. What I do offer is a long-term, royalty-free license to use that copyrighted software that I give them once payment is made in full.

If they use my code or my designs without a license, then I have the ability to file a copyright infringement case. Thanks to the Recording Industry of America (RIAA), copyright infringement cases can be upwards of $150,000 USD per infringed copy, which can be translated into a download, which can be translated into a website visitor. Very quickly, companies realize that it’s in their best interests to pay what they owe me.

Having said all of that, if you don’t want to do it, then just don’t do it. But you have to have the backbone to say no. Set boundaries for yourself, and then enforce them. But backbone is what makes the world go round.

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

#243

Post by mmcnl » Wed, Aug 10, 2022, 7:54 PM UTC

dymk wrote: post #167

mmcnl wrote: post #152

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.

I’d agree with this if OP was getting paid, but they’re doing this for free on their own time. If it’s stressing them out, politely say no, and if Pushy Requestor continues to push, block them. You don’t need to take time to rationally explain your thought process to every random dickhead on the internet.

For me it wouldn't matter if I'm being paid or not. Someone's trying to communicate to OP, with good intent (I presume). I think that deserves a thoughtful response.