Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\))
Subject: Re: Patch to clean up and add missing GSoC pages
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <f1cd08da-9578-7aa5-5658-26e0ca36b6f1@postgresql.org>
Date: Mon, 24 Apr 2023 10:33:18 +0200
Cc: =?utf-8?Q?Stefanie_Janine_St=C3=B6lting?= <stefanie@ProOpenSource.eu>,
 pgsql-www@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C69ACB33-86A2-404E-B6A3-43580F933E97@yesql.se>
References: <31f2c0fc-3220-2bb0-53b0-6e89414189b1@ProOpenSource.eu>
 <f1cd08da-9578-7aa5-5658-26e0ca36b6f1@postgresql.org>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/C69ACB33-86A2-404E-B6A3-43580F933E97%40yesql.se>
Precedence: bulk

> On 22 Apr 2023, at 20:59, Jonathan S. Katz <jkatz@postgresql.org> =
wrote:
>=20
> Hi Stefanie,
>=20
> On 4/21/23 5:27 AM, Stefanie Janine St=C3=B6lting wrote:
>> Hi there,
>> Attached you'll find a patch containing changes on the GSoC pages.
>=20
> Thanks for submitting this!

Seconded!

> I'm not sure where these pages are linkable from currently. The only =
link I see is to the wiki from the developers page[1], but we don't have =
any more links back to the .org page. IIRC, this was done in part due to =
what you've raised with this patchset, i.e. the content goes stale and =
requires someone to actively maintain it.

It's currently not linked at all, but searching for GSoC on the site =
leads to
/summerofcode/ which is in a sad state now.

> I agree that the timeline is useful. Maybe we put that on the =
developers page, since it seems all of the other content is available on =
the wiki? That way, we can retire the .org page.

I would prefer to actively maintain the .org page as the entry point for =
GSoC
and leave the Wiki for the projects and other things which changes more
frequently.  The current maintainence overhead is to change the list of =
admins
and mentors as well as add the past year, and that seems quite =
manageable.

I do however think we should keep the timeline on /summerofcode/ and not =
on
each individual yearly archive page (the fact that newly added pages in =
the
patch has the timeline to 2008 while the main page goes to 2006 =
highlights
this).

We can work on where to link to this as a separate step, but to clean up =
the
current state I think we should go ahead with this patch.  Reading =
through it
can't spot any markup errors.

--
Daniel Gustafsson