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 1h0Xq2-0002QK-HU for pgsql-www@arkaria.postgresql.org; Sun, 03 Mar 2019 20:35:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h0Xq0-0002Ez-2O for pgsql-www@arkaria.postgresql.org; Sun, 03 Mar 2019 20:35:56 +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 1h0Xpz-0002Es-Ps for pgsql-www@lists.postgresql.org; Sun, 03 Mar 2019 20:35:55 +0000 Received: from mail-lj1-x242.google.com ([2a00:1450:4864:20::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h0Xpu-0007Ja-I7 for pgsql-www@lists.postgresql.org; Sun, 03 Mar 2019 20:35:54 +0000 Received: by mail-lj1-x242.google.com with SMTP id t13so2508781lji.2 for ; Sun, 03 Mar 2019 12:35:50 -0800 (PST) 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=rvIFiaab3DzYmzjzxdn/pcWA/d9Us0uj9YE8M55PBuw=; b=hKGTTJH6HgYrGVMwE/kHmlLWhcE7CPLVBkzeOp6tSdz7CIvYhUg9Hpa2lQfhxOOiX5 mh7/Q5xXSY7IyPg6zAetf/z2hbovVb3EDhPnvobYgd+wOkX6crPf8fW7UkpDioIK2wHz ccsf4EmPTNJbg+t9sLJKT4ddigJusFUlWPutE7zw4rQSl9MUrumVPWpGmmXV8MfV6aEw ReKaWyYv9QY2aVPXLt9NCa6oD30o6GS55EwrxSa227R+sZ7I7M7K1fzg82h2IC13U+fu Z2WdrxtjgwcUMfAzHqShkja+IGh+5vOSaZFESYeBB06htk6OQ06pljCipt94OpKi0VtX Oc7w== 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=rvIFiaab3DzYmzjzxdn/pcWA/d9Us0uj9YE8M55PBuw=; b=Bqn8GGfDwufxoheAXB3jdbndf2dLGYd0/8wAkqxADrNEeD3r1tADhW5S5aIRsRq9LZ 0tKA6lTntddtjwOoZRg8GmIZvf6E1zvzrpJTjsIwGJP9Jz9FFtgCecAIhxaFw8+z3DAi FrRazU1LBp/AmkOArT8fF/5dI4QRAHnfSixDtCruMCPQRe2BvOCRiPBbdA8J94b3YEav /G9B4QPWejqvk7VUT/R88e86D2Fw6CYeRrkeUMtnsP7KCq1AVWhDn39RuPM7ynl6helX 0/ZdqK0uT/ah6oDgd6wflnE0va+tkbvyFud5miZm/7NFmGZyDV3sawSpui85DwozKz/b r4EA== X-Gm-Message-State: APjAAAUxv7BeW6QCaR0z0yz7BRzpYOrgWudvmcU6dDoLdYAmND8MO7+Q SNDkT2KEbV3alSlQefp+lF8h4xtcLl8zgopmaYmJhsn2 X-Google-Smtp-Source: APXvYqxR7rlT+yArPxCCuQVzLMJziQZYKIeQ0WLTx5OKfFYAs+AmT3KG39/FDl2mwsVD5hr+CT6SJJuI6DlWmUCQ3dk= X-Received: by 2002:a2e:9150:: with SMTP id q16mr8767610ljg.18.1551645347057; Sun, 03 Mar 2019 12:35:47 -0800 (PST) MIME-Version: 1.0 References: <18940.1551545018@sss.pgh.pa.us> In-Reply-To: <18940.1551545018@sss.pgh.pa.us> From: Magnus Hagander Date: Sun, 3 Mar 2019 21:35:36 +0100 Message-ID: Subject: Re: Namespace projects.postgresql.org To: Tom Lane Cc: Stefan Kaltenbrunner , PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000ba9e6005833695f4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000ba9e6005833695f4 Content-Type: text/plain; charset="UTF-8" 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 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. > 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. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000ba9e6005833695f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Mar 2, 2019 at 5:43 PM Tom La= ne <tgl@sss.pgh.pa.us> wrote= :
Stefan Kaltenb= runner <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
--
<= div>=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpr= o.com/
--000000000000ba9e6005833695f4--