Обсуждение: Upcoming Events on front page
During a SwissPUG meeting, I was recently asked the question, 'Why isn't pgConf.EU on .org?' Upon further investigation,it emerged that several events were missing from the front page of postgresql.org. As of 4 September 2025,the following conferences are displayed in the "Upcoming Events" section: > • 2025-09-04 · PGDay Austria 2025 > • 2025-09-03 – 2025-09-05 · PGConf.Brazil 2025 > • 2025-09-09 · PGDay UK 2025 > • 2025-09-12 · pgDay Lowlands 2025 > • 2025-09-25 · PGDay Napoli 2025 > • 2025-09-29 – 2025-10-01 · PGConf NYC 2025 > • 2025-11-20 · PostGIS Day 2025 When I compare that with the events listed on <https://www.postgresql.org/about/events/>, I notice that three more eventsare missing from the front page between PGConf NYC and PostGIS Day: > 2025-10-17 PG Down Under 2025 > 2025-10-19 PGDay Israel 2025 > 2025-10-21 – 2025-10-24 PGConf.EU 2025 Furthermore, the PGDay Austria event, which is taking place today, has already been moved to the event archive on the dedicatedevents page, even though it is still listed on the front page. Can you explain these discrepancies? TIA Tobias
On 9/4/25 4:06 PM, Tobias Bussmann wrote: > During a SwissPUG meeting, I was recently asked the question, 'Why isn't pgConf.EU on .org?' Upon further investigation,it emerged that several events were missing from the front page of postgresql.org. As of 4 September 2025,the following conferences are displayed in the "Upcoming Events" section: > >> • 2025-09-04 · PGDay Austria 2025 >> • 2025-09-03 – 2025-09-05 · PGConf.Brazil 2025 >> • 2025-09-09 · PGDay UK 2025 >> • 2025-09-12 · pgDay Lowlands 2025 >> • 2025-09-25 · PGDay Napoli 2025 >> • 2025-09-29 – 2025-10-01 · PGConf NYC 2025 >> • 2025-11-20 · PostGIS Day 2025 > > When I compare that with the events listed on <https://www.postgresql.org/about/events/>, I notice that three more eventsare missing from the front page between PGConf NYC and PostGIS Day: > >> 2025-10-17 PG Down Under 2025 >> 2025-10-19 PGDay Israel 2025 >> 2025-10-21 – 2025-10-24 PGConf.EU 2025 > > Furthermore, the PGDay Austria event, which is taking place today, has already been moved to the event archive on the dedicatedevents page, even though it is still listed on the front page. > > Can you explain these discrepancies? There was a long discussion about this when the Recognized Community Conferences guidelines rolled out, and I can't quickly find the thread. The tl;dr is that we agreed to give preference to community conferences on the homepage, but still need to show at least 2 non-recognized events on the page, should more than zero exist. As a result, we also expanded the number of events listed on the homepage from 5 to 7. Thanks, Jonathan
Вложения
> There was a long discussion about this when the Recognized Community Conferences guidelines rolled out, and I can't quicklyfind the thread. The tl;dr is that we agreed to give preference to community conferences on the homepage, but stillneed to show at least 2 non-recognized events on the page, should more than zero exist. Wow, thanks for the explanation! I'm not sure if I like the outcome, but at least this isn't a bug. Thanks Tobias
Вложения
On 9/4/25 4:19 PM, Tobias Bussmann wrote: >> There was a long discussion about this when the Recognized Community Conferences guidelines rolled out, and I can't quicklyfind the thread. The tl;dr is that we agreed to give preference to community conferences on the homepage, but stillneed to show at least 2 non-recognized events on the page, should more than zero exist. > > Wow, thanks for the explanation! I'm not sure if I like the outcome, but at least this isn't a bug. I don't particularly want to re-open the original debate - but - I wouldn't be opposed to further expanding the number of events display on the homepage to 9 or 10. We have more events in PostgreSQL today than we did before. Jonathan
Вложения
On Fri, Sep 5, 2025 at 8:21 PM Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 9/4/25 4:19 PM, Tobias Bussmann wrote:
>> There was a long discussion about this when the Recognized Community Conferences guidelines rolled out, and I can't quickly find the thread. The tl;dr is that we agreed to give preference to community conferences on the homepage, but still need to show at least 2 non-recognized events on the page, should more than zero exist.
>
> Wow, thanks for the explanation! I'm not sure if I like the outcome, but at least this isn't a bug.
I don't particularly want to re-open the original debate - but - I
wouldn't be opposed to further expanding the number of events display on
the homepage to 9 or 10. We have more events in PostgreSQL today than we
did before.
Given the amount of time that has passed since back then, I think it would be fair to discuss the concept again. But a good way to do that is to not start over from the beginning, but to go through the old thread, and then propose a new solution that to at least some level considers the arguments made back then.
//Magnus
On 06.09.25 00:05, Magnus Hagander wrote: > On Fri, Sep 5, 2025 at 8:21 PM Jonathan S. Katz <jkatz@postgresql.org > <mailto:jkatz@postgresql.org>> wrote: > > On 9/4/25 4:19 PM, Tobias Bussmann wrote: > >> There was a long discussion about this when the Recognized > Community Conferences guidelines rolled out, and I can't quickly > find the thread. The tl;dr is that we agreed to give preference to > community conferences on the homepage, but still need to show at > least 2 non-recognized events on the page, should more than zero exist. > > > > Wow, thanks for the explanation! I'm not sure if I like the > outcome, but at least this isn't a bug. > > I don't particularly want to re-open the original debate - but - I > wouldn't be opposed to further expanding the number of events > display on > the homepage to 9 or 10. We have more events in PostgreSQL today > than we > did before. > > Given the amount of time that has passed since back then, I think it > would be fair to discuss the concept again. But a good way to do that is > to not start over from the beginning, but to go through the old thread, > and then propose a new solution that to at least some level > considers the arguments made back then. Ideally, both the algorithm and the discussion that led to it would be documented, like in a footnote or something. This kind of algorithmic highlighting of certain things over other things without further explanation is the kind of thing that people constantly complain about in the realm of social media. We have an opportunity to be more transparent here.
On 9/10/25 1:14 AM, Peter Eisentraut wrote: > On 06.09.25 00:05, Magnus Hagander wrote: >> Given the amount of time that has passed since back then, I think it >> would be fair to discuss the concept again. But a good way to do that >> is to not start over from the beginning, but to go through the old >> thread, and then propose a new solution that to at least some level >> considers the arguments made back then. > > Ideally, both the algorithm and the discussion that led to it would be > documented, like in a footnote or something. > > This kind of algorithmic highlighting of certain things over other > things without further explanation is the kind of thing that people > constantly complain about in the realm of social media. We have an > opportunity to be more transparent here. Well, it was previously documented in the code[1] the original commit message[2][3], though I can't find the original email thread (likely due to not including a ref to it in the commit messages). But what you're getting at is that we could include a small description for how the algorithm works. I'm OK with that, but I'd prefer to put the full explanation on the events page and not the homepage, so we can save home page real estate for things like listing more events. Jonathan [1] https://github.com/postgres/pgweb/blob/master/pgweb/core/views.py#L57 [2] https://github.com/postgres/pgweb/commit/d252bdedf30c235433fed9137aba8db255d5cfb3 [3] https://github.com/postgres/pgweb/commit/5c3f229e44dbca4ecf3950f50a3bcb3d00987d71