X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9C3B1D1B450; Mon, 1 Dec 2003 19:43:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 65694-08; Mon, 1 Dec 2003 15:42:44 -0400 (AST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id B8D91D1B436; Mon, 1 Dec 2003 15:42:42 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id DE2FF36FE2; Mon, 1 Dec 2003 15:40:05 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C6F0936FDC; Mon, 1 Dec 2003 15:40:05 -0400 (AST) Date: Mon, 1 Dec 2003 15:40:05 -0400 (AST) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Chris Ryan Cc: Dave Page , Robert Treat , "Marc G. Fournier" , pgsql-www@postgresql.org Subject: Re: gforge In-Reply-To: <20031201182609.2644.qmail@web40010.mail.yahoo.com> Message-ID: <20031201153842.O38069@ganymede.hub.org> References: <20031201182609.2644.qmail@web40010.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/4 X-Sequence-Number: 3064 IMHO ... I would personally love to avoid having to move, for exactly the reasons that several people of put forth, but largely, migrating projects from one to the other *would* be a nightmare (doable, but painful) ... So, if it is/were possible to build up a team to push development of GBorg forward, that would be teh optimal solution ... On Mon, 1 Dec 2003, Chris Ryan wrote: > With respect to GBorg vs GForge, or any other project hosting site > infrastructure for that matter, it is my firm belief that you should do > what is best for the PostgreSQL community. Which is best? I am sure > everyone will have their own opinions about that along with the merits > and disadvantages to each choice. If the choice is made to move away > from GBorg I would fully understand and offer my assistance in any > migration effort possible to another system. > > As for the direct development and maintenance of GBorg I often just > simply lack the time to do anything beyond simple maintenance and some > of the smaller enhancements requested by users. One of my biggest > things I've been wanting to do it enhance the admin screens for project > approval and turn that over to this list in the same manner that the > news and events is currently done. If GBorg is to stay around some > changes like that would be great to try and involve more people than > just myself into the process. I could also come up with a list of > things people have asked for in the past that could be worked on. > > If GBorg stays it will need effort and participation from the > community in order to make it into a better development platform. That > is not something I can do by my self. > > In an effort to fix a mistake I have probably made from the > beginning I would like to announce that I do not claim control over the > vision or future of GBorg. I have always tried to do what was desired > by others in the effort to make GBorg useful to the PostgreSQL > community. If the pgsql-www group wants to claim control of the vision > I would encourage it does so. > > > Chris Ryan > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.com/ > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664