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 1h4Rh7-0004Ia-UO for pgsql-www@arkaria.postgresql.org; Thu, 14 Mar 2019 14:50: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 1h4Rh6-0006bn-LX for pgsql-www@arkaria.postgresql.org; Thu, 14 Mar 2019 14:50:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4Rh6-0006bg-CW for pgsql-www@lists.postgresql.org; Thu, 14 Mar 2019 14:50:52 +0000 Received: from mail-lj1-x243.google.com ([2a00:1450:4864:20::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4Rh3-00028B-DM for pgsql-www@lists.postgresql.org; Thu, 14 Mar 2019 14:50:51 +0000 Received: by mail-lj1-x243.google.com with SMTP id z20so5080886ljj.10 for ; Thu, 14 Mar 2019 07:50:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xtn4WANmuhbCByEBvsuaroq7trGiIV63cAH1KXFtNA8=; b=HZ/i9hckqrvCV7KrlcSYJWXfKN3AN1CVLnQzr6sXahGld8cznvtbq6449EbyK47s1R SNXH7JiW0Wb/yog4etTIDcNWbhEATQz6hZ+guzGFxbdTg2S89SlbfsdmgFL3TY5RKIMh QbDi0ajb4EFfLkIivbmXoRz5x/2kI3FG3tAdxgxPWyUpePyjkyKxUk9uu/Y0ImYa235J tDz35wmS5ac5HJskLf9N4dFtToYp7VhidmSSdN4kGEZgHXBBVaYqVlPKGy0Fu+IKZpwd OtqeM61MhiCvcZeqfnC4qHfBl3v4yiE4XlZWEve/uiMI2U90NM3ENvWbN1EKs8100dKg vnPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xtn4WANmuhbCByEBvsuaroq7trGiIV63cAH1KXFtNA8=; b=QHdnoskR9OV8eDTANjAI3NiEVtQsFA7hu6UujcfNK1jQSroZdpr1olrdi6+/BmGpEs LTLS/RgWbIsIbRdi5ml1fgp8nf6TMZstoggFE7BMEzXmwevdHQYxN8KvRxmsdfB3xyzI 9sbuk03ch58xInG4Q8GinjvzU2V3/Dmb/GUquM6c465ORP4OJJapOweJfbcLkzmWKCNO B096M1G+DQUBwKGpfKLw8G5AmTMJqUo1WEVKJtzp6/phbzvQUiDkz4JyAdJTgzHmq+ik V7ClGrVCeDYF7mKbBVSK4z6FI5wajQkv1eznQLG/dh3R5hnVzyLhCdJP5/cZfgHC8/zP f2jw== X-Gm-Message-State: APjAAAXL1TRBFsROaV7TJvzoE3TmjnRq3CJLCXIxNvYN8drRleXpWtwY n3lf8DoF6/Ceb1uoB6MxWBWKStzMR99JqfGT8dtppw== X-Google-Smtp-Source: APXvYqw+/wNPaz2Jt34Xs4/PUHdDBC/e+qX0vZZWhKbt/QizMYTEHjPBDWCRPvr6iR8ZM3o7LHr432YZWOThFtdChsU= X-Received: by 2002:a2e:9217:: with SMTP id k23mr26761432ljg.159.1552575047475; Thu, 14 Mar 2019 07:50:47 -0700 (PDT) MIME-Version: 1.0 References: <18940.1551545018@sss.pgh.pa.us> In-Reply-To: From: Magnus Hagander Date: Thu, 14 Mar 2019 15:50:36 +0100 Message-ID: Subject: Re: Namespace projects.postgresql.org To: Tom Lane Cc: Stefan Kaltenbrunner , PostgreSQL WWW Content-Type: multipart/alternative; boundary="0000000000003148c705840f0c2d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000003148c705840f0c2d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Mar 3, 2019 at 9:35 PM Magnus Hagander wrote: > > > On Sat, Mar 2, 2019 at 5:43 PM Tom Lane wrote: > >> 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 d= o >> > 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 historic= al >> rather than current projects. >> > > They are no longer being actively updated, no. For gborg there definitely > doesn't exist anything else. For pgfoundry I don't know exactly how dead = it > is. But the last sync was pulled sometime in 2013. > > I have now removed the projects.postgresql.org entry from DNS. I haven't done anything to the FTP entries, since they are as mentioned quite possibly the only copy of some of this stuff. Perhaps we should drop a README file =C3=ADnto the pub/projects directory explaining that content in these directories can be expected to be out of date? It won't help people following deep links into it, but at least it might do something? //Magnus --0000000000003148c705840f0c2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Mar 3, 2019 at 9:35 PM Magnus Hag= ander <magnus@hagander.net>= ; wrote:


On Sat, Mar 2, 20= 19 at 5:43 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>= ; writes:
> Is this proposal also for cleaning up the old gborg and pgfoundry data=
> on our file-mirrors (ie: http://ftp.postgresql.org/pub/p= rojects/) 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?=C2=A0 I'd be kind of inclined to = keep
such data just for archival reasons.=C2=A0 Doesn't mean it has to be ea= sily
accessible of course, and we should make sure it's presented as histori= cal
rather than current projects.

They are = no longer being actively updated, no. For gborg there definitely doesn'= t exist anything else. For pgfoundry I don't know exactly how dead it i= s. But the last sync was pulled sometime in 2013.=C2=A0

I have now removed the projects.postgresql.org entry from= DNS.

I haven't done anything to the FTP entri= es, since they are as mentioned quite possibly the only copy of some of thi= s stuff.

Perhaps we should drop a README file =C3= =ADnto the pub/projects directory explaining that content in these director= ies can be expected to be out of date? It won't help people following d= eep links into it, but at least it might do something?

=
//Magnus
--0000000000003148c705840f0c2d--