SVN Repository Structure

Proposed structure:-

---- external                (Drupal core and contrib modules unedited in any way)
---- trunk                   (nabuur.com as running on prod)
---- branches ---- kester    (individual contributors branches)
             |---- frans
             |---- rolf
             |---- wales
             |---- etc...

External

For now it's going to be built as external/current only without tagging, but with scope to create.
It (will) contain  CVS checkouts at tags, or in rare (-dev) cases branches; and svn:externals for required libraries (eg. tinymce)
This may be useful, if not it could be dropped.

Trunk

Should be able to be deployed on prod most of the time. There isn't a live revision, for now major changes can be worked in developers branches.
There are svn:ignore for obvious developer modules: devel?, update_status?, cvs_deploy?

Each install's structure

To aid separation of core, contrib, and custom modules the structure of each install is structured:-

---- drupal                 (Drupal core)
---- sites  ---- all        (drupal.org contrib modules and themes)
            --- default     (nabuur specific modules and themes)

There is a sym-link (checked into svn) in drupal to ../sites. Separation like this should assist any future tagging also.

A list of /sites/all and /site/default modules is in the modules index page