Closed perolavsvendsen closed 8 months ago
Refinement 25/09/23
Context:
Plan:
ert
requirement from fmu-sumo
sim2sumo
to repo fmu-sumo-sim2sumo
(namespace: fmu.sumo.sim2sumo)fmu-sumo-sim2sumo
to Komodo. Test.ecl2df
requirement from fmu-sumo
sim2sumo
from fmu-sumo
State now: fmu-sumo as it was prior to sim2sumo
uploader
to repo fmu-sumo-uploader
(namespace still fmu.sumo.uploader)uploader
and sim2sumo
.State now: Separate repositories
Still works as-is in Komodo environment
fmu-sumo
still contains explorer
- but only that.
[x] Consider rebuilding/refactoring the uploader
(Wait until it is established in its own repo)
Longer term:
fmu-sumo
to fmu-sumo-explorer
. May not be necessary.Key philosophical question: Do we want to have many, small, light repos - or fewer, larger repos?
Requirements
explorer
Current known users
Other topics
RegularSurface
objects/instances).fmu-sumo
(not correct after repo split) (edit: separate issue created)fmu-sumo-uploader
. Mainly for reference? (edit: separate issue created)fmu-sumo-sim2sumo
. Mainly for reference? (edit: separate issue created)Consider if (main) documentation on the front-end should contain the user-facing documentation, or if we want to use ReadTheDocs also for that (or just for the API reference, mainly targeting developers).
Repositories split. Closing.
Currently, both the
explorer
, theuploader
and theutilities
are in the same repository. This may not scale very well, as seen in e.g. #214. In general, the modules does not share code, but share requirements. While the uploader is depending on packages only available on Unix, the explorer needs to run on Windows.fmu.sumo.explorer
)fmu.sumo.uploader
)fmu.sumo.sim2sumo
) (?)