| [stem-dev] SVN Directory Structure |
Hi all,
On the call today, there was a discussion about directory structure for the SVN move. It was decided that we should follow a consistent naming scheme to what other Eclipse projects are using.
For SVN, you have the three default roots, used for tagged revision control:
- trunk
- tags
- branches
Some Eclipse Projects are moving toward a more standardized sub-convention based on workspace project type.
For example, in the Equinox repository, in the trunk they have:
- compendium
- components
- framework
- incubator
.. etc
and then inside of some of those directories, you see:
- bundles
- features
- examples
- tests
In my opinion, separating bundles, features, examples, and tests is a good strategy (although it slightly complicates checkout). Should there be any higher granularity to the separation (maybe data, models, or geography?) Also, should there be a higher level separation between logical components of STEM (core, diseases, UI, etc)?
-Matt