Message-ID: <4006C6BF.802@cs.msu.su>
Date: Thu, 15 Jan 2004 19:58:39 +0300
From: Alexey Borzov <borz_off@cs.msu.su>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
MIME-Version: 1.0
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: Dave Page <dpage@vale-housing.co.uk>, pgsql-www@postgresql.org
Subject: Re: Todo for 'portal', programmers perspective
References: <03AF4E498C591348A42FC93DEA9661B8720494@mail.vale-housing.co.uk>
	<1074184254.17856.416.camel@camel>
In-Reply-To: <1074184254.17856.416.camel@camel>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

Robert Treat wrote:
>>>1) If all the static content (i.e. the content that does not change
>>>often) is stored in the database and is editable only through 
>>>web-interface then there is a bottleneck: the person who 
>>>gives access to web-interface. If the interface is not robust 
>>>enough to let not-quite-trusted people use it, then the 
>>>bottleneck is even more narrow. On the other hand, if the 
>>>content is available in public CVS, then every one may check 
>>>it out and edit it and later submit for inclusion.
>>
>>The same bottleneck applies either way as those with access to the admin
>>interface are basically those with cvs commit access. Still, CVS does
>>give more convenient read-only access than the web does.
>>
> 
> 
> I'd like to point out that from a management standpoint, I think we've
> been fairly responsive when it comes to news & events, so I don't see a
> bottleneck there. On top of that, ISTM that it is easier to for end
> users to submit news and to get it approved if its in a web/db based
> system. 

I want to once again point out that this applied to static content, not 
to news and events which should of course be managed through web interface.