Proposed repository structure

I apologize to everyone for being out of the loop for so long; I had  
some personal issues come up. In any case, I've been talking with  
Johannes and Pierre, and we've come up with the following proposed SVN  
repository structure. Comments are invited and encouraged.

- All projects will use the standard SVN trunk/ tags/ branches/  
structure.
    Pros: Works with various tools that expect it, mirrors CVS'  
behavior for those not used to SVN
    Cons: Less flexible

- Zend and TSRM will remain separate projects from php-src/
    Pros: Again, mirrors the old CVS layout
    Cons: It's ugly!

- All -web/ projects will lose the -web/ suffix and be put under a  
web/ master directory.
    Pros: Organizationally more structured
    Cons: It's a change from CVS

- Obsolete projects which aren't touched anymore will NOT be converted  
from CVS
    Pros: Avoids clutter in SVN
    Cons: CVS would have to be maintained indefinitely to preserve the  
history

Here's a quick overview of the proposed root of the SVN repository:

pear/
  <various pear modules>
pecl/
  <various pecl modules>
php-doc/
php-src/
tsrm/
web/
  php/
  php-doc/
  php-master/
  smarty/
  <etc.>
zend/ <this will be Zend 2>

-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."