Re: Next commitfest app release is planned for March 18th - Mailing list pgsql-hackers

From Jacob Brazeal
Subject Re: Next commitfest app release is planned for March 18th
Date
Msg-id CA+COZaBsiZ2VgLdTWK2G3dXinLYNxokez0r_JNKwYMn0h3NQBA@mail.gmail.com
Whole thread Raw
In response to Re: Next commitfest app release is planned for March 18th  (Jelte Fennema-Nio <me@jeltef.nl>)
Responses Re: Next commitfest app release is planned for March 18th
List pgsql-hackers
> 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, or even
> week to week. But I just might. In any case I'm glad that somebody is
> experimenting with it.

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
* Help you find threads that need a review
* Help you find threads to commit, if you're a committer.

I think the UX is a bit confusing right now and it might not be obvious how to do all of these things. For example,
I think your default view right now is mostly showing you patches you wrote, which is a bit of an accident (if you
scroll down, you'll see some patches you didn't author, but are probably relevant to you.)

I think we can fix all of this up in the UX, but my question to you might be:
* What would a good default view be?
* What filters would be useful to you?
* How could we optimize your patch-review workflow, in general?


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: scalability bottlenecks with (many) partitions (and more)
Next
From: Andres Freund
Date:
Subject: Re: scalability bottlenecks with (many) partitions (and more)