Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h07ju-0006g2-G4 for pgsql-www@arkaria.postgresql.org; Sat, 02 Mar 2019 16:43:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h07js-0006c8-U7 for pgsql-www@arkaria.postgresql.org; Sat, 02 Mar 2019 16:43:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h07js-0006c1-OU for pgsql-www@lists.postgresql.org; Sat, 02 Mar 2019 16:43:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h07jm-0008WH-3f for pgsql-www@lists.postgresql.org; Sat, 02 Mar 2019 16:43:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x22GhcDP018941; Sat, 2 Mar 2019 11:43:38 -0500 From: Tom Lane To: Stefan Kaltenbrunner cc: Magnus Hagander , PostgreSQL WWW Subject: Re: Namespace projects.postgresql.org In-reply-to: References: Comments: In-reply-to Stefan Kaltenbrunner message dated "Sat, 02 Mar 2019 10:02:32 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18939.1551545018.1@sss.pgh.pa.us> Date: Sat, 02 Mar 2019 11:43:38 -0500 Message-ID: <18940.1551545018@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stefan Kaltenbrunner writes: > Is this proposal also for cleaning up the old gborg and pgfoundry data > on our file-mirrors (ie: http://ftp.postgresql.org/pub/projects/) or do > we want to keep those? Are those actually just mirrors, or is it likely that they're now the only accessible copies of that stuff? I'd be kind of inclined to keep such data just for archival reasons. Doesn't mean it has to be easily accessible of course, and we should make sure it's presented as historical rather than current projects. regards, tom lane