On Tue, Mar 4, 2025 at 12:02 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
>
> On Tue, 4 Mar 2025 at 17:31, Peter Geoghegan <pg@bowt.ie> wrote:
> > > Peter Geoghegan suggested adding a "dashboard" of this
> > > kind. Feedback on this is very welcome, but depending on the
> > > complexity I don't know when I'll get to it. I'll be a bit more busy
> > > the next few weeks and also have some holidays planned.
> >
> > But here you say that you *haven't* worked on what I had in mind,
> > which is confusing.
> >
> > Are you saying that you have yet to implement a version of this that
> > shows everything (every patch that isn't closed out) for all
> > commitfests? What you've come up with only works for the current
> > commitfest, and not the next one?
>
> I meant to say: I roughly implemented what Peter G described... Ideas
> to further improve it are very welcome, but it might take a while
> until I'm able to do that.
Got it.
From the looks of the screen shot that you posted (can't seem to find
the same dashboard view on https://commitfest-test.postgresql.org?),
this is *exactly* what I had in mind -- I don't know what I said that
you haven't fully taken into account here? It's just a screen shot,
but as far as it goes it looks great.
Did you mean that you have general doubts about the general quality of
the dashboard code? As in, the code itself is rough? Seems unlikely
that that was what you meant, since you also seemed to say that you're
planning another release (i.e. deploying to production) on March 18.
I'm fairly neutral on the question of whether or not the homepage
should just be the dashboard for logged in users. Though I do think
it's important that the new dashboard is highly discoverable, so that
people know that it exists without having to be told about it.
It'd be nice if at some point you also added the ability to
star/favorite/like patches -- I'm thinking of something that worked a
little bit like starring a gmail thread. Any such patches would appear
towards the end of the dashboard page, in its own section,
independently of whether I as a user am involved or not involved in
the patch. This would be private information, visible only to the
individual user that favorited the patch -- a mere bookmark.
--
Peter Geoghegan