search

piskvorky / gensim

Topic Modelling for Humans
https://radimrehurek.com/gensim
GNU Lesser General Public License v2.1
15.62k stars 4.38k forks source link

Automated closing / locking of stale tickets #2474

Open piskvorky opened 5 years ago

piskvorky commented 5 years ago

I suggest adding Github bots to the Gensim repo to:

  1. Automatically comment on need info label, to point the user to our check-list from the issue template of what we need in reports (notably a reproducible example + SW versions), and warn them the issue will be closed otherwise.
  2. Automatically warn (post a comment) about future closing of a ticket if the ticket has a "need info" tag and no activity for 1 week.
  3. Close the ticket if there's no activity for 2 weeks.
  4. Lock the ticket if there's no activity for 1 month (to prevent people hijacking old tickets).

I found some bots that reportedly do that, e.g. stale bot, lock bot.

But we have to be careful about permissions requested by these 3rd party tools. I don't have much trust in external tools, and requesting the bot any sort of access to our private repos would be an immediate show-stopper.

mpenkov commented 5 years ago

I'm a bit "meh" about this, because we don't have that many tickets labeled need-info, so the manual labor involved in nagging people and closing tickets is minimal.

gojomo commented 5 years ago

An auto-reminder might help 'wake' a few reporters into answering requests for more info, or into letting us know it's no longer an issue for them. But given that both reporters and contributors can may only be looking-in on a part-time/casual/occasional schedule, I'd want multiple-reminders & generous deadlines before an auto-close.

I'd not want the auto-locking - if a new report/update is truly related to an older issue, perhaps even an auto-closed issue, it's best to append-to, and re-open the old issue – to retain original info in original context. (When someone is truly 'hijacking' an old ticket with unrelated questions/concerns, I think that requires case-by-case responses which guide them to the proper forum/new-issue.)

piskvorky commented 5 years ago

Another use-case for bots:

  1. Automatic comment & close of tickets we label as not a bug. Use case: all the people who want to chat on Github, and we have to point them to the issue template / mailing list over and over again.

@mpenkov yes, we managed for years without bots, this is by no means critical. But making the whole dev process clearer and more streamlined and automated is desirable IMO.