Hi team,
Next week, we’re kicking off a two-month community hackathon focused on clearing out the Open edX PR review backlog. More details can be found in this Discuss forum post. We’d really appreciate if core contributors here at OpenCraft could schedule some time to target a few PRs, and help get them past the finish line. Thanks in advance, and your comments and questions are most welcome!
The spring cleaning hackathon is now live!
Hi all, the two-month review sprint has officially started. Head over to the hackathon board view and pick a PR to review — any comment or review on a PR you didn’t author counts toward the leaderboard. Let’s go! 
Following @antoviaque ‘s suggestion, I’ve created tickets for all code contributors to do 2-3 review in the next sprint 
Hey all! Someone asked a pertinent question regarding response delays on PRs, so I thought I’d share the question here, along with my response:
Open edX Senior Developer :
Hello, my favorite colleague Gabriel. I reviewed a couple of these (last week) but haven’t heard back from the respective devs. How long should I hold this open in case of follow-up review passes?
My response :
Dear colleague, how flattering. You are my favorite colleague too! And good question. As Michelle reminded us on the Discuss board, we should follow the existing OSPR guidelines on this: if there’s no response from the PR author for a month, leave a message asking if they’re still planning to work on it. If nothing after another two weeks, close the PR with a friendly note that they’re welcome to reopen.
That said, it means three complete OpenCraft sprints, but I think it would be fine to leave the task in “blocked” status until you either get a response or close the PR. Does that make sense?
I’ve given everyone a friendly nudge to report on their progress so we can keep moving these PRs forward.