Skip to content

Mono-repository-structure #263

@frigusgulo

Description

@frigusgulo

Ive been thinking of a few ways to "balkanize" this code base. I think the most practical way to do this is to seperate functionality into 3 seperate "packages".

  1. parsing logic (i.e. sonardyne processing, novatel processing, tiledb routing)
  2. workflow logic, so our workspace management and pipeline management logic gets seperated and treats parsing logic as a dependency
  3. command line logic, this becomes its own package as well.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions