As release managers go through open PRs, we tag them with "Waiting on Review" to indicate to other internals devs that a PR needs review.
In fact, we have quite a few that are currently waiting on review: https://github.com/php/php-src/pulls?q=is%3Aopen+is%3Apr+label%3A%22Waiting+on+Review%22Unfortunately, we don't always know who is the best person to review a PR, so we hope that others are checking to see whether there are PRs that need reviews in their area of expertise.
It would be helpful to know from whom we should request reviews, based on the area of the code (i.e., ext, Zend, main, etc.). One way is to set up a table on the wiki with this information. Another way is to use a GitHub CODEOWNERS file,[^1] which takes care of requesting the reviews automatically.
I've opened a draft PR to discuss the CODEOWNERS file approach: https://github.com/php/php-src/pull/8670
I don't know how feasible it is to maintain a list like this for the PHP project. Ideally, folks would add themselves to the list and self-identify which areas of the code base they want to have automatically request them for reviews.
What do others think? -- Cheers, Ben[^1]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
OpenPGP_signature
Description: OpenPGP digital signature
