Howdy JB, I like this idea.
I believe that this is a natural step given how the codebase and active participation has grown. This helps us solve a few problems: 1. For subject matter experts, it allows them to know which reviews truly need their attention without having to sort through an inbox. 2. For new contributors, it allows them to know who understands the codebase, so they can get help as they are onboarding. Go community, Adam On Wed, Dec 24, 2025 at 11:04 AM Dmitri Bourlatchkov < [email protected]> wrote: > Hi JB, > > Using the auto-labeller to notify some specific people on PRs sounds > reasonable to me. > > For me personally, it probably makes little difference as I get > notifications for all PRs anyway :) However, I'm willing to participate and > see how the new system works in practice. > > Cheers, > Dmitri. > > On Wed, Dec 24, 2025 at 2:08 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi folks, > > > > Some time ago, we decided to remove auto-reviewers on PRs to prevent > email > > flooding and increase the "velocity". However, we have recently discussed > > concerns regarding PRs being merged too quickly without sufficient > > oversight. Additionally, several contributors have volunteered to help > > review changes for specific modules. > > > > To address this, I have drafted a proposal for module-specific reviewers: > > - PRs will be automatically labeled based on the modules affected. > > - A specific set of reviewers/experts will be automatically added to the > PR > > based on those labels. > > > > The goal is to ensure the right "experts" are notified without > overwhelming > > everyone with notifications. > > > > I have created a PR to illustrate how this would work: > > https://github.com/apache/polaris/pull/3328 > > Please note that this is an initial draft of the labels and reviewers, > and > > we can refine the lists as needed. > > > > Thoughts? > > > > Regards, > > JB > > >
