Dear DVC team,
Thank you for the great work and coming with an agnostic approach for DVC!
It seems that a) one could create a tar.gz of the directory used as a DVC remote and b) that someone else could unpack this directory somewhere else and use it as a local remote.
Is there any counter-argument for distributing an archive of a DVC remote?
I have seen that it seems fine according to Copying a dvc repository. But it was in another context (filesystem specificities).
Why archiving a DVC remote? The idea is to share publicly a snapshot of a DVC remote.
One way could be to
dvc push to a specific public remote when someone would want to create a snapshot. However, this implies two things one might not want. First, this requires a dedicated public server. Second, this prevents from having a DOI for the snapshot.
Would you have a better suggestion than distributing an archive to share a snapshot of a DVC remote?