Reduce JIRA issue count

[raphinesse]

I think we should close all JIRA issues that

• refer to a deprecated component
• haven't been updated in over X
  (I think one year might work for now)

I'm open to other closing criteria.

Proposal for comment on issues closed for inactivity

Thanks for reporting this bug. It's been some time since there were any updates to this issue, so I'm not sure this is still a problem. I'm going to close this issue now and request you reopen the issue if you're still experiencing this problem. I'm sorry for any inconvenience.

Quick Stats

• Unresolved issues: 2020
• haven't been updated in over a year: 1224

[raphinesse]

Well, browsing through the inactive issues a bit, I'm not sure that we should simply close based on activity. There seem to be many still-valid issues in there 😞

Any other ideas on how to tame the beast?

[brodybits]

I would propose this kind of a process for one component at a time:

• Enable issues on GitHub as discussed in GitHub migration proposal #75
• Migrate following one of these alternatives:
  • Use Google GitHub Issue Mover [1] or Browser-based tool such as Kamino Chrome extension [2] to auto-migrate open issues to GitHub
  • Close all open issues with a note asking the OP to migrate to GitHub if still relevant
• Move forward with stale bot [3] on GitHub

As a side comment it seems to me like a handful of people have put in the majority of the cleanup and maintenance effort (major efforts by @raphinesse), would like to see it more distributed somehow.

[1] https://github.com/google/github-issue-mover
[2] https://chrome.google.com/webstore/detail/kamino/ffdebockfdjileaojbbccofhgncmioaf
[3] https://github.com/probot/stale

[raphinesse]

Closing in favor of the more recent and active discussion on the mailing list.