Hello,
are there any patterns or at least "good experience practices" for creating a structure of a configuration management repository, such a Perforce?
The repository should contain both source code, executables, project management artifacts and various design documents.
Obviously, the structure should be robust to changes, and be intuitive for the project members so they can easily locate the right place for their files.
Thanks,
Pavel