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?
