5 ms·

Consider applying the exponential back-off technique. Originally designed for firewalls, it works well with annoying people! (particularly Slack etc. with faste

by keyle 4y ago

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 hours silly request 3: respond the next day silly request 4: respond within a week Stand your ground. No one can make you lose your cool or upset you, unless you let them. Politely decline every time and they'll get the drift, slowly. And if your product is open source, they can fork it and shovel it themselves.

rvnx 4y ago
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 ideas that you or users submitted. The question of whether to implement the feature or not, is to be answered during product priotization while assessing potential engineering cost and impact of the feature. Whether the user is annoying or not isn't directly relevant, and if it is, it should be based on potential reputational risk under the impact score.
- prmoustache 4y ago
  > 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 are going to be coming and saying "you see, this open-source software is not maintained" I fail to see how it would be a bad thing.
- keyle 4y ago
  You're mistaken this as my default response handling. That's incorrect. This is only for the repeated and unsolicited actors who have nothing better to do than make your life a living hell. The logs will show that you're being responsive, and that this person clearly doesn't let go.
- spfzero 4y ago
  >"you see, this open-source software is not or poorly maintained" 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!"

by keyle 4y ago

rvnx 4y ago

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 ideas that you or users submitted. The question of whether to implement the feature or not, is to be answered during product priotization while assessing potential engineering cost and impact of the feature. Whether the user is annoying or not isn't directly relevant, and if it is, it should be based on potential reputational risk under the impact score.

prmoustache 4y ago
> 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 are going to be coming and saying "you see, this open-source software is not maintained" I fail to see how it would be a bad thing.
keyle 4y ago
You're mistaken this as my default response handling. That's incorrect. This is only for the repeated and unsolicited actors who have nothing better to do than make your life a living hell. The logs will show that you're being responsive, and that this person clearly doesn't let go.
spfzero 4y ago
>"you see, this open-source software is not or poorly maintained" 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!"