bhack
bhack
We have more then 5k+ open Issue/Feature requests so I think that generally doesn't make sense to totally trust old tickets as Orgs changes, allocated resources changes, project policies changes...
Other then this I think that we have also some problem in the PRs stale policy: https://github.com/pytorch/pytorch/pull/55679#issuecomment-1912867025
/cc @penguinwu
As it seems that the Pytorch team is not interested in organising a regular grooming activity like other [popular projects](https://github.com/microsoft/vscode/wiki/Issue-Grooming) on GitHub I think that the stale management is the...
Please check also Chaoss metrics (Linux Foundation) about responsiveness: https://chaoss.community/practitioner-guide-responsiveness/
P.s. as we are able to organize regular [Docathon](https://pytorch.org/blog/docathon-june-2024/) I suppose we are able to organize also Grooming hackathlon
I see this was removed few days ago from https://github.com/orgs/pytorch/projects/15. Are we going to reject this proposal?
> As a side question, @bhack would you mind sharing which company/team you're a part of? It's been awesome to see how active you are here the past few months,...
@ZainRizvi I sent you an email. We can follow-up in that thread for things not strictly related to this ticket.
At the end, it seems that @BoyuanFeng is manually reviewing some tickets or not?