Who responds? No SLA for first touch. Can fall through the cracks and be addressed weeks later
Requires research, potentially they have no cCLA, there is a long async feedback loop
CLA checker could help with triage
What org are you from, did they sign a iCLA? It takes a lot of time. A week to a month or more.
Time challenges for someone with a CLA already can still be hard because we don’t have the resources for triage of requests. An effective tactic is posting in Slack. Is this described anywhere?
We have the tech call for outstanding PR review. Do things get missed?
Maintenance WG has not had a task for outstanding PRs from outside the WG. Should it be?
It is part of the standing agenda, and it was helpful when it was in the half hour after the call.
How hard is it to find the PRs across the repos?
A dashboard would be helpful for all PRs. Anna will try to bring that up, to see all the PRs from an org in GitHub. https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Asamvera
Hygiene issues: hard to close stuff out with a lot of items
Only a handful of people feel comfortable doing the review. Doing it in tech call would have a process for others to see the review happen, and what they would need to look for if they were doing it.
How to quality control PR review – is it true that we don’t want just anyone reviewing? Functionally anyone can but they tend to be timid. We don’t have a hierarchy of who can accept it. There isn’t a problem of lots of reviewers. A first pass would be very helpful to the people who would make the final call.
Multiple levels to review – broader set who can do first level review, but if it is changing something functional it swings by a leadership role. Two ways it comes in: bug fixes are easier for others to approve. When functionality comes in, the tech lead has a bigger role in reviewing and determining what goes in core (in Hyrax, there would do that for other major components).
Julie might also look at things that would be new functionality in Hyrax.
Limited set of PR reviewers in the community creates a wait time. We definitely need more reviewers and we’ve not had an issue with quality control.
PR checklist is documented, can we incorporate more: https://samvera.github.io/pr-checklist.html
Can we make a github project board to pull from across repos in the org?
Making sure the PR template in github is up to date and easy to follow