On Thu, Sep 4, 2008 at 2:20 PM, Stephen John Smoogen <smooge(a)gmail.com> wrote:
2008/9/4 Karsten 'quaid' Wade <kwade(a)redhat.com>:
> Ping project: any reaction to this?
>
> If we're all good, I'll start hammering the scope list in to final shape
> this afternoon.
>
Ok its very aggressive. I am not sure there is any time in there for
screwups like finding out that the CMS falls over at 400 continuous
users...
For scope, I can see the need for the following:
1) Securable.
2) Easy to create custom CSS
3) Able to create cache/static pages versus using a 'squid' proxy to
do it for you.
4) Able to handle large loads for static pages.
5) Securable.
6) What parts of the site will it cover:
Front page, licenses, etc.
Ok now a question about:
Scope need 2008-09-02 2008-09-09
Vet solutions 2008-09-09 2008-09-17
Publictest instance 2008-09-17 2008-09-23
Install 2008-09-17 2008-09-18
CSS 2008-09-18 2008-09-23
Content load 2008-09-18 2008-09-23
To vet solutions, you really need to do public tests.. should it be:
Initial vetting
publictest instances
install
css
content load
Final vetting
--
Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"