Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pqt8a-0006Mv-Rn for pgsql-www@arkaria.postgresql.org; Mon, 24 Apr 2023 10:09:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pqt8Z-0002vd-OQ for pgsql-www@arkaria.postgresql.org; Mon, 24 Apr 2023 10:09:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pqt8Z-0002vU-Ez for pgsql-www@lists.postgresql.org; Mon, 24 Apr 2023 10:09:35 +0000 Received: from dd39330.kasserver.com ([85.13.143.17]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pqt8V-001brD-Fx for pgsql-www@lists.postgresql.org; Mon, 24 Apr 2023 10:09:34 +0000 Received: from [192.168.1.247] (unknown [145.224.74.4]) by dd39330.kasserver.com (Postfix) with ESMTPSA id 1EFCE4940270; Mon, 24 Apr 2023 12:09:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proopensource.eu; s=kas202212221024; t=1682330968; bh=lnQ7cqwKx2PtlL2ebL6FVCuMP6GX8ozCYnrpzOuhkhM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=PACKMaIfcgkMWxvfo9yPGDUD8k3e94mjZ7GYvmBYzrNKTiERQmcrqDpzvbzqJ9Dmx G+qLqKK+m/ho0EgeIbfFMqiORBnJ6cr6KP59sNaxjMRcYVzjyp2WS4HJIapjrhDCgX EiL+nLUbTp6d0oW3dS7ClDvjOf8HsWC5ZKtqLFxOGgfHhj6cgfvgGS3IAIV/625kLI faxCNTYaAuOPbsrQ2lO1rQVALChEhRnBgUQt6DG+RqOeeQOifRHVPIZgGlg+Bd71WX 6i9U7tLSGChg4iXNhTMvEA+VPlNDQUbjq0wcceImmn2pSdpoBNfR9KB876f6bFOtH9 4H44ito/uQj8A== Message-ID: <5973cf36-8a71-8057-4ab0-714d4d2563e4@ProOpenSource.eu> Date: Mon, 24 Apr 2023 12:09:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Patch to clean up and add missing GSoC pages Content-Language: de-DE, en-US To: Daniel Gustafsson , "Jonathan S. Katz" Cc: pgsql-www@lists.postgresql.org References: <31f2c0fc-3220-2bb0-53b0-6e89414189b1@ProOpenSource.eu> From: =?UTF-8?Q?Stefanie_Janine_St=c3=b6lting?= Organization: =?UTF-8?Q?ProOpenSource_O=c3=9c?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: / List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi there, I have been thinking about how to have better links, too. An easy solution might be to just link to the Wiki for year, the GSoC page is about. Every GSoC page itself might link to a certain amount of recent years, for example two. That way you can go to previous years in nice way. I can add the two points fast. The goal for this patch has not been, to have everything replaced at once, it was about filling up the information that is available on Googles GSoC pages and to fill the gap. And in addition to have links to Google GSoC sites, that do work instead of ending on an empty page (if you are lucky). In a next step I would also like to go back on GSoC pages as far as possible, meaning, what I can get on information of Google as they changed the links. Some pages might be available on archive pages, which I will check, too. I believe it would also be useful, to have more information about the projects on our pages. Namely the project descriptions on Google GSoC pages. Cheers, Stefanie -- ProOpenSource OÜ Director Stefanie Janine Stölting Sepapaja 6 Tallinn 15551 Estonia Registry Code: 16258841 VAT: EE102386758 Web: https://ProOpenSource.eu On 24.04.23 10:33, Daniel Gustafsson wrote: >> On 22 Apr 2023, at 20:59, Jonathan S. Katz wrote: >> >> Hi Stefanie, >> >> On 4/21/23 5:27 AM, Stefanie Janine Stölting wrote: >>> Hi there, >>> Attached you'll find a patch containing changes on the GSoC pages. >> 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 >