Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Re: gforge
Date: Thu, 27 Nov 2003 08:37:37 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B87200BB@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] gforge
thread-index: AcO0Wio19ItIVXkdTeG8srxdEIEA4gAZpi8Q
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Robert Treat" <xzilla@users.sourceforge.net>,
	"Marc G. Fournier" <scrappy@postgresql.org>
Cc: <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]=20
> Sent: 26 November 2003 20:16
> To: Dave Page; Marc G. Fournier
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] gforge
>=20
> On Wednesday 26 November 2003 11:00, Dave Page wrote:
> > > -----Original Message-----
> > > From: Marc G. Fournier [mailto:scrappy@postgresql.org]
> > Mainly because we prefer the traditional mailing lists +=20
> CVS approach=20
> > like the core server uses. We also have a multilanguage=20
> website that=20
> > gborg can't do, but then I'm not sure that sf.net can either (for=20
> > example).
> >
>=20
> I'm pretty sure you could do your multilingual support on sf,=20
> though I'd need to look at your code to know for sure. sf=20
> gives you a standard user account ish web directory so its=20
> pretty flexible; the only big downside that I ever saw was=20
> they only give folks access to mysql databases, not=20
> postgresql :-( As for standard mailing lists / cvs approach,=20
> theres no reason you couldnt approach a sourceforge project=20
> the same way.
>=20
> BTW - I've been meaning to ask why don't we use the pgadmin=20
> code's language approach for the main website?

The design doesn't lend itself to a site the size of www.postgresql.org.
It's all done using php's gettext implementation, which is fine in
itself, but every html page is a mass of gettext calls, one for each
paragraph for maximum flexibility. That's fine on that site where there
are only about 6 pages, but we have around 10000 on www.postgresql.org.

> > Probably better people to ask would be Robert or Chris K-L, as they=20
> > actively chose sf.net as an alternative to GBorg.
> >
>=20
> I think the original rational for it was that great bridge=20
> had shut things down, so things were switched to sourceforge=20
> and when gborg came up there was no reason to switch back.=20=20
>=20
> speaking from a personal standpoint as someone who is a=20
> member of projects on both sites and has looked at the=20
> backend code for both sites, I do feel the sourceforge code=20
> is superior to the gborg code.=20

I'm sure sf.net has a lot more (paid) resources to put into it. From my
pov, I find sf.net to be over complex and confusing, but maybe that's
just me...

> from a project standpoint I=20
> think the information is laid out better both per project and=20
> on the site as a whole... for example the is no way to search=20
> for a specific project on gborg.. another example is the urls=20
> for each given project, compare:
> http://gborg.postgresql.org/project/pgweb/projdisplay.php
> vs. http://sourceforge.net/projects/phppgadmin/

You can omit the projdisplay.php, and I'm sure that 'projects' could be
symlinked to 'project'

Regards, Dave.