Had debate over what form an infrastructure should take -- tool or project centric? In most cases 'project' seems the way to go. However, for tools that are very localized in their implementation and use -- 'tool' may be the way to go.
For instance, WebFocus is broken out toolwise by:
Report/Data Server (PDF batch based reporting)
Web Server (MRE ~ HTML based reporting)
WebFocus has ability to 're-use' components via includes and it's data access is
tied pretty tightly to meta data on the webfocus server. In my mind -- that would
indicate for a subversion structure that is pretty reflective of the WebFocus app path.
This is what we're trying -- I'll report back on how it actually works out.