> Well, I'm for improving the catalogue to provide what people want from
> it, but I'm certainly not going to support web pages, mailing lists,
> file sharing or the one your forgot, bug tracking as well as
> pgFoundry.
AFAIK, nobody is using the bug tracking since it appears to be pretty
much broken.
> Given past experience of migration, I can only believe that the least
> painful, and most likely to happen option is an upgrade of pgFoundry
> on a new, documented VM that the sysadmin team can manage properly.
> Trying to get rid of pgFoundry will lead to years of faffing about
> while we try to migrate people - if we even can migrate them anywhere
> without losing mailing list/tracker history etc.
Well, we can simply keep it on life support while we encourage people to
use other services. Then, like GBorg, we can kill it because nothing on
it is maintained anymore.
--Josh Berkus