Assign severities to TODO items

[redundancy]

Assign severities to TODO items

[Redundancy]

I'll go through these this weekend and try and clean up and add information.

In terms of the major blocker to production usage - as long as you're happy with the functionality available now, my biggest concern is that although the code is tested, it's not hardened against real-life issues like connection failures or data corruption, and the test cases are not extensive for a tool intended to be used across a potentially higher-latency WAN connection. It also has absolutely nothing at the moment for setting file access flags / ownership etc.

While I'm reasonably happy with the library, the CLI interface isn't in any way mature (and it might not communicate failure cases clearly or with the correct error codes).

So, I wouldn't want to currently make any guarantees on the CLI "interface", because it probably needs a lot more attention and changes, which leads me to really want to separate that into its own repository, and use vendoring to properly control the dependencies.

Ultimately, I think it would be easiest to put into production if you were willing to run rsync (potentially) redundantly against the result of gosync for a while in order to establish confidence that it was a no-op consistently.