CVS Modularization

["Daniel E. Markle" <syntax@ashtech.net>]

I think we need to break the CVS modules down instead of having one huge
linuxkb module.  Here is what I propose, keep in mind this is just a draft
for comments:

www.linuxkb.org website updating, cvs permissions only to designated people.
Should probably be able to update/rollback these on demand by the module 
administrator for immediate verification.
----------------------------------------------------------------------------
static-web - website static content to be updated on site immediately 
        (todo lists, images, news items, etc.) stuff that we need to be able to
	update the main site with immediately.
dynamic-web - website dynamic scripts, used to generate site content, this
	would update the actual system, would not be used for testing.  Changes
	would be made here after testing using the pre-www site.  We need the
	capability here to roll back these changes easily in case it breaks the
	site for some reason.
backend-web - used to update core scripts and db, only usable by module admin.
	Any core scripts where mistakes could break the whole site.

pre-www.linuxkb.org test website areas:
---------------------------------------
static-pre - static content that we want developer comments on before posting
	to the main site.  Test layouts, images, etc.
dynamic-pre - dynamic website generation scripts to be tested and developed on
	before being put on the main site by the dynamic-web module admin.
db-pre - used to develop and test db maintainance and related scripts.
search-pre - used to develop and test backend search scripts and methods.
bizfinder-pre - an area for developers working on the business finder to work.

Undoubtedly I have missed a ton of stuff, and I may even be way off base,
send me your flames and I will absorb them ;)

-- 


-------------------
Daniel E. Markle
syntax@ashtech.net

Linux - The OS of the future.
Windows - Still using that legacy OS?
-------------------