Thread: Gborg: announcement by 404
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Said in another list: > Now that gborg.postgresql.org is officially dead, seems like it'd be a > good idea to update all the references to it that are in the FAQ. Did I miss something, or was there no post made to -announce and/or -general about this? Since even people on the -www list seemed to have been caught by surprise by the move, I think we should at least make a public announcement. Perhaps a news item or other mention on the main postgresql.org page? Something on the main pgfoundry.org page? Some sort of redirect or friendlier message is needed as well. For example, the second link when Googling for "Postgres Slony" is: http://gborg.postgresql.org/project/slony1 ...which now gives a very unfriendly 404 message from pgfoundry. Granted, the first Google hit is the authoritative one, but this is probably just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg', or 'pgsphere' for some even scarier examples. I'll reiterate my offer to write a web-log scraping script for the main site and extend it to pgfoundry, to at least start triaging some of the worst effects of the move if nobody has other ideas. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200711132306 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHOna/vJuQZxSWSsgRA7LXAJsH8dUFYiMz9XCd1YB4Y7WUj0GCkACgwWma aa4fD7D0+nbTfuUKlX0ldoM= =UKzK -----END PGP SIGNATURE-----
Greg Sabino Mullane wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > > Said in another list: >> Now that gborg.postgresql.org is officially dead, seems like it'd be a >> good idea to update all the references to it that are in the FAQ. > > Did I miss something, or was there no post made to -announce > and/or -general about this? Since even people on the -www list > seemed to have been caught by surprise by the move, I think we should at > least make a public announcement. Perhaps a news item or other mention > on the main postgresql.org page? Something on the main pgfoundry.org page? Yes, well, it has only taken a few years to transfer across and finalise the move so you may have missed some of the notices and discussions. Here is a post from 3.6 years ago about the move - http://archives.postgresql.org/pgsql-www/2004-03/msg00063.php > Some sort of redirect or friendlier message is needed as well. For > example, the second link when Googling for "Postgres Slony" is: > > http://gborg.postgresql.org/project/slony1 > > ...which now gives a very unfriendly 404 message from pgfoundry. Granted, > the first Google hit is the authoritative one, but this is probably > just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg', > or 'pgsphere' for some even scarier examples. I'll second that - we should have redirects (or notice pages showing the new url) for a while instead of a sudden disappearance. > I'll reiterate my offer to write a web-log scraping script for the main site > and extend it to pgfoundry, to at least start triaging some of the worst > effects of the move if nobody has other ideas. > > - -- > Greg Sabino Mullane greg@turnstep.com > PGP Key: 0x14964AC8 200711132306 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > -----BEGIN PGP SIGNATURE----- > > iD8DBQFHOna/vJuQZxSWSsgRA7LXAJsH8dUFYiMz9XCd1YB4Y7WUj0GCkACgwWma > aa4fD7D0+nbTfuUKlX0ldoM= > =UKzK > -----END PGP SIGNATURE----- > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- Shane Ambler pgSQL@Sheeky.Biz Get Sheeky @ http://Sheeky.Biz
"Greg Sabino Mullane" <greg@turnstep.com> writes: > Said in another list: >> Now that gborg.postgresql.org is officially dead, seems like it'd be a >> good idea to update all the references to it that are in the FAQ. > > Did I miss something, or was there no post made to -announce > and/or -general about this? Since even people on the -www list > seemed to have been caught by surprise by the move, I think we should at > least make a public announcement. Perhaps a news item or other mention > on the main postgresql.org page? Something on the main pgfoundry.org page? I thought gborg had been announced as dead long ago. > Some sort of redirect or friendlier message is needed as well. For > example, the second link when Googling for "Postgres Slony" is: > > http://gborg.postgresql.org/project/slony1 > > ...which now gives a very unfriendly 404 message from pgfoundry. Granted, > the first Google hit is the authoritative one, but this is probably > just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg', > or 'pgsphere' for some even scarier examples. I think the problem here is that if there's an error Google will notice that and stop returning search results. If there's a page saying "I'm not a page" then Google will assume that's what's supposed to be there. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning
Gregory Stark wrote: > "Greg Sabino Mullane" <greg@turnstep.com> writes: ... >> http://gborg.postgresql.org/project/slony1 >> >> ...which now gives a very unfriendly 404 message from pgfoundry. Granted, >> the first Google hit is the authoritative one, but this is probably >> just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg', >> or 'pgsphere' for some even scarier examples. > > I think the problem here is that if there's an error Google will notice that > and stop returning search results. If there's a page saying "I'm not a page" > then Google will assume that's what's supposed to be there. That's what redirection using "301 Moved Permanently" is for. It will tell Google that the new page permanently replaced the old one. Concerning Google, this is a better solution than either a 404 or a human-readable page about the move. Best Regards Michael Paesold
On Wed, Nov 14, 2007 at 09:15:29AM +0100, Michael Paesold wrote: > Gregory Stark wrote: > >"Greg Sabino Mullane" <greg@turnstep.com> writes: > ... > >>http://gborg.postgresql.org/project/slony1 > >> > >>...which now gives a very unfriendly 404 message from pgfoundry. Granted, > >>the first Google hit is the authoritative one, but this is probably > >>just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg', > >>or 'pgsphere' for some even scarier examples. > > > >I think the problem here is that if there's an error Google will notice > >that > >and stop returning search results. If there's a page saying "I'm not a > >page" > >then Google will assume that's what's supposed to be there. > > That's what redirection using "301 Moved Permanently" is for. It will tell > Google that the new page permanently replaced the old one. Concerning > Google, this is a better solution than either a 404 or a human-readable > page about the move. Or you can construct a human-readable 404 page. Google will notice it says 404 and not index it, but a browser will show a nicer error msg than just "not found". IIRC, custom error pages in apache does that. If not, it can certainly be done with simple PHP - we do this for wwwmaster.postgresql.org to deliver "not found" pages inside the graphical framework. (originally they didn't have a 404 code though, which caused the mirrorer to pick them up, and google to index them, which wasn't a very good idea :-P) //Magnus
On Wed, Nov 14, 2007 at 06:18:36PM +1030, Shane Ambler wrote:
>
> Yes, well, it has only taken a few years to transfer across and finalise
> the move so you may have missed some of the notices and discussions.
I think this misses the point. Here's the way the move was handled:
Day N : "We need to move gborg."
Day N+7: "We still need to move gborg."
Day N+6 months: "We still need to move gborg."
Day N+1 year: "We still need to move gborg."
Day N+2 years: "We still need to move gborg."
Day M-1 day: "I'm turning gborg of tomorrow!"
Day M: gborg off
Somewhere between Day N+2 years and Day M-1, there really ought to have been
the following:
Day M-30 days: "Gborg will be decommissioned in 30 days."
Day M-7 days: "Gborg will be decommissioned in 7 days. If you haven't moved
your data yet, get to work! This deadline won't be moved."
&c.
I don't believe this is too much to ask, for any of our services. I have
the impression that some members of the www group believe the same thing.
This project is now far too large to make decisions one day and put them
into place the next. It's _also_ far too large not to set reasonable
deadlines for members of the community, and stick to them, in respect of
hosted infrastructure -- provided the lead time for that sort of
administrative work is long enough. Note that, "We really need to do
something about this," isn't a deadline.
A
--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Wednesday, November 14, 2007 04:18:07 +0000 Greg Sabino Mullane <greg@turnstep.com> wrote: > I'll reiterate my offer to write a web-log scraping script for the main site > and extend it to pgfoundry, to at least start triaging some of the worst > effects of the move if nobody has other ideas. Which web-log do you need? - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHOnpa4QvfyHIvDvMRAkD+AJ9SvRQ4SPyhgOPyHsX3Mrn9c9iGmgCg5K9u fUU/w0etaB1CM720xa0P2HA= =j/nO -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 14 Nov 2007 04:18:07 -0000 "Greg Sabino Mullane" <greg@turnstep.com> wrote: > Did I miss something, or was there no post made to -announce > and/or -general about this? Since even people on the -www list There were not announcements this time and there certainly should have been. However, there have been many, many announcements trying to get people off gborg and I have very little sympathy for any who were stuck. I personally emailed every single member telling them that it was shut down. If they couldn't get up the time to move it in a year, I doubt they ever would have had to courtesy to move when we asked, over and over and over for them to do so. > seemed to have been caught by surprise by the move, I think we should > at least make a public announcement. Agreed. > Perhaps a news item or other > mention on the main postgresql.org page? Something on the main > pgfoundry.org page? > Well I don't think we need anything on the postgresql.org but on the pgfoundry.org page. I will also write up a mention on planetpostgresql which will get aggregated in lots of places (including .org). > Some sort of redirect or friendlier message is needed as well. For > example, the second link when Googling for "Postgres Slony" is: > > http://gborg.postgresql.org/project/slony1 > > ...which now gives a very unfriendly 404 message from pgfoundry. Well that is kind of dumb. Slony hasn't been on gborg for a year. Joshua D. Drake - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHOzImATb/zqfZUUQRAuKcAKCMHEx11m7cy9yfKlVZ9wPfn0aLLgCdG+dT o87fMz+a5ZZ4fH8R2HJsjyg= =FRQy -----END PGP SIGNATURE-----
On Wed, Nov 14, 2007 at 01:34:05PM -0400, Marc G. Fournier wrote: > For all the discussions on why doing this so quickly was such a bad idea, do > you realize that *so far*, there have been a whole three *active* projects that > hadn't been moved over? pgweb, pljava and pgjdbc ... That is completely irrelevant. My point is a simple one: we're a mature project, and we should act like grown ups with our infrastructure. That means rather more _specific_ notice to users about when things will go away. The way it happened, it looked like someone woke up one morning and said, "I think I'll take down gborg today." If we want people to trust our software with their critical data, we have to act as though predictability is a good thing. Nobody is suggesting that it was ok to have gborg linger the way it did. All I'm saying is that the next time we shut something down, we need to tell _everybody_ well in advance exactly _when_ we think things will go away (emergencies are, of course, excepted). This doesn't mean four-hour "maintenance windows" at midnight or any of that. But it does mean that, some weeks in advance of something going away, there should be some evidence that the changes are planned. A -- Andrew Sullivan Old sigs will return after re-constitution of blue smoke
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For all the discussions on why doing this so quickly was such a bad idea, do you realize that *so far*, there have been a whole three *active* projects that hadn't been moved over? pgweb, pljava and pgjdbc ... There may be other projects that hadn't moved yet, but they are either dead projects, or so little used that nobody has noticed the site is down ... but that is why there is a backup of the code and mailing lists, *just in case* ... - --On Wednesday, November 14, 2007 10:43:02 -0500 Andrew Sullivan <ajs@crankycanuck.ca> wrote: > On Wed, Nov 14, 2007 at 06:18:36PM +1030, Shane Ambler wrote: >> >> Yes, well, it has only taken a few years to transfer across and finalise >> the move so you may have missed some of the notices and discussions. > > I think this misses the point. Here's the way the move was handled: > > Day N : "We need to move gborg." > Day N+7: "We still need to move gborg." > Day N+6 months: "We still need to move gborg." > Day N+1 year: "We still need to move gborg." > Day N+2 years: "We still need to move gborg." > Day M-1 day: "I'm turning gborg of tomorrow!" > Day M: gborg off > > Somewhere between Day N+2 years and Day M-1, there really ought to have been > the following: > > Day M-30 days: "Gborg will be decommissioned in 30 days." > Day M-7 days: "Gborg will be decommissioned in 7 days. If you haven't moved > your data yet, get to work! This deadline won't be moved." > > &c. > > I don't believe this is too much to ask, for any of our services. I have > the impression that some members of the www group believe the same thing. > This project is now far too large to make decisions one day and put them > into place the next. It's _also_ far too large not to set reasonable > deadlines for members of the community, and stick to them, in respect of > hosted infrastructure -- provided the lead time for that sort of > administrative work is long enough. Note that, "We really need to do > something about this," isn't a deadline. > > A > > -- > Andrew Sullivan > Old sigs will return after re-constitution of blue smoke > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHOzGN4QvfyHIvDvMRAkIEAKCdH0NSNEtC8Dtr+IDyD4FbJn9apgCePwd3 I4NNTbAt0y4VgorSFWBK8N4= =VooA -----END PGP SIGNATURE-----
Andrew Sullivan wrote: > On Wed, Nov 14, 2007 at 06:18:36PM +1030, Shane Ambler wrote: >> Yes, well, it has only taken a few years to transfer across and finalise >> the move so you may have missed some of the notices and discussions. > > I think this misses the point. Here's the way the move was handled: Not from my point of view - I wouldn't say that I have been overly active within postgres, yet over the last couple of years I have heard of the move to pgfoundry and have progressively been looking there more than gborg even when I come to a link to gborg I have learned to then search for it at pgfoundry. It has been confusing having two different places listing the same projects (for the most part) especially when it is not consistent with which site had the most recent work. The developers that used these sites have had more than enough time to transfer their work and now users only have one place to go. I do think redirection/moved messages should be coming from gborg for a while instead of just the quick disappearing act. I guess the real question is how much traffic has gborg been receiving before the shutdown and how much of that came from google or similar searches? If this is low as I expect, then updating google listings will be the major hurdle to complete the changeover. -- Shane Ambler pgSQL@Sheeky.Biz Get Sheeky @ http://Sheeky.Biz
On Thu, Nov 15, 2007 at 04:31:23AM +1030, Shane Ambler wrote: > The developers that used these sites have had more than enough time to > transfer their work and now users only have one place to go. Nobody is disputing that that is a good result. I am not talking about the desirability of the result; I am talking about how we do not get to desirable results in future using shoddy means. Note first that the developers were never given a hard date until the very end -- I know this, because I administered a project there, and wasn't given such a date. (I did reply, however, and said that we wouldn't move the project as it had been rendered irrelevant.) Second, most of the pleas to move the projects included various suggestions of automatic scripty bits that were going to do the moving. If I'm (say) the JDBC developers, and I have to choose between improving the driver or moving the project to meet some future possible gee-it'd-be-nice-if-we-could deadline, I know what I'd do -- especially since there's the hope that the problem will take care of itself later. Developers are users of the infrastructure, too. And their time and interest is a precious community resource that shouldn't be squandered. So distracting them (especially at beta time) with a short deadline for the removal of a service they may well be using is not good for the project. That's why a real announcement with a real date about when the service would end is important. A -- Andrew Sullivan Old sigs will return after re-constitution of blue smoke
Andrew Sullivan wrote: > On Wed, Nov 14, 2007 at 01:34:05PM -0400, Marc G. Fournier wrote: > > For all the discussions on why doing this so quickly was such a bad idea, do > > you realize that *so far*, there have been a whole three *active* projects that > > hadn't been moved over? pgweb, pljava and pgjdbc ... > > That is completely irrelevant. My point is a simple one: we're a mature > project, and we should act like grown ups with our infrastructure. That > means rather more _specific_ notice to users about when things will go away. > The way it happened, it looked like someone woke up one morning and said, "I > think I'll take down gborg today." If we want people to trust our software > with their critical data, we have to act as though predictability is a good > thing. > > Nobody is suggesting that it was ok to have gborg linger the way it did. > All I'm saying is that the next time we shut something down, we need to tell > _everybody_ well in advance exactly _when_ we think things will go away > (emergencies are, of course, excepted). This doesn't mean four-hour > "maintenance windows" at midnight or any of that. But it does mean that, > some weeks in advance of something going away, there should be some evidence > that the changes are planned. Agreed. I assume it was just done this way due to frustration, which isn't a great way to deal with things, but I think we all understand it. (I have to say I was kind of shocked at the rapidity of it, but at this stage, I wasn't going to slow down something I have been waiting for for years. ;-) ) -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Wednesday 14 November 2007 12:34, Marc G. Fournier wrote:
> For all the discussions on why doing this so quickly was such a bad idea,
> do you realize that *so far*, there have been a whole three *active*
> projects that hadn't been moved over? pgweb, pljava and pgjdbc ...
>
since i have a list of projects that have been contacted and thier status, let
me just say that this is not true. libpqxx is in quasi limbo wrt thier
mailing lists right now.
> There may be other projects that hadn't moved yet, but they are either dead
> projects, or so little used that nobody has noticed the site is down ...
> but that is why there is a backup of the code and mailing lists, *just in
> case* ...
>
>
on irc we had a question come up that might have been a case for looking at
something on gborg, but since that 404's people move on... given we still
have links in the irc bot and our search engine recommendation system that
point to gborg, I'm sure it's not the only case, but your kidding yourself if
you think people are going to email you to get access to the information
based on a 404 error on the links we suggest; they'll just move on.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
On Wednesday 14 November 2007 12:36, Joshua D. Drake wrote:
> On Wed, 14 Nov 2007 04:18:07 -0000
>
> "Greg Sabino Mullane" <greg@turnstep.com> wrote:
> > Did I miss something, or was there no post made to -announce
> > and/or -general about this? Since even people on the -www list
>
> There were not announcements this time and there certainly should have
> been. However, there have been many, many announcements trying to get
> people off gborg and I have very little sympathy for any who were stuck.
>
> I personally emailed every single member telling them that it was shut
> down. If they couldn't get up the time to move it in a year, I doubt
> they ever would have had to courtesy to move when we asked, over and
> over and over for them to do so.
>
I also contacted everyone personally and the people I spoke with were more
than willing to move thier projects (and many did so), but given they had no
access to cvs, majordomo, the gborg db or filesystem, the onus was on the web
team to keep this moving forward. You keep painting this as some fault of
the project developers and I find it very disrespectful.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Robert Treat wrote: > On Wednesday 14 November 2007 12:36, Joshua D. Drake wrote: >> On Wed, 14 Nov 2007 04:18:07 -0000 > You keep painting this as some fault of > the project developers and I find it very disrespectful. It is unfortunate that you feel that way, it certainly isn't true. However, I have done my part. I help Slony and I helped pgweb. My hands are all clean of paint, no turpentine needed. Sincerely, Joshua D. Drake
All, The Gborg thread belongs only on -www, not on advocacy. Please keep it on -www. Thanks! --Josh -- Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I just finished setting a bunch of permanent redirects on pgfoundry. Any gborg links to the following projects now go to their correct external URLs with a permanent redirect: phppgadmin dbdpg dbmodeller libpqxx slony1 These projects now bounce to the correct pgfoundry location: pljava pguuid plr pgintcl pgjobs dbi-link pgautotune pgintcl pgeasy tablelog pgimport tcap pfm pgdiff These are ones I don't know where (if anywhere) to point to. If anyone knows a valid location for any of these, please let me know: pgmatlab psqlodbcplus erserver jsppgadmin pgexport pgreplication gsm webpg rservimp pgexplorer pgcup xpsql ad-pgfoundry xcodegen pgvbaccess jpgadmin libobjcpq pginformix pgmoneyconvert citext thewsgsnippet pgjdbc pdadmin libpgcgi pgavd pglogd orapgsqlviews pgprocess uniqueidentifier pgsqlcocoa pgpayroll That was a first pass. I'll keep scanning the error log and handle things as they come up. If anyone is working on the mailing list archives or knows the status of them, please let me know as well. Otherwise, I'll track things down one by one as I did for the above. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200711160901 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHPaLAvJuQZxSWSsgRA0nIAKDja4Fa8DxCvoASiCKozFCjpLDLugCfW09S sHOiSGMxAlpiBz8b1tDKNbg= =aymv -----END PGP SIGNATURE-----
Thanks Greg. Regards, Dave Greg Sabino Mullane wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > > I just finished setting a bunch of permanent redirects on pgfoundry. > Any gborg links to the following projects now go to their > correct external URLs with a permanent redirect: > > phppgadmin dbdpg dbmodeller libpqxx slony1 > > These projects now bounce to the correct pgfoundry location: > > pljava pguuid plr pgintcl pgjobs dbi-link pgautotune > pgintcl pgeasy tablelog pgimport tcap pfm pgdiff > > These are ones I don't know where (if anywhere) to point to. If anyone > knows a valid location for any of these, please let me know: > > pgmatlab psqlodbcplus erserver jsppgadmin pgexport pgreplication > gsm webpg rservimp pgexplorer pgcup xpsql ad-pgfoundry > xcodegen pgvbaccess jpgadmin libobjcpq pginformix pgmoneyconvert > citext thewsgsnippet pgjdbc pdadmin libpgcgi pgavd pglogd > orapgsqlviews pgprocess uniqueidentifier pgsqlcocoa pgpayroll > > That was a first pass. I'll keep scanning the error log and handle things > as they come up. If anyone is working on the mailing list archives or > knows the status of them, please let me know as well. Otherwise, I'll > track things down one by one as I did for the above. > > - -- > Greg Sabino Mullane greg@turnstep.com > PGP Key: 0x14964AC8 200711160901 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > -----BEGIN PGP SIGNATURE----- > > iD8DBQFHPaLAvJuQZxSWSsgRA0nIAKDja4Fa8DxCvoASiCKozFCjpLDLugCfW09S > sHOiSGMxAlpiBz8b1tDKNbg= > =aymv > -----END PGP SIGNATURE----- > > > > ---------------------------(end of broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate
Greg Sabino Mullane wrote: > I just finished setting a bunch of permanent redirects on pgfoundry. Great, thanks! > These are ones I don't know where (if anywhere) to point to. If anyone > knows a valid location for any of these, please let me know: > > pgmatlab psqlodbcplus erserver jsppgadmin pgexport pgreplication > gsm webpg rservimp pgexplorer pgcup xpsql ad-pgfoundry > xcodegen pgvbaccess jpgadmin libobjcpq pginformix pgmoneyconvert > citext thewsgsnippet pgjdbc pdadmin libpgcgi pgavd pglogd > orapgsqlviews pgprocess uniqueidentifier pgsqlcocoa pgpayroll - pgjdbc I think pgjdbc was the gborg project for the official JDBC driver. So this is the pgfoundry project: http://pgfoundry.org/projects/jdbc/ - erserver As eRServer has been superseded by Slony, I guess the authors haven't created a pgfoundry project anymore. - pgavd IIRC, pgavd was a first C++ implementation of what has later become the autovacuum contrib module, which again was the basis for the backend implementation of today. Those are all project names I had any associations with. Hope it helps. Best Regards Michael Paesold
On Friday 16 November 2007 09:04, Greg Sabino Mullane wrote:
> These are ones I don't know where (if anywhere) to point to. If anyone
> knows a valid location for any of these, please let me know:
>
> pgmatlab psqlodbcplus erserver jsppgadmin pgexport pgreplication
> gsm webpg rservimp pgexplorer pgcup xpsql ad-pgfoundry
> xcodegen pgvbaccess jpgadmin libobjcpq pginformix pgmoneyconvert
> citext thewsgsnippet pgjdbc pdadmin libpgcgi pgavd pglogd
> orapgsqlviews pgprocess uniqueidentifier pgsqlcocoa pgpayroll
>
well, cross referencing your list with the notes i have...
pgmatlab, psqlodbcplus, pgexport, gcm, pgexplorer, pgcup, xpsql, xcodegen,
pginformix, pgmoneyconvert, citext, thewsgsnippet, pdadmin, libpgci, pgavd,
pgprocess, uniqueidentifier, pgpayroll - all of these were on my abandoned
projects list, i was unable to get ahold of the admins, and couldn't find
evidence they moved. i'd guess some of them are still usefull but...
pglogd, orapgsqlviews, ad-pgfoundry - these were not even on my list, so they
must have been removed from gborg quite some time ago. interesting they still
get hits.
pgjdbc is the jdbc project at pgfoundry
pgsqlcocoa moved to sourceforge
erserver, libobjcpq - both of these projects had asked to be moved to
pgfoundry
jsppgadmin, webpg, rservimp, pgvbaccess, jpgadmin - these project admins asked
that the projects be killed.
i've actually got notes on a lot more projects but whatever...
> That was a first pass. I'll keep scanning the error log and handle things
> as they come up. If anyone is working on the mailing list archives or
> knows the status of them, please let me know as well. Otherwise, I'll
> track things down one by one as I did for the above.
yeah, mailing list movement was where things got bogged down, so i'd imagine
it's been completly neglected, even for active projects like plr that wanted
thier mailing list moved.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
On Sat, Nov 17, 2007 at 09:25:13AM +0100, Michael Paesold wrote: > - erserver > As eRServer has been superseded by Slony, I guess the authors haven't > created a pgfoundry project anymore. I especially asked not to move the project over. It seemed to me to function mostly as an example of how not to do replication, so I didn't see any value in moving it (I shut down the mailing list over a year ago, because of spam penetration problems, and nobody ever complained to me). If someone feels this ought to be moved over, I can certainly get the archives back from Marc and put up a project. A -- Andrew Sullivan Old sigs will return after re-constitution of blue smoke