Re: Update on 'portal' changes

From: Alexey Borzov <borz_off(at)cs(dot)msu(dot)su>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-www(at)postgresql(dot)org
Subject: Re: Update on 'portal' changes
Date: 2004-03-08 17:11:25
Message-ID: 404CA93D.6030102@cs.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Hi!

Dave Page wrote:
>>Speaking of which, what is the real reason for keeping the
>>current website and the "next-generation" one in one project?
>>
>>Maybe a better approach would be to register a separate
>>project for the next-generation website (I think this was
>>already proposed here)?
>
> Because the project is for all the websites, not just the one you are
> working on.

OK, let's paraphrase: what is the reason for having one project for all websites
instead of one project per website? I got the impression that *different*
developers work on different websites...

> We *have* created a separate CVS module which should be more than enough
> segregation.

Can CVS write access be given for this module only?

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2004-03-08 17:18:37 Re: Update on 'portal' changes
Previous Message Dave Page 2004-03-08 17:05:27 Re: Update on 'portal' changes