On 2025-Aug-08, Jelte Fennema-Nio wrote: > Thanks to the Claude Code AI tool I was able to get some boring > cleanup done on the CF app in not that much time. I'll release all of > it on August 19th. > > List of the changes: > - Update to Bootstrap 5 for more modern visual look and better default > contrast of a bunch of UI elements. > - Add a navigation bar at the top of the page, including a "Contribute > on GitHub" button which links to the CF app repo. > - Move the dashboard to the homepage under the list of commitfests. > - Much better tag selector, which shows the tag descriptions and > colors. (descriptions are also searchable). > - Bugfix where draft patches would show in the wrong section in the > personal dashboard > - Nicer sorting icons for the commitfest columns (exact icon depends > on the column) > - Show Search/Filter options by default > - Improved the typography of date ranges by using an en-dash\
Nice stuff. I tried the search, works great, hadn't noticed it before though now I see it was there already. Maybe the result page could be improved still, for instance https://commitfest-test.postgresql.org/search/?searchterm=psql shows a long list of patches in which it's hard to see which ones are current, which were Committed, which ones were Returned with Feedback. (The latter is extremely useful to find old items that were neglected -- I do that all the time, manually, very annoying.) I hope more widespread use of tags will one day release us from having the "Topic" categorization, which is not all that useful anymore. Two minor comments: the tags in the patch page https://commitfest-test.postgresql.org/patch/5501/ are not clickable, so I can't go to other patches containing the same tags as this one. This sounds like a trivial fix. Tags are already clickable in other pages. The other one I noticed while looking at the prod Draft-CF a couple of days ago. Here: https://commitfest-test.postgresql.org/54/ I think the "Closed patches" in the draft CF should not list the patches that were moved to a future non-draft CF -- that's clutter and serves no purpose. It still makes sense to list the Draft-CF in the "Status" section of the patch page itself. (Eh, now I notice that the help page says at the bottom "Another difference between Draft CommitFests and regular CommitFests is that Draft CommitFests don't list resolved patches." which is kinda not true) Not a fan of the high-contrast buttons (the new black/white elements in the navigation bar). It feels odd to have everything in gray, except a too-notorious blue Github button. IMO that button is also too wide -- if I keep the browser window of the same width I typically use (half the screen) then the menu at the top disappears and is replaced with the hamburger button, and so becomes unusable. Many thanks for working on this, -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "No nos atrevemos a muchas cosas porque son difíciles, pero son difíciles porque no nos atrevemos a hacerlas" (Séneca)
