Re: Next commitfest app release is planned for March 18th

On Thu, 6 Mar 2025 at 18:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Peter Eisentraut <peter@eisentraut.org> writes:
> > On 04.03.25 21:37, Jelte Fennema-Nio wrote:
> >> 1. This new homepage includes open patches from*all* commitfests. And
> >> there's currently no page with that information.
>
> > Ok, that's interesting, but I'm even less sure why that should be the
> > default view.  The whole point of chunking things into commitfests is to
> > have a focused view on what to do now and what to do later.
>
> Indeed, that choice seems completely astonishing.  You just kicked to
> the curb all of the discussion at FOSDEM about how patches shouldn't
> be carried forward automatically.

I see where you're coming from, but I think you're exaggerating a bit.
The commitfest that each patch is part of is visible in the CF column
on the new page. Patches from old commitfests color-coded red, and are
sorted below new patches from future commitfests, which are again
sorted below patches of the active commitfest. Your own old patches
that you are supposed to move/close are shown at the top of your page,
to remind authors to actually do that.

To be clear: This new view does not replace the homepage anymore, it's
now a separate /me page.

> Effectively this means patches
> will *never* go away until somebody closes them explicitly.

True, but it will also cause authors to actually close/move those
patches explicitly. And if an author doesn't close/move their patch in
an old commitfest for some time, it seems completely reasonable for
someone else to close that patch as Withdrawn/Rejected (or maybe a new
status like Inactive). I'd say let's try this new view out like this
and see what problems people actually have when using it. Especially
since this is in addition to the existing views, not replacing
anything.