The current disscusion is good, but...

[Ken Evans <eros331 yahoo com>]

Maybe I'm jumping the gun here, so correct me if I'm
wrong but isn't discussing DBs vs. CVS a step we
aren't ready to take?  It a great discussion but I
thought there would be a plan of action first.

The theory goes that one of the first things we're
suppose to do is come up with a practical requirements
list.  At least that is the theory.  Everywhere I've
been, they've always been rushing a deadline so this
never happens.

I think it might be best to come up with one organized
requirements list that would later be broken up into:

*  front-end, 
   back-end

OR

*  front-end,
   middle tier(if we have so much dynamic content),
   back-end(back-end can only talk to middle tier,
security).  Also, the middle tier could do some
caching.

Then once the lists are put together, teams
(scriptors, backend, and DBAs or CVS maintainers) can
be made and each requirement could be argued over the
best way to do it.

In fact it might not even be wise to pick a language
to implement it all until the lists are complete and
everyone is sure they can easily, cleanly, quickly
fulfill the requirements.

We could have a quick discussion though to limit the
languages we want to explore as possibilities.  It
seems as though just about everyone knows PHP and that
90% of us know Perl and/or Python.  So maybe that
would be the limit of the languages that would be
candidates.

Anyhow let me know what you all think.  Obviously,
there are now quite a number of people in here that
have more real world experience than I do, so I'm
definitely not going to get offended.

I'm just trying to help this get started on the right
foot.  With the requirements in place, we could set
goals (milestones) and more easily plan for the
future.

Kenneth J. Evans

__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/