2 ms·
I then wonder if somebody has a bumpbot now, just to prevent these issues from being closed by stalebot. :)
by gaius_baltar 5y ago
I then wonder if somebody has a bumpbot now, just to prevent these issues from being closed by stalebot. :)
- techdragon 5y agoI was going to ... In fact I just did a bunch of research for half an hour. I picked a language, hosting, UI tools, looked up the API calls and worked out how to do most of the mechanical process behind the scenes. Despite being a decent idea and a product I'd 100% use myself, I'm not sure I should do any more work on the idea due to GitHub's Acceptable Use Policy... > 10. User Protection > You must not engage in activity that significantly harms other users. We will resolve disputes in favor of protecting users as a whole. I can see a lot of arguments that GitHub could use to label any kind of automatic "bumpbot" bot/tool/service in widespread use as violating this clause. If I was more confident it wouldn't get ban-hammered and shutdown, I'd pop back open that folder of notes and get at it.
- remram 5y agoI was considering making a browser plugin to have a one-click button to comment "this issue is not going away by itself, please read it before you decide it's stale" or similar. Now that ddevault wrote this it might be a good resource to put in there. Making a completely automated bot certainly falls short of GitHub's acceptable use policy.
- Qub3d 5y agoMy first thought: Maybe include a link to the ddvault post in the template? On second thought... maybe not. I could see it quickly becoming a battering ram that just annoys OSS devs. Ultimately, this isn't something users can't improve, it has to be the maintainer. Nagging OSS maintainers is how we wind up with incidents like left-pad. In the most extreme of circumstances, if a maintainer is hiding issues behind the stale bot, it could be interpreted as abandonment and a fork should be made.