| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Alexey Klyukin <alexk(at)commandprompt(dot)com>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Proposal to shutdown pgFoundry |
| Date: | 2011-05-24 19:08:59 |
| Message-ID: | BANLkTinWsw7uh-zA4wAgJyW0e+=3DWmJcQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, May 24, 2011 at 6:31 PM, Cédric Villemain
<cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
>> The alternative to providing forwarding is to keep pgfoundry up for a
>> year after we start telling people to move off of it, but gradually lock
>> out activity on pgfoundry. That way there would be a transition period
>> during which the new locations for projects could climb the search results.
That's why the proposal gave a six month transition time and not
something shorter.
> At the end of this period, can we just make pgfoundry generated pages
> static, for memory and not to break links at all ?
That's not a good idea, as a) they won't point to the new projects and
b) will become steadily more out of date.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2011-05-24 19:14:40 | Re: PUGS site and events |
| Previous Message | Cédric Villemain | 2011-05-24 18:31:30 | Re: Proposal to shutdown pgFoundry |