content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [pgsql-advocacy] Server unreliability
Date: Wed, 29 Sep 2004 21:10:38 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE475DBA@algol.sollentuna.se>
Thread-Topic: [pgsql-advocacy] Server unreliability
Thread-Index: AcSmVblCp2lao6EgQU+8xoS71pnMiQAAeEDg
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Josh Berkus" <josh@agliodbs.com>,
	<pgsql-advocacy@postgresql.org>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>,
	"PostgreSQL www" <pgsql-www@postgresql.org>

> > We have been talking about a new web page layout for years at this=20
> > point.  I almost don't care if they just put a dancing bear=20
> up on the=20
> > web site.  Let's do something!
>=20
> I'd suggest finding some money to sponsor somebody full-time=20
> for a month to accomplish the migration to the new web=20
> structure, which is more-or-less=20
> finished.   That's what's holding us up right now AFAIK.

What kind of work is required for this, precisely? Is it coding, or just
moving plain content over? If it's just plain content, how much work
would it be to make an interface so several different people can do just
a couple of pages each in a fully distributed way?=20

Is there a list somewhere on what needs to be done (like the TODO list)?
I see a few on the gborg site, but surely that's not all that remains?
(they're all techdocs only..)


//Magnus