On Tue, 18 Feb 2025 at 00:38, Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Mon, Feb 17, 2025 at 4:33 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > This looks fantastic. Thanks so much for working on it! And all the
> > other usability improvements too.
>
> +1.
Thanks all, I'm also very happy that it's deployed.
> I very much welcome a more formal release process for the CF app,
> though with shorter feedback cycles.
Do you mean here that you'd like less than two weeks between the
announced staging deploy and prod deploy?
> I like "Useful links that you can use and bookmark", but I'd prefer if
> there was only one link that I needed to bookmark. That is, I'd like
> it if "Your entries in the current commitfest", "Your entries in the
> open commitfest", and "Entries that you are reviewing in current
> commitfest" were all merged into one dashboard view
I think that indeed would be very useful, but also not a small task to
do well. The links were pretty easy to implement, so I went for that
first.
Overall from what I've heard after talking to people there are a few
main use cases for the commitfest app.
1. As a committer/reviewer/submitter, keep track of all the patches
that you are interested in
2. As a reviewer, find new patches (and from the opposite side, have
reviewers find your submitted patches)
3. As a submitter, trigger CFBot runs
4. Get details on a specific patch (does it pass CI, look at a diff in
a web view, check out the change locally).
5. If there's other usecases please let me know.
I don't use it much for 1 myself. I've been mostly using my
"Interesting" label in my email client for tracking interesting
threads. So instead I focussed mostly on improving 4, and a bit of 2
for now. Now that there's some more useful patch info available for
each patch, I probably also want to start keeping track of patches
that I'm interested in, on the cf app.
