Projects to be integrated into repository

• ACC online / offline
  • simulation
  • control systems
  • lattices
• ERL online / offline
  • simulation
  • layout files
  • lattices
  • EPICS
• CHESS - most code currently not under version control
  • control / monitoring code
    • legacy & EPICS
  • motion control & DAQ macros (for program SPEC)
  • μ-controller ‘firmware’
  • data handling / analysis
  • web code (PHP, javascript)
  • EPICS and RTEMS code may be first to integrate, others are CHESS-specific
• ILC
• ACC-TA

Possible directory layout

/
 |
 +-branches - subtrees here reflecting all files in branches
 |
 +-tags - subtrees here reflecting all tagged files
 |
 +-trunk - mainline of repository (duplications of sub-components will
   |       be duplicated to some extent in branches and tags trees.
   |   
   +--Common (or global)
   |  |
   |  +--Documentation - repo organization notes, build system notes, 
   |  |                  how to build, links to wiki, other resources
   |  |
   |  +--Templates - build-file templates, examples
   |  |
   |  +--Build - working build-files, scripts to perform and 
   |  |          customize builds
   |  |
   |  +--Announce - place for pertinent announcements, mirrored on wiki
   |
   |
   +--Admin - administrative files for repository
   |
   |
   +--Project Class 1
   |  |
   |  +--Project 1 - for project code and docs
   |  |  |
   |  |  +--Makefile entity
   |  |  |
   |  |  +--Build - build files to initiate & support 
   |  |  |          project/metaproject construction
   |  |  |
   |  |  +--Documentation
   |  |  +--code
   |  |  +--modules
   |  |  +--include
   |  |  .  
   |  .  . (other project specific dirs)
   |  .  .
   |  .
   .  +--Project N
   .
   .
   +--Project Class N
   |
   |
   +--Packages - 3rd party packages required by various projects.
                 Maybe inside a Project Class?  Sufficiently
                 general ones might go in top level.