content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: progress update, some questions
Date: Wed, 21 Apr 2004 13:53:13 +0100
Message-ID: <03AF4E498C591348A42FC93DEA9661B889FAEE@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] progress update, some questions
Thread-Index: AcQnnV6eeD41L8+UTSeOiDiS/nonmQAAXf4Q
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Alexey Borzov" <borz_off@cs.msu.su>, <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Alexey Borzov [mailto:borz_off@cs.msu.su]=20
> Sent: 21 April 2004 13:34
> To: pgsql-www@postgresql.org
> Subject: [pgsql-www] progress update, some questions
>=20
> Greetings.
>=20
> I almost finished the work on user-level form submits=20
> (surveys, bugs, doc comments, events and news) and have a few=20
> questions.
>=20
> 1) Is 'active' field in 'events' table really needed? Maybe=20
> just consider the events with end date in the future as valid?

No, that field is now obsolete.

> 2) Bug submit through the website just increments some=20
> sequence but the bug itself is not stored in the database. Is=20
> this the expected behaviour? What came out of a lengthy=20
> discussion about a "real" bug tracker?

Yes, that is the intended behaviour for the moment.

> 3) There is *no* moderation at all for the doc comments, I=20
> suppose? You know why PHP's have such a good signal-to-noise=20
> ratio? Here is the
> reason: http://lists.php.net/group.php?group=3Dphp.notes

There is no moderation, though I believe some of the docs guys go
through them before any releases to incorporate anything useful.=20

Feel free to add some moderation if you like - an email to the list with
a link to an 'approve' script in /admin would do the job I guess.

Regards Dave.