16:26:42 <+olasd> I don't think stuff depending on the storage should go in swh.model
16:26:50 <+olasd> even if it's an indirect hidden dependency
16:27:02 <+seirl> hmm, right
16:27:39 <+olasd> I mean, I agree that this should probably be more generic than being buried in the vault
16:27:54 <+olasd> but I'm not sure swh.model is the right place
16:28:46 <+seirl> maybe i can put it in swh.vault.to_disk in the meantime?
16:29:05 <+olasd> as it's a high-level storage operation it might make sense to make that a swh.storage submodule
16:29:22 <+seirl> swh.storage.to_disk?
16:29:35 <+seirl> that sounds pretty good to me
16:30:00 <+olasd> it sounds less weird (to me) than having it in swh.model

→ D288