division in sub projects (or not ?)

Hello,

I'm trying to fit some of my written source code to a good CVS directory 
structure.  Here at the KULeuven, we think about using sub projects under the 
"Orocos root directory".  Thus each sub project has its own src/ include/ 
doc/ directory, namespaces, etc... This emphasises the component-based 
approach of independent parts.  We would not make a difference between kernel 
space and user space code (since this should not be set fixed by Orocos).  
For "inter-component" communication / linking, we will use an "Orocos Wrapper 
Interface" (ORWIN :-) )  If you want to use a particular system call or a 
method of another component, you'll have to write a wrapper from ORWIN to 
your Operating System, Module or Component.

The selection of appropriate wrapper /module / component should be done by a 
"Configuration Agent" whose sole purpose is to combine hot spots with frozen 
spots and thus complete the framework (see glossary 
http://www.orocos.org/glossary.html ).  

I'd like to hear from other people how they see the "large" and the "small" 
of this project and how they think their contributions would integrate best.

kind regards,
Peter

PS : the name ORWIN was completely made up on the spot :-) Alternatives 
welcome !