Live data from Hacker News

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

news.ycombinator.com

181–190 of 243 posts

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

#182

Earlier quoted context omitted.

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.

This exists as third party services. IIRC it’s exactly how bountysource used to work. I think the model never took off enough to be attractive to github to implement on their end. But yea I think it would be cool and more popular if integrated directly in it.

Users don't understand costs, especially for certain countries. The biggest bounty I got was like $300 for a solid week of work. Most were a few bucks. It was a waste of everyone's time and money, except BountySource.

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

#184
Honestly I think you should try to state exactly how you feel (F off) in the most professional and non-abrasive way possible. What do you really want to say to this person? Do that.

The important thing is to speak your truth. You don't owe anyone else anything in this life!

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

#186
You can just block them from the repo. If it's using up your emotional energy after you've explained your position, be proactive and push it away. I realise that's the nuclear option, but at some point you have to draw a line - especially when it's your time and your mental health that is being drained away.

I've only needed to do it a couple of times on my projects, but sometimes it's needed.

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

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

And if 2. is "no" then let them know why not, but there is no need to "debate" it further either. Sometimes it's very important NOT to add features to a project. In fact I would argue that this is one of the strengths of OSS projects compared to "enterprise software".

[deleted]
Post reply on HN