public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alexey Borzov <[email protected]>
To: Robert Treat <[email protected]>
Cc: Dave Page <[email protected]>
Cc: [email protected]
Subject: Re: Todo for 'portal', programmers perspective
Date: Thu, 15 Jan 2004 19:58:39 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <1074184254.17856.416.camel@camel>
References: <[email protected]>
	<1074184254.17856.416.camel@camel>

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.

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Todo for 'portal', programmers perspective
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox