Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 372189FB3B1; Fri, 4 May 2007 15:47:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 62814-09; Fri, 4 May 2007 15:47:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by postgresql.org (Postfix) with ESMTP id 11B8E9FBD73; Fri, 4 May 2007 15:47:05 -0300 (ADT) Received: from new-host.home ([71.166.59.121]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JHJ002TC5IBQU88@vms048.mailsrvcs.net>; Fri, 04 May 2007 13:47:00 -0500 (CDT) Date: Fri, 04 May 2007 14:46:41 -0400 From: Robert Treat Subject: Re: [HACKERS] Feature freeze progress report In-reply-to: <912350.37761.qm@web54612.mail.yahoo.com> To: pgsql-www@postgresql.org Cc: Chris Ryan , "Marc G. Fournier" , "Joshua D. Drake" , Josh Berkus , Bruce Momjian , pgsql-hackers@postgresql.org Message-id: <200705041446.42352.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <912350.37761.qm@web54612.mail.yahoo.com> User-Agent: KMail/1.9.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/37 X-Sequence-Number: 11971 I think this is the apprach joshua tried the first time and it backfired... I think we need a more personal approach. I'm willing to put time into this if people want a new point man (I don't think Joshua will mind, lmk if you do) but it will have to wait untill after pgcon. On Thursday 03 May 2007 15:12, Chris Ryan wrote: > I was just getting ready to suggest such an approach. We could > email all the project admins for the reamaining projects with the > dead-line. Backup the information and tell people who to contact in > order to claim whatever information they want. Once the dead-line is > past you can simply shutdown all the gborg services. Those who don't > claim their information either have already moved someplace else or > don't care about what is on gborg anymore. > > Additionally if it were desired we could place tarballs of the > cvsrepositories and whatever download files where uploaded for each > project on some ftp server if anyone was interested in preserving that > ifnormation for posterity. > > It would not be difficult for me to get a list of email addresses > and project names of those admins on gborg. > > Chris Ryan > > --- "Marc G. Fournier" wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Why not just send a notice out stated that Gborg will be shutdown as > > of June > > 1st ... give a finite deadline to move things over to pgfoundry ... > > just > > because we 'shut down' the site on June 1st, it doesn't mean we are > > going to > > wipe it all out, we can just put a Redirect on the web server on > > gborg over to > > pgfoundry so that ppl can't go *to* gborg's web site ... we can also > > make the > > CVS 'read-only', so that developers can't update the CVS there, but > > ppl can > > still download the code ... > > -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL