Next Gen mepo design

• Standard python directory structure

  • subdirs correspond to namespaces
  • run scripts go in bin

• Hierarchical/nested/recursive

  • operations (including clone) check for config file in each subrepository
  • top level uses some sort of marker to signify top

• Config file hidden

  • something like ./mepo/config.yaml (components.yaml if we think it really helps transition)

• config file updated after each mepo action

  • never hand edit mepo files
  • need to work through full list of mepo actions and agree on how captured state changes.