public inbox for [email protected]help / color / mirror / Atom feed
Namespace projects.postgresql.org 10+ messages / 6 participants [nested] [flat]
* Namespace projects.postgresql.org @ 2019-02-28 11:15 Magnus Hagander <[email protected]> 0 siblings, 4 replies; 10+ messages in thread From: Magnus Hagander @ 2019-02-28 11:15 UTC (permalink / raw) To: PostgreSQL WWW <[email protected]> Breaking this: https://www.postgresql.org/message-id/CABUevEzo-wBhipDX%3DoNH1cUhtVLKF7h2VCSJZB2j9FeSs3c1nA%40mail.g... Into it's own thread so people don't miss it. Basically, the suggestion is to kill off the projects.postgresql.org namespace which has been forwarding to pgfoundry for years, given that pgfoundry is mostly unmaintained and has been for ages. -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/; Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/; ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-02-28 12:20 Dave Page <[email protected]> parent: Magnus Hagander <[email protected]> 3 siblings, 0 replies; 10+ messages in thread From: Dave Page @ 2019-02-28 12:20 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: PostgreSQL WWW <[email protected]> On Thu, Feb 28, 2019 at 11:15 AM Magnus Hagander <[email protected]> wrote: > Breaking this: > > > https://www.postgresql.org/message-id/CABUevEzo-wBhipDX%3DoNH1cUhtVLKF7h2VCSJZB2j9FeSs3c1nA%40mail.g... > > Into it's own thread so people don't miss it. > > Basically, the suggestion is to kill off the projects.postgresql.org > namespace which has been forwarding to pgfoundry for years, given that > pgfoundry is mostly unmaintained and has been for ages. > +1 -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-02-28 16:43 Stephen Frost <[email protected]> parent: Magnus Hagander <[email protected]> 3 siblings, 0 replies; 10+ messages in thread From: Stephen Frost @ 2019-02-28 16:43 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: PostgreSQL WWW <[email protected]> Greetings, * Magnus Hagander ([email protected]) wrote: > Breaking this: > > https://www.postgresql.org/message-id/CABUevEzo-wBhipDX%3DoNH1cUhtVLKF7h2VCSJZB2j9FeSs3c1nA%40mail.g... > > Into it's own thread so people don't miss it. > > Basically, the suggestion is to kill off the projects.postgresql.org > namespace which has been forwarding to pgfoundry for years, given that > pgfoundry is mostly unmaintained and has been for ages. +1 Thanks! Stephen Attachments: [application/pgp-signature] signature.asc (819B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-02-28 16:50 Jonathan S. Katz <[email protected]> parent: Magnus Hagander <[email protected]> 3 siblings, 0 replies; 10+ messages in thread From: Jonathan S. Katz @ 2019-02-28 16:50 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; PostgreSQL WWW <[email protected]> On 2/28/19 6:15 AM, Magnus Hagander wrote: > Breaking this: > > https://www.postgresql.org/message-id/CABUevEzo-wBhipDX%3DoNH1cUhtVLKF7h2VCSJZB2j9FeSs3c1nA%40mail.g... > > Into it's own thread so people don't miss it. > > Basically, the suggestion is to kill off the projects.postgresql.org > <http://projects.postgresql.org; namespace which has been forwarding to > pgfoundry for years, given that pgfoundry is mostly unmaintained and has > been for ages. +1 Jonathan Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-03-02 09:02 Stefan Kaltenbrunner <[email protected]> parent: Magnus Hagander <[email protected]> 3 siblings, 1 reply; 10+ messages in thread From: Stefan Kaltenbrunner @ 2019-03-02 09:02 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: PostgreSQL WWW <[email protected]> On 2/28/19 12:15 PM, Magnus Hagander wrote: > Breaking this: > > https://www.postgresql.org/message-id/CABUevEzo-wBhipDX%3DoNH1cUhtVLKF7h2VCSJZB2j9FeSs3c1nA%40mail.g... > > Into it's own thread so people don't miss it. > > Basically, the suggestion is to kill off the projects.postgresql.org > namespace which has been forwarding to pgfoundry for years, given that > pgfoundry is mostly unmaintained and has been for ages. +1 - actually looking at the horribly outdated stuff that is on pgfoundry website, that seems like a very good idea. 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? Stefan ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-03-02 16:43 Tom Lane <[email protected]> parent: Stefan Kaltenbrunner <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Tom Lane @ 2019-03-02 16:43 UTC (permalink / raw) To: Stefan Kaltenbrunner <[email protected]>; +Cc: Magnus Hagander <[email protected]>; PostgreSQL WWW <[email protected]> Stefan Kaltenbrunner <[email protected]> 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 ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-03-03 20:35 Magnus Hagander <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Magnus Hagander @ 2019-03-03 20:35 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; PostgreSQL WWW <[email protected]> On Sat, Mar 2, 2019 at 5:43 PM Tom Lane <[email protected]> wrote: > Stefan Kaltenbrunner <[email protected]> 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/ <http://www.hagander.net/; Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/; ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-03-14 14:50 Magnus Hagander <[email protected]> parent: Magnus Hagander <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Magnus Hagander @ 2019-03-14 14:50 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; PostgreSQL WWW <[email protected]> On Sun, Mar 3, 2019 at 9:35 PM Magnus Hagander <[email protected]> wrote: > > > On Sat, Mar 2, 2019 at 5:43 PM Tom Lane <[email protected]> wrote: > >> Stefan Kaltenbrunner <[email protected]> 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. > > 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 ínto 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 ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-03-14 15:27 Tom Lane <[email protected]> parent: Magnus Hagander <[email protected]> 0 siblings, 1 reply; 10+ messages in thread From: Tom Lane @ 2019-03-14 15:27 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; PostgreSQL WWW <[email protected]> Magnus Hagander <[email protected]> writes: > 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 ínto 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? +1 regards, tom lane ^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Namespace projects.postgresql.org @ 2019-07-11 16:43 Magnus Hagander <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 10+ messages in thread From: Magnus Hagander @ 2019-07-11 16:43 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Stefan Kaltenbrunner <[email protected]>; PostgreSQL WWW <[email protected]> On Thu, Mar 14, 2019 at 4:27 PM Tom Lane <[email protected]> wrote: > Magnus Hagander <[email protected]> writes: > > 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 ínto 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? > > +1 > Back from the dead a few months later, this has now been done! -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/; Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/; ^ permalink raw reply [nested|flat] 10+ messages in thread
end of thread, other threads:[~2019-07-11 16:43 UTC | newest] Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2019-02-28 11:15 Namespace projects.postgresql.org Magnus Hagander <[email protected]> 2019-02-28 12:20 ` Dave Page <[email protected]> 2019-02-28 16:43 ` Stephen Frost <[email protected]> 2019-02-28 16:50 ` Jonathan S. Katz <[email protected]> 2019-03-02 09:02 ` Stefan Kaltenbrunner <[email protected]> 2019-03-02 16:43 ` Tom Lane <[email protected]> 2019-03-03 20:35 ` Magnus Hagander <[email protected]> 2019-03-14 14:50 ` Magnus Hagander <[email protected]> 2019-03-14 15:27 ` Tom Lane <[email protected]> 2019-07-11 16:43 ` Magnus Hagander <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox