Thanks for your comments Antoine, > Do contributors actually have the rights to reopen a PR of theirs? I think so, but we should double-check.
I had a search and it appears that people who are not committers cannot re-open closed PRs. Instead of just closing, I could add a 30 day warning and stale-warning flag. If there are no additional comments within 30 days, we close the PR, advising in the message that if the authors should feel free to reopen it themselves and if they don't have permissions to ping a relevant committer. If there are comments on the PR, we remove the flag, and the 12 month clock has effectively been reset here for the next time we run the script. >> Issues - improvements that haven't been commented on in over 3 years > Sounds good, but with a question: will the automatic comment be reiterated later? In my experience, it's quite unnerving to have to comment every XX days on an issue to prevent an auto-close. Good point, I'd also find that very off-putting. This should be fine - when the script is run again, the new comment giving the warning will effectively have reset the clock back to 3 years. > Also, we should make the script doing this public somewhere. Perhaps in the Arrow monorepo itself, somewhere under dev/ ? Good point. I'll add the script there, run manually for the first iteration to have some control over it and refine it. Then once we're happy with the results and how much manual intervention is needed, we could consider automating it via CI, or I could look at running it after each release or some other cadence. On Sun, 22 Jun 2025 at 09:26, Antoine Pitrou <anto...@python.org> wrote: > > Hi Nic, > > In general, I think addressing this is a good idea. Some random thoughts > below: > > Le 17/06/2025 à 12:40, Nic Crane a écrit : > > > > I'd like to take the following actions: > > > > Category: 1 - PRs - haven't been commented on or touched in the past 12 > > months (137 at present; 40% of open PRs)[1] > > Classification: Possibly abandoned > > Reason: Creates noise or impression the issue is being worked on > > Response: Close these with the message "Closing because it has been > > untouched for a year, which may be an indication it's not longer being > > actively worked on. Feel free to re-open if it is still being worked > on!" > > Do contributors actually have the rights to reopen a PR of theirs? I > think so, but we should double-check. > > > Category: 2 - Issues - improvements that haven't been commented on in > over > > 3 years (498; 12% if open issues) > > Classification: May or may not still be things we'd like to implement in > > future, unclear > > Reason: Gives the impression that items are currently on someone's > roadmap, > > may prevent user making feature request for it > > Reponse: Comment on these issues with warning that will be closed in 30 > > days if no comment saying otherwise. Close unanswered issues after 30 > days. > > Sounds good, but with a question: will the automatic comment be > reiterated later? In my experience, it's quite unnerving to have to > comment every XX days on an issue to prevent an auto-close. > > > Category: 3 - Issues - user questions with no ongoing conversation for > over > > 12 months (107; 3% of open issues)[3] > > Classification: Unclear if user still needs helps > > Reason: Adds to repo noise > > Reponse: Comment on these issues with warning that will be closed in 30 > > days if no comment saying otherwise. Close unanswered issues after 30 > days. > > Manually update to "improvement" if it's now a feature update or docs > > change needed. > > +1 > > Also, we should make the script doing this public somewhere. Perhaps in > the Arrow monorepo itself, somewhere under dev/ ? > > Regards > > Antoine. > >
