content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: putting up modified 'portal'
Date: Wed, 18 Feb 2004 20:59:16 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B889F3E9@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] putting up modified 'portal'
Thread-Index: AcP2TfbDS5n7CqYjQPq1vvrAGucbngAEpoBQ
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <webmaster@letzplay.de>, <scrappy@postgresql.org>,
	<borz_off@cs.msu.su>
Cc: <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Andreas Grabm=FCller [mailto:webmaster@letzplay.de]=20
> Sent: 18 February 2004 18:38
> To: scrappy@postgresql.org; borz_off@cs.msu.su
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] putting up modified 'portal'
>=20
> I've now applied your new code (please note I have not=20
> changed anything so your hacks do still exist).
>=20
> However, I don't think it makes much sense to work this way.=20
> As it seems we can't give Alexey access to only one single=20
> module, what about creating a new project on gborg=20
> (postgresql.org 3.0 or something like that) where we can play=20
> without affecting anything on the current website?

No. There is no need for a new project. Once Alexey has proven himself as *=
everyone* has to (including myself), then we will give him CVS write access=
. Until then patches may be produced against CVS and applied by one of us.=
=20

One of the things I will be doing at some point is reworking things to upda=
te from CVS during site builds so from then on we will all work in scratch =
copies and commit changes to CVS (unlike currently when some of us work in =
the live version). Working this way will mean that CVS write access will ha=
ve to be as tightly controlled as write access to the docroot itself.

Regards, Dave.