SWF / MVC write-up

[Tom Zeller]

>> Moving all svn projects to the top level, meaning no more utilities/
>> and extensions/, would enable the use of an Eclipse Team Project Set
>> file to set up a workspace from scratch
>
> I'm not familiar with that, sounds cool.

I tend to have lots of workspaces, so I have been trying importing via
an Eclipse Project Set file to checkout from svn and organize into
working sets automatically. The issue is that the utilties/ and
extensions/ and parent-projects/ parent paths are removed during
checkout, all projects are at the same top level in the workspace
filesystem.

>> _and_ the scripts in the
>> parent projects could be modified once to work.
>
> Don't know what you mean, but if something doesn't work now and this
> would make it work, that would be good obviously.

It's just a one-liner in add-module.sh.

> My only potential concern with making all new repos is:  I'm a big fan
> of not losing svn history (unlike Chad).  So if we were going to do
> this, IMHO we would want to do it right and make sure each new repo
> wound up with all its original history intact.  So either 1) literally
> copy the utilities/extensions repos N times, and then in each delete all
> but the one that's supposed to stay, or 2) use the svn dumpfilter (?)
> stuff to filter a dump file to get just the relevant subtree, and then
> import it into a fresh repo.

I like keeping svn history. Not sure how much work that would be to
rearrange and keep history.