Hi, Thanks for raising the idea of strengthening review practices. ASF projects should balance process with inclusiveness. Formal enforcement (such as mandatory two-review rules in GitHub) can unintentionally centralise control, especially if all reviewers come from the same organisation, and can lead to the exclusion of other companies' contributions, both directly and indirectly.
A more community-friendly approach might be to encourage multi-review through project norms, i.e. documenting it in the CONTRIBUTING guide or treating it as a “preferred practice”, rather than enforcing it. However, Chris is spot on here—the key question is whether there’s been any real issue this change solves. If not, why introduce it? Kind Regards, Justin
