New commitfest app release on August 19th
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\
On Fri, 8 Aug 2025 at 09:19, Jelte Fennema-Nio <me@jeltef.nl> wrote:
I'll release all of it on August 19th.
As always, you can see the changes live here:
https://commitfest-test.postgresql.org/ (username and password are "pgtest")
Feedback is welcome. Especially if you think something looks off or
buttons don't work (likely caused by the Bootstrap 5 upgrade). I think
I visited all the pages and clicked all the buttons, but I might have
missed a few.
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)
On Fri, 8 Aug 2025 at 11:55, Álvaro Herrera <alvherre@kurilemu.de> wrote:
Nice stuff.
Thanks for all the feedback. It's super helpful.
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.)
Indeed I just moved the box around this time. It's probably not too
hard to allow searching globally. So I created an issue to track it:
https://github.com/postgres/pgcommitfest/issues/92
I hope more widespread use of tags will one day release us from having
the "Topic" categorization, which is not all that useful anymore.
Yeah, that's something I intend to try out soonish.
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.
It's not entirely trivial I guess: What CF should those buttons link
to? The In Progress CF, the Open CF or the last CF that
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)
I think that's fair. How about I simply remove the closed patches
section in Draft CFs completely and make sure a closed/completed patch
is always moved to the open CF? Or do you see any reason to keep the
section?
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.
I'll see if I can make the styling of the buttons a bit better.
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.
Pushed a fix for that now.
On Fri, 8 Aug 2025 at 09:19, Jelte Fennema-Nio <me@jeltef.nl> 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
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.
On Mon, Aug 11, 2025 at 9:39 AM Jelte Fennema-Nio <me@jeltef.nl> wrote:
On Fri, 8 Aug 2025 at 11:55, Álvaro Herrera <alvherre@kurilemu.de> wrote:
Nice stuff.
...
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.It's not entirely trivial I guess: What CF should those buttons link
to? The In Progress CF, the Open CF or the last CF that
Could be any of these, on a page with tabs or links to others ?
On Aug 19, 2025, at 15:03, Jelte Fennema-Nio <me@jeltef.nl> wrote:
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.
The new UI looks nicer.
But I now aways get “Error 503 Backend fetch failed” when I click on any email link or attachment link.
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
On Tue, 19 Aug 2025 at 09:18, Chao Li <li.evan.chao@gmail.com> wrote:
But I now aways get “Error 503 Backend fetch failed” when I click on any email link or attachment link.
Seems the web-archives are having issues. That's unfortunate timing,
but unrelated to the commitfest app deploy.
On Tue, Aug 19, 2025 at 03:18:22PM +0800, Chao Li wrote:
But I now aways get “Error 503 Backend fetch failed” when I click on
any email link or attachment link.
That happens from time to time. This is unrelated to the CF app
itself.
--
Michael
On Tue, Aug 19, 2025 at 2:04 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.
I found the font difficult to read, like it's not rendering smoothly
on my system. While the text looked smaller, I had to zoom out to 75%
in my browser to get the whole table to fit on screen -- anyone else?
(I didn't see font in the list of changes...)
--
John Naylor
Amazon Web Services
On Tue, 19 Aug 2025 at 09:31, John Naylor <johncnaylorls@gmail.com> wrote:
I found the font difficult to read, like it's not rendering smoothly
on my system. While the text looked smaller, I had to zoom out to 75%
in my browser to get the whole table to fit on screen -- anyone else?
(I didn't see font in the list of changes...)
That's a difference between Bootstrap 3 and Bootstrap 5 I guess.
Before font-family was set to this:
"Helvetica Neue", Helvetica, Arial, sans-serif
Now it's set to this much longer fallback string:
system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", "Noto
Sans", "Liberation Sans", Arial, sans-serif, "Apple Color Emoji",
"Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"
Can you check what font is actually being used on your system like this[1]https://devtoolstips.org/tips/en/list-used-fonts/?
On Tue, Aug 19, 2025 at 4:15 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
Now it's set to this much longer fallback string:
system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", "Noto
Sans", "Liberation Sans", Arial, sans-serif, "Apple Color Emoji",
"Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"Can you check what font is actually being used on your system like this[1]?
"Rendered fonts" shows:
Family name: Cantarell (Fontations)
PostScript name: Cantarell-Regular
Font origin: Local file(80 glyphs)
--
John Naylor
Amazon Web Services
On 2025-Aug-19, Jelte Fennema-Nio wrote:
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.
Hmm, you seem to have changed the main page title from "Commitfests" to
"CommitFests". There is a subjective argument that the uppercase F in
the middle of that word looks terrible for some reason, but there's also
the objective argument that the change on that particular page broke the
pginfra monitoring for the page.
Can you please put that lowercase "f" back? Here's a quick patch. (I
think several people would not be pleased if the uppercase F were to
propagate much more.)
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Attachments:
0001-Proper-spelling-is-Commitfest-with-lowercase-f.patchtext/x-diff; charset=utf-8Download
From 27f475f27511073900e8fc45332ce5d11e6bbdf8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81lvaro=20Herrera?= <alvherre@kurilemu.de>
Date: Tue, 19 Aug 2025 11:24:45 +0200
Subject: [PATCH] Proper spelling is "Commitfest", with lowercase 'f'
---
README.md | 2 +-
pgcommitfest/commitfest/templates/base.html | 2 +-
pgcommitfest/commitfest/templates/help.html | 18 +++++++++---------
pgcommitfest/commitfest/templates/home.html | 2 +-
pgcommitfest/commitfest/views.py | 2 +-
5 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/README.md b/README.md
index f96fdc9..0e85323 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# CommitFest
+# Commitfest
This application manages commitfests for the PostgreSQL community.
diff --git a/pgcommitfest/commitfest/templates/base.html b/pgcommitfest/commitfest/templates/base.html
index 8834db7..445fcc3 100644
--- a/pgcommitfest/commitfest/templates/base.html
+++ b/pgcommitfest/commitfest/templates/base.html
@@ -47,7 +47,7 @@
</a>
<ul class="dropdown-menu" aria-labelledby="moreDropdown">
<li><a class="dropdown-item" href="/activity/">Activity Log</a></li>
- <li><a class="dropdown-item" href="/commitfest_history/">All CommitFests</a></li>
+ <li><a class="dropdown-item" href="/commitfest_history/">All Commitfests</a></li>
</ul>
</li>
<li class="nav-item">
diff --git a/pgcommitfest/commitfest/templates/help.html b/pgcommitfest/commitfest/templates/help.html
index 7a4f198..c99944a 100644
--- a/pgcommitfest/commitfest/templates/help.html
+++ b/pgcommitfest/commitfest/templates/help.html
@@ -1,23 +1,23 @@
{%extends "base.html"%}
{%block contents%}
<p>
- This is the "CommitFest app", the website where the PostgreSQL community tracks proposed changes to PostgreSQL. If you're familiar with GitHub, then this website fulfills a similar purpose to the list of Pull Requests (PRs) on GitHub repo. The most important difference is that the CommitFest app is not the "source of truth", instead the PostgreSQL mailinglists are. The "CommitFest app" is simply a tool to help the communtiy keep track of changes proposed on the mailinglist in an organized manner. Below are the most important concepts that you should know about when using the CommitFest app.
+ This is the "Commitfest app", the website where the PostgreSQL community tracks proposed changes to PostgreSQL. If you're familiar with GitHub, then this website fulfills a similar purpose to the list of Pull Requests (PRs) on GitHub repo. The most important difference is that the Commitfest app is not the "source of truth", instead the PostgreSQL mailinglists are. The "Commitfest app" is simply a tool to help the communtiy keep track of changes proposed on the mailinglist in an organized manner. Below are the most important concepts that you should know about when using the Commitfest app.
</p>
- <h2>CommitFest</h2>
+ <h2>Commitfest</h2>
<p>
- PostgreSQL development is organized into "CommitFests" (often abbreviated to "CF"). Each CommitFest contains a list of entries called <a href="#patch">patches</a> (similar to PRs, see below for details). The main purpose of CommitFests are to make sure patches that people are interested in are not forgotten about, as well as running CI (aka CFBot) on these patches. Each CommitFest has a period where it is "Open", in which people can add patches to the CommitFest. This "Open" period is followed by an "In Progress" period, in which the idea is that committers and reviewers focus on reviewing and committing the patches in this "In Progress" CommitFest. At the end of the month a CommitFest gets "Closed" (and stays closed forever). Any not yet committed patches can be moved to the following "Open" CommitFest by their authors, to try again in the next cycle. Having these timebound periods has several benefits:
+ PostgreSQL development is organized into "Commitfests" (often abbreviated to "CF"). Each Commitfest contains a list of entries called <a href="#patch">patches</a> (similar to PRs, see below for details). The main purpose of Commitfests are to make sure patches that people are interested in are not forgotten about, as well as running CI (aka CFBot) on these patches. Each Commitfest has a period where it is "Open", in which people can add patches to the Commitfest. This "Open" period is followed by an "In Progress" period, in which the idea is that committers and reviewers focus on reviewing and committing the patches in this "In Progress" Commitfest. At the end of the month a Commitfest gets "Closed" (and stays closed forever). Any not yet committed patches can be moved to the following "Open" Commitfest by their authors, to try again in the next cycle. Having these timebound periods has several benefits:
<ol>
<li>It gives a regular cadence of development to people who like to have this.</li>
<li>It provides a natural age-out mechanism for patches that the submitter has lost interest in.</li>
<li>It provides an easy way for reviewers/committers to prioritize which patches to review.</li>
</ol>
- This <b>does not</b> mean that patches are only committed during a CommitFest, nor that people will only respond on the mainlinglist to patches in the "In Progress" CommitFest.
+ This <b>does not</b> mean that patches are only committed during a Commitfest, nor that people will only respond on the mainlinglist to patches in the "In Progress" Commitfest.
</p>
- <p>There are 5 CommitFests per year. The first one is "In Progress" in <em>July</em> and starts the nine months feature development cycle of PostgreSQL. The next three are "In Progress" in <em>September</em>, <em>November</em> and <em>January</em>. The last CommitFest of the feature development cycle is "In Progress" in <em>March</em>, and ends a when the feature freeze starts. The exact date of the feature freeze depends on the year, but it's usually in early April.</p>
+ <p>There are 5 Commitfests per year. The first one is "In Progress" in <em>July</em> and starts the nine months feature development cycle of PostgreSQL. The next three are "In Progress" in <em>September</em>, <em>November</em> and <em>January</em>. The last Commitfest of the feature development cycle is "In Progress" in <em>March</em>, and ends a when the feature freeze starts. The exact date of the feature freeze depends on the year, but it's usually in early April.</p>
<h2>Patches</h2>
<p>
- A "patch" is a bit of an overloaded term in the PostgreSQL community. Email threads on the mailing list often contain "patch files" as attachments, such a file is often referred to as a "patch". A single email can even contain multiple related "patch files", which are called a "patchset". However, in the context of a CommitFest app a "patch" usually means a "patch entry" in the CommitFest app. Such a "patch entry" is a reference to a mailinglist thread on which change to PostgreSQL has been proposed, by someone sending an email that contain one or more "patch files". The CommitFest app will automatically detect new versions of the patch files and update the "patch entry" accordingly.
+ A "patch" is a bit of an overloaded term in the PostgreSQL community. Email threads on the mailing list often contain "patch files" as attachments, such a file is often referred to as a "patch". A single email can even contain multiple related "patch files", which are called a "patchset". However, in the context of a Commitfest app a "patch" usually means a "patch entry" in the Commitfest app. Such a "patch entry" is a reference to a mailinglist thread on which change to PostgreSQL has been proposed, by someone sending an email that contain one or more "patch files". The Commitfest app will automatically detect new versions of the patch files and update the "patch entry" accordingly.
</p>
<p>
There are three "Active" categories of patch status:
@@ -38,7 +38,7 @@
<h2>Drafts</h2>
<p>
- Appart from the regular CommitFests, there is also a "Drafts" CommitFest that is used to collect patches for new features that are not yet ready for general reviewing. There are various reasons why a patch might not be ready for general reviewing but the author still wants to track it publicly in the "CommitFest app", this is usually due to the combination of one of the following reasons:
+ Appart from the regular Commitfests, there is also a "Drafts" Commitfest that is used to collect patches for new features that are not yet ready for general reviewing. There are various reasons why a patch might not be ready for general reviewing but the author still wants to track it publicly in the "Commitfest app", this is usually due to the combination of one of the following reasons:
<ul>
<li>The author has temporarily lost interest, but expects to come back in the future.</li>
<li>The author does not want to forget abuot </li>
@@ -46,7 +46,7 @@
<li>The author wants to have CI run on the patch, while they are polishing it further</li>
<li>The author would like to be notified when the patch is in need of a rebase</li>
</ul>
- Like regular CommitFests, a Draft CommitFest also has an "Open" period and a "Closed" state, but it has no "In Progress" period. The "Open" period for a Draft CommitFest last lasts a year. When the last CommitFest of the development cycle becomes "In Progress", the Draft CommitFest for that PostgreSQL version is closed, and a new one is immediately opened for the next PostgreSQL release.
+ Like regular Commitfests, a Draft Commitfest also has an "Open" period and a "Closed" state, but it has no "In Progress" period. The "Open" period for a Draft Commitfest last lasts a year. When the last Commitfest of the development cycle becomes "In Progress", the Draft Commitfest for that PostgreSQL version is closed, and a new one is immediately opened for the next PostgreSQL release.
</p>
- <p>Another difference between Draft CommitFests and regular CommitFests is that Draft CommitFests don't list resolved patches.</p>
+ <p>Another difference between Draft Commitfests and regular Commitfests is that Draft Commitfests don't list resolved patches.</p>
{%endblock%}
diff --git a/pgcommitfest/commitfest/templates/home.html b/pgcommitfest/commitfest/templates/home.html
index d5f060f..d0fbade 100644
--- a/pgcommitfest/commitfest/templates/home.html
+++ b/pgcommitfest/commitfest/templates/home.html
@@ -7,7 +7,7 @@
</p>
{% endif %}
- <h3>CommitFests</h3>
+ <h3>Commitfests</h3>
<p>
<table class="table commitfests-table" style="table-layout: auto; width: auto;">
<style>
diff --git a/pgcommitfest/commitfest/views.py b/pgcommitfest/commitfest/views.py
index 35e395c..7e99b30 100644
--- a/pgcommitfest/commitfest/views.py
+++ b/pgcommitfest/commitfest/views.py
@@ -173,7 +173,7 @@ def help(request):
request,
"help.html",
{
- "title": "What is the CommitFest app?",
+ "title": "What is the Commitfest app?",
},
)
--
2.39.5
On Fri, Aug 8, 2025 at 4:20 PM Jelte Fennema-Nio <me@jeltef.nl> 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.
Thanks for your continued work on improving the commitfest app!
I pushed the patch registered in PG19-2 and tried to change its status
to Committed by clicking [Change Status] -> [Committed] in its
commitfest page [1]https://commitfest.postgresql.org/patch/5945/. This worked fine until yesterday, but starting
today, nothing happens when I click it. Could this be related to
today's new release?
Regards,
[1]: https://commitfest.postgresql.org/patch/5945/
--
Fujii Masao
On Tue, 19 Aug 2025 at 12:08, Fujii Masao <masao.fujii@gmail.com> wrote:
I pushed the patch registered in PG19-2 and tried to change its status
to Committed by clicking [Change Status] -> [Committed] in its
commitfest page [1]. This worked fine until yesterday, but starting
today, nothing happens when I click it. Could this be related to
today's new release?
Oops, that was indeed accidentally broken. It's fixed now.
On Tue, 19 Aug 2025 at 11:31, Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Aug-19, Jelte Fennema-Nio wrote:
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.Hmm, you seem to have changed the main page title from "Commitfests" to
"CommitFests". There is a subjective argument that the uppercase F in
the middle of that word looks terrible for some reason, but there's also
the objective argument that the change on that particular page broke the
pginfra monitoring for the page.Can you please put that lowercase "f" back? Here's a quick patch. (I
think several people would not be pleased if the uppercase F were to
propagate much more.)
Applied and deployed your patch to make the monitoring happy. Could
you add me to whatever list is necessary for me to receive these
notifications too?
I'm wondering what other people consider the correct spelling though.
The wiki[1]https://wiki.postgresql.org/wiki/CommitFest has been using the spelling with the capital F. As well as
the code for the commitfest app.
Hi
,
While the text looked smaller, I had to zoom out to 75%
in my browser to get the whole table to fit on screen -- anyone else?
(I didn't see font in the list of changes...)
Same here (Firefox 141, Ubuntu 24.04). I had to scale the page to 90%.
It doesn't bother me too much - just wanted to share in case the
intent was to make the table screen-wide. It seems to be slightly
wider in practice.
--
Best regards,
Aleksander Alekseev
On Tue, 19 Aug 2025 at 12:06, Jelte Fennema-Nio <me@jeltef.nl> wrote:
On Tue, 19 Aug 2025 at 11:31, Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Aug-19, Jelte Fennema-Nio wrote:
This is now deployed to production. Please let me know if some
behaviour got broken or styling looks weird.Hmm, you seem to have changed the main page title from "Commitfests" to
"CommitFests". There is a subjective argument that the uppercase F in
the middle of that word looks terrible for some reason, but there's also
the objective argument that the change on that particular page broke the
pginfra monitoring for the page.Can you please put that lowercase "f" back? Here's a quick patch. (I
think several people would not be pleased if the uppercase F were to
propagate much more.)Applied and deployed your patch to make the monitoring happy. Could
you add me to whatever list is necessary for me to receive these
notifications too?I'm wondering what other people consider the correct spelling though.
The wiki[1] has been using the spelling with the capital F. As well as
the code for the commitfest app.
In the earliest conversations I can find about the idea on -core, we
actually used commit-fest. However, I would say Commitfest is correct, as
that's what we've used for the name on the site for years.
The URL above is a redirect to https://wiki.postgresql.org/wiki/Commitfest
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
On Tue, Aug 19, 2025 at 7:57 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
On Tue, 19 Aug 2025 at 12:08, Fujii Masao <masao.fujii@gmail.com> wrote:
I pushed the patch registered in PG19-2 and tried to change its status
to Committed by clicking [Change Status] -> [Committed] in its
commitfest page [1]. This worked fine until yesterday, but starting
today, nothing happens when I click it. Could this be related to
today's new release?Oops, that was indeed accidentally broken. It's fixed now.
Thanks for the fix! I was able to change the status to Committed successfully.
Regards,
--
Fujii Masao
Aleksander Alekseev <aleksander@tigerdata.com> writes:
While the text looked smaller, I had to zoom out to 75%
in my browser to get the whole table to fit on screen -- anyone else?
(I didn't see font in the list of changes...)
Same here (Firefox 141, Ubuntu 24.04). I had to scale the page to 90%.
For me, with Safari on macOS, the font does look a bit different but
not objectionably so. But I too notice that the tables of patches
seem significantly wider than before. If I zoom out enough to fit
the whole table width in my usual browser window, the text is almost
unreadably small. The tables were a bit wider than screen width
already, but it feels like they changed significantly.
regards, tom lane
On Tue, 19 Aug 2025 at 16:27, Tom Lane <tgl@sss.pgh.pa.us> wrote:
For me, with Safari on macOS, the font does look a bit different but
not objectionably so. But I too notice that the tables of patches
seem significantly wider than before. If I zoom out enough to fit
the whole table width in my usual browser window, the text is almost
unreadably small. The tables were a bit wider than screen width
already, but it feels like they changed significantly.
I deployed a change now where the font-size is changed back to 14px
again, and I removed "system-ui" font from the font list. I hope that
solves the difficult to read fonts and larger tables issues. Feedback
welcome, since this is definitely a thing that difference based on the
machine/screen/OS.
On 2025-Aug-19, Jelte Fennema-Nio wrote:
Applied and deployed your patch to make the monitoring happy.
Many thanks! It is indeed happier.
Could you add me to whatever list is necessary for me to receive these
notifications too?
Hmm, I don't know that I can do that. It's kinda hardcoded to pginfra
sysadmins and adding exceptions to the multiple layers of config file
generation looks quite arcane. I'm not touching that for now, sorry.
I'm wondering what other people consider the correct spelling though.
The wiki[1] has been using the spelling with the capital F. As well as
the code for the commitfest app.
I'm happy to assign blame the capital F to people who's no longer with
the project, so they don't have to defend the choice.
(Actually, it may have been me.)
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Siempre hay que alimentar a los dioses, aunque la tierra esté seca" (Orual)
On Wed, Aug 20, 2025 at 12:31 AM Jelte Fennema-Nio <me@jeltef.nl> wrote:
I deployed a change now where the font-size is changed back to 14px
again, and I removed "system-ui" font from the font list. I hope that
solves the difficult to read fonts and larger tables issues. Feedback
welcome, since this is definitely a thing that difference based on the
machine/screen/OS.
The font is much better, thanks!
The table still only fits at 80%, but I think even that would be
tolerable if ID were put at the end of the row. I've never needed the
ID by itself, and if I did I could mouse-over the patch link.
--
John Naylor
Amazon Web Services
On Fri, 8 Aug 2025 at 12:50, Jelte Fennema-Nio <me@jeltef.nl> 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\
While using the CommitFest interface to send a private mail, I noticed
that the confirmation checkbox ("Check to confirm sending") does not
appear as a standard small tick box. Instead, it renders as a long
horizontal box across the page. The functionality still works, but the
display looks incorrect.
Regards,
Vignesh
We just witnessed something weird with a patch that's perhaps a bug in
the workflow for detecting attachments. Patch in question was
https://commitfest.postgresql.org/patch/5972/
1. patch was in CF19-2
2. patch needed rebase.
3. Mario sent a new mail with rebased git-format-patch to the thread
4. patch continued to need rebase. In fact, it appeared as if the thread
info was not updated at all.
5. Mario moved the CF item to CF19-3
6. Nothing appeared to change, i.e. the thread display said that the
last email was from Peter, ignoring the new email.
7. I detached the thread from the CF item, then attached the thread
again. This time it showed both messages, but the attachment list
continued to show only the old one, ignoring the new patch.
Any thoughts? One idea is to delete the CF item and create it afresh :-)
I *suspect* that the thread-processor ignored the attachment because of
CF19-2 being dead, but had already imported the email message; and then
when the patch was moved to CF19-3, the new email was not processed
again so the attachment was again not seen. Does that make sense?
Thanks!
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Postgres is bloatware by design: it was built to house
PhD theses." (Joey Hellerstein, SIGMOD annual conference 2002)
On Wed, Aug 20, 2025 at 10:36 AM John Naylor <johncnaylorls@gmail.com> wrote:
On Wed, Aug 20, 2025 at 12:31 AM Jelte Fennema-Nio <me@jeltef.nl> wrote:
I deployed a change now where the font-size is changed back to 14px
again, and I removed "system-ui" font from the font list. I hope that
solves the difficult to read fonts and larger tables issues. Feedback
welcome, since this is definitely a thing that difference based on the
machine/screen/OS.The font is much better, thanks!
The table still only fits at 80%, but I think even that would be
tolerable if ID were put at the end of the row. I've never needed the
ID by itself, and if I did I could mouse-over the patch link.
I just noticed something interesting:
https://commitfest.postgresql.org/57/
is still too small per my complaint above, but
https://commitfest.postgresql.org/58/
looks just fine at 100% browser zoom. It looks like the biggest
(only?) difference is the width of the "Patch column".
--
John Naylor
Amazon Web Services
On Wed, 7 Jan 2026 at 10:53, John Naylor <johncnaylorls@gmail.com> wrote:
I just noticed something interesting:
https://commitfest.postgresql.org/57/
is still too small per my complaint above, but
https://commitfest.postgresql.org/58/
looks just fine at 100% browser zoom. It looks like the biggest
(only?) difference is the width of the "Patch column".
I've pushed some CSS to staging to do a bit more aggressive wrapping
if stuff doesn't fit in the table (the reason it overflowed seemed to
be long usernames and long single words in patch descriptions). Can
you double check if that solves the problem for you:
https://commitfest-test.postgresql.org/ (username and password are "pgtest")
If so I'll deploy it together with the other changes on staging in ~2 weeks.
On Wed, Jan 7, 2026 at 8:54 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
I've pushed some CSS to staging to do a bit more aggressive wrapping
if stuff doesn't fit in the table (the reason it overflowed seemed to
be long usernames and long single words in patch descriptions). Can
you double check if that solves the problem for you:https://commitfest-test.postgresql.org/ (username and password are "pgtest")
If so I'll deploy it together with the other changes on staging in ~2 weeks.
Works for me, thanks!
--
John Naylor
Amazon Web Services