221–230 of 243 posts
"Unfortunately I only have limited resources to maintain XYZ, and such a feature add would increase my maintenance and testing burden beyond that which I'm able to accommodate. Feel free to fork my work and/or use competing product QPR""
that's assuming even if they paid you, you still wouldnt want to do it. if you are willing to add the feature for money, that's easy, just ask them for money. often they will
If you don't stand up for yourself in life, you're opening the door for people to take advantage of you. Don't let the perceptions of others control you
If you must respond to them, politely decline, with or without a reason as you like.
If they continue insisting (which it appears they are), just stop responding. You don't owe them anything, and the above still stands.
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-...
Earlier quoted context omitted.
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.
But yes, it clearly didn't work.
Consider applying the exponential back-off technique. Originally designed for firewalls, it works well with annoying people! (particularly Slack etc. with faster rates than below.) This only really applies when you owe people an answer, so I'm not even sure this applies here. You could simply palm them off politely. Here is how it works. Silly request 1: respond within the hour silly request 2: respond within a few h…
You'll become "the guy who doesn't respond to GitHub issues" and that is going to backfire on you because commercial software, or other projects, or prosoective employers are going to be coming and saying "you see, this open-source software is not or poorly maintained" I recommend on saying "Thanks for sharing the idea" Once you have time to work on your project, then you create a new sprint based on a couple of idea…
They could just as easily be saying "wow, look at this OSS project, there are so many feature requests they can't keep up. Seems like it's valuable; people really make use of it. Let's hire!"