Thread: Shutting down the pgfoundry project

Now that we have our website up at the new address,
https://odbc.postgresql.org/ (Hooray!), let's shut down the web pages
and project at PGFoundry.

Dave, Hiroshi I., Hiroshi S., you are the project admins at pgfoundry.
Can you disable, or delete, or whatever you can do to the project there,
please?

I don't think we care about remaining issues in the bug tracker. I
briefly looked at a few of the latest ones, the remaining ones are many
years old and probably not applicable anymore, or at least we have no
plans to address them anyway.

It would be nice to put a 301 redirect from the pgfoundry site to the
new site. We could try to ask Marc to set one up, but it's probably
quicker to just drop an index.html with a meta-refresh tag there. I can
do that, but is there some cron job that I need to disable, so that it
doesn't get overwritten?

- Heikki

A 22-01-2015 09:23, Heikki Linnakangas escrigué:

Now that we have our website up at the new address, https://odbc.postgresql.org/ (Hooray!), let's shut down the web pages and project at PGFoundry.

Dave, Hiroshi I., Hiroshi S., you are the project admins at pgfoundry. Can you disable, or delete, or whatever you can do to the project there, please?

I don't think we care about remaining issues in the bug tracker. I briefly looked at a few of the latest ones, the remaining ones are many years old and probably not applicable anymore, or at least we have no plans to address them anyway.

It would be nice to put a 301 redirect from the pgfoundry site to the new site. We could try to ask Marc to set one up, but it's probably quicker to just drop an index.html with a meta-refresh tag there. I can do that, but is there some cron job that I need to disable, so that it doesn't get overwritten?

- Heikki

One question

 it would be interessant to update the credits of postgreSQL ODBC "The source code for this driver was originally adopted from version 0.20 of PostODBC. The authors at that time were Christian Czezatke and Dan McGuirk. Later it was maintained by Julie Ann Case." and put at least the names of people who have mantained the driver many many years.

Names like: Hiroshi Inoue, Hiroshi Saito, Dave Page ...

what do you think ?

My best regards

Simeó Reig

Barcelona (Spain)

Hi

On Thu, Jan 22, 2015 at 8:23 AM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> Now that we have our website up at the new address,
> https://odbc.postgresql.org/ (Hooray!), let's shut down the web pages and
> project at PGFoundry.
>
> Dave, Hiroshi I., Hiroshi S., you are the project admins at pgfoundry. Can
> you disable, or delete, or whatever you can do to the project there, please?

I've disabled the various modules and updated the homepage and
description to indicate the new location. I think that's about all I
can do.

> I don't think we care about remaining issues in the bug tracker. I briefly
> looked at a few of the latest ones, the remaining ones are many years old
> and probably not applicable anymore, or at least we have no plans to address
> them anyway.
>
> It would be nice to put a 301 redirect from the pgfoundry site to the new
> site. We could try to ask Marc to set one up, but it's probably quicker to
> just drop an index.html with a meta-refresh tag there. I can do that, but is
> there some cron job that I need to disable, so that it doesn't get
> overwritten?

So I don't seem to have root on that box any more (which is a good
thing). I had a cron job that attempted to run update-website.sh (with
no path), which was presumably failing as that script is not in my
home directory. It is in /home/pgfoundry.org/groups/psqlodbc though,
so I've renamed it in case root's cron was running it. I've also
replaced index.html with one that does a redirect.

Thanks for working on this Heikki.

--
Dave Page
Chief Architect, Tools & Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

On 01/22/2015 11:38 AM, Dave Page wrote:
> I've disabled the various modules and updated the homepage and
> description to indicate the new location. I think that's about all I
> can do.
>...
> I've also replaced index.html with one that does a redirect.

Great, thanks Dave!

- Heikki

Heikki Linnakangas

Thursday, January 22, 2015 8:12 AM

Great, thanks Dave!

- Heikki

Heikki Linnakangas

Thursday, January 22, 2015 3:23 AM

Now that we have our website up at the new address, https://odbc.postgresql.org/ (Hooray!), let's shut down the web pages and project at PGFoundry.

Dave, Hiroshi I., Hiroshi S., you are the project admins at pgfoundry. Can you disable, or delete, or whatever you can do to the project there, please?

I don't think we care about remaining issues in the bug tracker. I briefly looked at a few of the latest ones, the remaining ones are many years old and probably not applicable anymore, or at least we have no plans to address them anyway.

It would be nice to put a 301 redirect from the pgfoundry site to the new site. We could try to ask Marc to set one up, but it's probably quicker to just drop an index.html with a meta-refresh tag there. I can do that, but is there some cron job that I need to disable, so that it doesn't get overwritten?

- Heikki

On 01/22/2015 04:13 PM, michael@sqlexec.com wrote:
> So should I not go to this link anymore:
> http://www.postgresql.org/ftp/odbc/

That address is still correct. It was the main website that was moved,
and is now at https://odbc.postgresql.org/. We have no plans to move the
downloads site.

- Heikki

On 01/22/2015 11:21 AM, Simeó Reig wrote:
>   it would be interessant to update the credits of postgreSQL ODBC "The
> source code for this driver was originally adopted from version 0.20 of
> PostODBC. The authors at that time were Christian Czezatke and Dan
> McGuirk. Later it was maintained by Julie Ann Case." and put at least
> the names of people who have mantained the driver many many years.
>
> Names like: Hiroshi Inoue, Hiroshi Saito, Dave Page ...
>
> what do you think ?

Well, it does say that "the driver is currently maintained by a number
of contributors to the PostgreSQL project", which I think covers it. The
section mainly explains the history of how the driver found its way into
the PostgreSQL project. That said, if you want to write a docs patch, I
have no objections to expanding it.

Actually, it should mention that it was later split off from the
PostgreSQL source distribution again, to live as a free software project
of its own.

- Heikki