MIME-Version: 1.0
References: <1D92AE1C-83A0-4C3D-950C-DBA07422BD89@gmx.net>
 <ffbb8e3a-9def-4532-8e9c-85e4f2a074e8@postgresql.org>
 <F8E3BA26-63ED-4733-AE7F-A8A861FCA39F@gmx.net>
 <058dacc5-c910-494d-a090-7dc492f868c4@postgresql.org>
In-Reply-To: <058dacc5-c910-494d-a090-7dc492f868c4@postgresql.org>
From: Magnus Hagander <magnus@hagander.net>
Date: Sat, 6 Sep 2025 00:05:16 +0200
Message-ID: 
 <CABUevEw55mh=Q-WB0mGsAKUJH05A5Ox8X=OnP8jW8tCfMyUcvA@mail.gmail.com>
Subject: Re: Upcoming Events on front page
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Tobias Bussmann <t.bussmann@gmx.net>, pgsql-www@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000242cfa063e150920"
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevEw55mh%3DQ-WB0mGsAKUJH05A5Ox8X%3DOnP8jW8tCfMyUcvA%40mail.gmail.com>
Precedence: bulk

--000000000000242cfa063e150920
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 5, 2025 at 8:21=E2=80=AFPM Jonathan S. Katz <jkatz@postgresql.o=
rg>
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. T=
he
> tl;dr is that we agreed to give preference to community conferences on th=
e
> 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, bu=
t
> 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

--000000000000242cfa063e150920
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Sep 5, =
2025 at 8:21=E2=80=AFPM Jonathan S. Katz &lt;<a href=3D"mailto:jkatz@postgr=
esql.org">jkatz@postgresql.org</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">On 9/4/25 4:19 PM, Tobias Bussmann wrote:<br>
&gt;&gt; There was a long discussion about this when the Recognized Communi=
ty Conferences guidelines rolled out, and I can&#39;t quickly find the thre=
ad. 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 o=
n the page, should more than zero exist.<br>
&gt; <br>
&gt; Wow, thanks for the explanation! I&#39;m not sure if I like the outcom=
e, but at least this isn&#39;t a bug.<br>
<br>
I don&#39;t particularly want to re-open the original debate - but - I <br>
wouldn&#39;t be opposed to further expanding the number of events display o=
n <br>
the homepage to 9 or 10. We have more events in PostgreSQL today than we <b=
r>
did before.<br><br></blockquote><div><br></div><div>Given the amount of tim=
e 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 begi=
nning, but to go through the old thread, and then propose a new solution th=
at to at least some level considers=C2=A0the arguments made back then.</div=
><div><br></div><div>//Magnus</div><div>=C2=A0</div></div><div dir=3D"ltr" =
class=3D"gmail_signature"><div dir=3D"ltr"></div></div></div>

--000000000000242cfa063e150920--