On 22.03.25 12:15, Jelte Fennema-Nio wrote:
On Fri, 21 Mar 2025 at 18:53, Tom Lane wrote:
Peter Eisentraut writes:
- If I'm the committer for a patch but not a reviewer, and the patch is
in "needs review" status, then the patch is formally speaking not
actionable by me and should not be unde
On Sat, Mar 22, 2025 at 10:49 AM Tom Lane wrote:
> > Personally, I think it'd be most useful for the dashboard to show all
> > open patches.
>
> Surely not "all"? We have that display already. Should be more like
> "patches that I have expressed an interest in or have reason to take
> current or
Peter Geoghegan writes:
> On Sat, Mar 22, 2025 at 7:15 AM Jelte Fennema-Nio wrote:
>> Yeah I think we need a way to "star" a patch (not just for committers,
>> but for anyone).
> Right. In my view "starring" something should definitely not appear in
> the "History Log" of the patch; it should be
On Sat, Mar 22, 2025 at 7:15 AM Jelte Fennema-Nio wrote:
> Yeah I think we need a way to "star" a patch (not just for committers,
> but for anyone). After creating this initial version of this dashboard
> I realized it's also possible to "subscribe to updates" for a patch,
> which means you'll get
On Fri, 21 Mar 2025 at 18:53, Tom Lane wrote:
>
> Peter Eisentraut writes:
> > - If I'm the committer for a patch but not a reviewer, and the patch is
> > in "needs review" status, then the patch is formally speaking not
> > actionable by me and should not be under "Patches that are ready for
> >
Peter Eisentraut writes:
> I have a few pieces of feedback that could be addressed by additional
> rules for how things are listed in the dashboard:
> - If I'm the committer for a patch but not a reviewer, and the patch is
> in "needs review" status, then the patch is formally speaking not
> a
On 17.03.25 23:11, Jelte Fennema-Nio wrote:
1. Major change: There's a new /me page which shows a dashboard of
open patches where you are author/reviewer/committer. These patches
are ordered & grouped in a hopefully useful way. Peter Geoghegan
suggested adding a "dashboard" of this kind. It's the
On Tue, 4 Mar 2025 at 02:21, Jelte Fennema-Nio wrote:
>
> The next commitfest app release is planned for March 18th
I deployed the latest release of the commitfest app. Below is a
changelog that's slightly updated.
1. Major change: There's a new /me page which shows a dashboard of
open patches w
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 commit
On Thu, 6 Mar 2025 at 18:08, Tom Lane wrote:
>
> Peter Eisentraut 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 les
Peter Eisentraut 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 p
On 3/5/25 12:14 AM, Jelte Fennema-Nio wrote:
On Tue, 4 Mar 2025 at 22:01, Andreas Karlsson wrote:
What I need to see is the below (plus any future commit fests).
Thanks you for describing how you use the current homepage. That's
super helpful.
I am interested in the dates when commit fests
On Tue, 4 Mar 2025 at 22:01, Andreas Karlsson wrote:
> What I need to see is the below (plus any future commit fests).
Thanks you for describing how you use the current homepage. That's
super helpful.
> I am interested in the dates when commit fests open and close
These are the same exact 5 mon
> On 4 Mar 2025, at 23:49, Jelte Fennema-Nio wrote:
>
> On Tue, 4 Mar 2025 at 20:46, Daniel Gustafsson wrote:
>> My preference would be not have any relative times or dates at all and just
>> show the date as is.
>
> I pushed a change that both improves the rendering of relative
> datetimes and
On Tue, 4 Mar 2025 at 20:46, Daniel Gustafsson wrote:
> My preference would be not have any relative times or dates at all and just
> show the date as is.
I pushed a change that both improves the rendering of relative
datetimes and also allows people to choose to disable that and just
show the da
> It'd be nice if the UI had usable hyperlinks that could be bookmarked
> by my browser. One hyperlink for each of the views.
Sounds reasonable!
> Probably "Recommended patches for you to check". Things that are on
> the periphery of my interests have the greatest chance of being picked
> up, I th
On Tue, Mar 4, 2025 at 4:38 PM Jacob Brazeal wrote:
> Out of curiosity, what features would make it most useful to you? Right now
> it's trying to do all of the following:
> * Summarize threads
> * Help you find threads about things you're interested in, independent of
> what you've commented on
> I tried this out, and was pleasantly surprised to see what seemed like
> useful summaries of discussions that I was directly involved in.
Thanks for trying it out! And big thanks to Jelte for helping me get
involved in the project.
> I'm not sure if I'll ever actually use this tool day to day,
On Tue, 4 Mar 2025 at 22:04, Peter Geoghegan wrote:
>
> On Tue, Mar 4, 2025 at 4:02 PM Jelte Fennema-Nio wrote:
> > You have to create a *new* account to do so, because the staging auth
> > and prod auth
> > systems are separate. Then you can mark yourself as author/reviewer of
> > a few patches
On Tue, Mar 4, 2025 at 4:02 PM Jelte Fennema-Nio wrote:
> You have to create a *new* account to do so, because the staging auth
> and prod auth
> systems are separate. Then you can mark yourself as author/reviewer of
> a few patches to see what it would look like.
How do I do that? Or can I do it
On Tue, 4 Mar 2025 at 21:57, Peter Geoghegan wrote:
>
> On Tue, Mar 4, 2025 at 3:50 PM Robert Haas wrote:
> > On Mon, Mar 3, 2025 at 8:21 PM Jelte Fennema-Nio wrote:
> > > As always, please test out the current staging website[1] to give some
> > > feedback.
> > > HTTP auth user and password ar
On 3/4/25 2:30 PM, Jelte Fennema-Nio wrote:
On Tue, 4 Mar 2025 at 13:36, Amit Kapila wrote:
On Tue, Mar 4, 2025 at 4:05 PM Álvaro Herrera wrote:
I think showing different pages on the same URL depending on whether
you're logged in or not is not great UX.
+1. The default should be what we
On Tue, Mar 4, 2025 at 3:50 PM Robert Haas wrote:
> On Mon, Mar 3, 2025 at 8:21 PM Jelte Fennema-Nio wrote:
> > As always, please test out the current staging website[1] to give some
> > feedback.
> > HTTP auth user and password are both pgtest.
>
> So, that worked for me, but then it wants me t
On Mon, Mar 3, 2025 at 8:21 PM Jelte Fennema-Nio wrote:
> As always, please test out the current staging website[1] to give some
> feedback.
> HTTP auth user and password are both pgtest.
So, that worked for me, but then it wants me to log into my
postgreql.org account, and that doesn't seem to
On Tue, 4 Mar 2025 at 17:15, Peter Eisentraut wrote:
> I think the option of having a list of things that I'm involved in as an
> author *or* reviewer is actually very useful and something I have wanted
> from time to time. But that is apparently not accessible using the
> normal search/filter me
On Tue, 4 Mar 2025 at 11:35, Álvaro Herrera wrote:
> https://commitfest.postgresql.org/me
I've restored the original homepage and moved this new dashboard
(minus the "Archive" link) to /me:
https://commitfest-test.postgresql.org/me/
On Tue, Mar 4, 2025 at 3:06 PM Jelte Fennema-Nio wrote:
> So patches with failing CI in the "in progress cf" will sort below
> healthy patches in the "open cf". I don't think you necessarily said
> that, but this seemed nice to me. And it's easy to spot which patches
> are for which CF because of
> On 4 Mar 2025, at 17:13, Jelte Fennema-Nio wrote:
> On Tue, 4 Mar 2025 at 16:29, Peter Eisentraut wrote:
>> Another small complaint: I don't like this style of relative times. (I
>> have also complained about it for the buildfarm status in the past.) I
>> suppose both styles are useful like
On Tue, 4 Mar 2025 at 18:25, Peter Geoghegan wrote:
> 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?),
The dashboard is only available if you login. You probably have to
create an account to do so, because
On Tue, Mar 4, 2025 at 12:02 PM Jelte Fennema-Nio wrote:
>
> On Tue, 4 Mar 2025 at 17:31, Peter Geoghegan 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
On Tue, 4 Mar 2025 at 17:31, Peter Geoghegan 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 holiday
On 04.03.25 11:33, Jelte Fennema-Nio wrote:
I'm curious if there was anything specific that you used the old
homepage for. Especially things you did often that are now harder to
do. The only things I used on the homepage were:
1. Going to the "In Progress" and "Open" commitfest (usually with one
On Mon, Mar 3, 2025 at 8:21 PM Jelte Fennema-Nio wrote:
> 1. Major change: The homepage is revamped completely! It now shows a
> dashboard of open patches where you are author/reviewer/committer if
> you are logged in. These patches are ordered & grouped in a hopefully
> useful way. If you're not
On Tue, 4 Mar 2025 at 16:29, Peter Eisentraut wrote:
> Another small complaint: I don't like this style of relative times. (I
> have also complained about it for the buildfarm status in the past.) I
> suppose both styles are useful like 50% of the time, but I'll tell you
> some of my reasoning:
On 04.03.25 02:21, Jelte Fennema-Nio wrote:
6. The "latest email" column now shows "time since" (e.g. 1 week ago)
instead of an exact timestamp. You can still see the exact timestamp
by hovering over the cell.
Another small complaint: I don't like this style of relative times. (I
have also co
On Tue, Mar 4, 2025 at 5:35 AM Álvaro Herrera wrote:
> The idea of this dashboard
> sounds very good to me, but it shouldn't replace the initial page (list
> of commitfests). Maybe put this in a URL such as
> https://commitfest.postgresql.org/you
> or
> https://commitfest.postgresql.org/me
>
On Tue, 4 Mar 2025 at 13:36, Amit Kapila wrote:
>
> On Tue, Mar 4, 2025 at 4:05 PM Álvaro Herrera wrote:
> > I think showing different pages on the same URL depending on whether
> > you're logged in or not is not great UX.
> >
>
> +1. The default should be what we see today, and there should be s
On Tue, Mar 4, 2025 at 4:05 PM Álvaro Herrera wrote:
>
> On 2025-Mar-04, Jelte Fennema-Nio wrote:
>
> > 1. Major change: The homepage is revamped completely! It now shows a
> > dashboard of open patches where you are author/reviewer/committer if
> > you are logged in. These patches are ordered & g
On 2025-Mar-04, Jelte Fennema-Nio wrote:
> 1. Major change: The homepage is revamped completely! It now shows a
> dashboard of open patches where you are author/reviewer/committer if
> you are logged in. These patches are ordered & grouped in a hopefully
> useful way. If you're not logged in it wi
On Tue, 4 Mar 2025 at 10:22, Peter Eisentraut wrote:
> I don't know if I like that. I can see the point of getting to the
> action quicker, but this sort of obscures the hierarchy of the site and
> the data. Before it was like, select a commitfest, select a filter,
> here are some patches. Now
On 04.03.25 02:21, Jelte Fennema-Nio wrote:
1. Major change: The homepage is revamped completely! It now shows a
dashboard of open patches where you are author/reviewer/committer if
you are logged in. These patches are ordered & grouped in a hopefully
useful way. If you're not logged in it will s
41 matches
Mail list logo
