Re: [Userops] Userops Acid Test v0.1

[Alex Jordan]

I replied to this on the Pumpiverse[1], but I figured everyone on here
might be interested in bikeshedding:

> Data liberation is something I see missing from this - it should be 
> possible (even if not painless) to export all your data from a 
> particular userops system.
> Also, it would be nice if the system helped with surrounding network 
> infrastructure - for example, the DNS. Sandstorm.IO's Sandcats (IIRC 
> the name) is a good example of this.

Christopher said (replies inline):

> I'm really interested in making sure people are able to keep their 
> data, though I have two ponderings on this:
> 
> * If you are running your own system (or one for family and friends) 
> and have the data reproducibility requirement fulfilled, can't you just 
> move your data reasonably easily? I think "data liberation" might be 
> more for instances where someone is running something for you

I assume by "data reproducibility" you're referring to the "recoverable
data" section? I think that gets us 90% of the way there. The
infrastructure should already be in place, so the interface would just
need some sort of "export" option.

The main use case I see for this is moving between different userops
systems (i.e. different implementations).

> * up until now, "data liberation" is such an application-by-application 
> process, I can't think of any way to generalize it as a system...

I can imagine a system that contained hooks for data liberation, either
for the application or the packaging to consume. Again, most of the
infrastructure needed for this _should_ be in place for the backup
system, right?

 [1]: https://pump.strugee.net/alex/comment/akDrOqEeSKGL9sOIyYx24w

signature.asc
Description: OpenPGP digital signature