I think that we could start to adopt our grooming policy for the Pytorch org repositories.
As an extension to this policy we could occasionally organize some “grooming hackathon” to support these activities.
I think a regular cleanup could also help to improve the issue label inclusivity (CHAOSS/LinuxFoundsation) metrics as it will help to clearly define and communicate to candidate contributors on what issues we really will want to still allocate the currently limited PR review resources.
Thanks for bringing up this topic.
We indeed have been struggling to keep up with the number of issues.
While I do think that there are many reasons for some old issues to still exist, I do agree that we most likely have a lot of them that are not relevant anymore.
I agree that we would need to first align and adopt such a policy before organizing such events.
The VSCode description is a good start but we would need to adapt it.
How generally these things, like a grooming policy, are going to be introduced to the community?
Just to understand where we could inline comment a policy draft.