Re: new commitfest transition guidance

On Wed, Feb 19, 2025 at 10:30 AM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> Moving stuff to the next commitfest is incredibly painful at the
> moment. It currently takes 4 clicks per patch to move it to the next
> commitfest. We could probably get this to 1 per patch with some UX
> redesign. But that still means that if you have 10 patches on the
> commitfest, then you have to click 10 times. It seems kind of silly to
> have to do that for a patch for which you sent an email to the thread
> last week.

I respectfully but firmly question your definition of "incredibly
painful". What *I* think is incredibly painful is that I can spend an
hour going through the CommitFest and not find a single patch that
needs a review. And it's not just me. I have heard of multiple cases
of people wanting to get involved in patch reviewing and being unable
to find anything that seemed like a good candidate. We are literally
driving people out of our development community by having a CF app
that is totally unusable. The first priority here, at least IMHO,
should be improving the signal to noise ratio to something bearable.
If we can fix that - even partially - by making someone with ten
patches in the CommitFest -- who is thus, most likely, hoping for
something *at least* 50 to 100 hours of someone else's review time --
have to click 40 times once every two months, that is well worth it.

I am not saying that is the best possible experience for the
developer. I wish we could keep up on top of all the patch submissions
much better than we do. But insisting that we have to keep track of
the ones that maybe nobody cares about any more on top of the ones
that somebody definitely still does care about is not helping.

--
Robert Haas
EDB: http://www.enterprisedb.com