the user interface I hope noone ever seesgit-annexhttp://git-annex.branchable.com/devblog/day_41__onward/git-annexikiwiki2013-11-27T22:47:37ZEmail alerthttp://git-annex.branchable.com/devblog/day_41__onward/comment_1_a716c7b5a9ea3c949ff047cfb4e9a0a4/aarone2013-11-27T22:47:37Z2013-10-22T21:23:24Z
I have at least one git-annex repository where I seldom open the web UI, but rather have the assistant humming along in the background. I think for my use case it would be best to receive an email notification that the assistant had detected a problem, which would prompt me to open the web UI and perform the recovery.
excellent ideahttp://git-annex.branchable.com/devblog/day_41__onward/comment_2_33149e424cd5f03fac376288bcc4dfdc/joeyh.name2013-11-27T22:47:37Z2013-10-22T22:13:58Z
Added to my todo. I think it would require the system have an MTA though, I really don't want git-annex to grow to the point it can send email. <img src="http://git-annex.branchable.com/smileys/smile4.png" alt=";)" />
Please check if it needs help from the user firsthttp://git-annex.branchable.com/devblog/day_41__onward/comment_3_3b07503bd79089ad3ce3ddd7535ed116/JasonWoof2013-11-27T22:47:37Z2013-10-23T23:30:10Z
<p>Awesome that you're working on recovery, and recovery automation!</p>
<p>Please only bother the user if there is a serious problem <em>and</em> it can't be fixed without their help. Otherwise I fear people will learn to ignore your dialog boxes, like they do most dialog boxes. If you want to notify your user that some hard drive corruption happened (and it's been fixed already) then put a little yellow/orange line across somewhere with a warning message.</p>
<p>When I read to the part about how it can (probably) be fixed automatically, I got a flash of annoyance and thought "well, then fix it automatically, why are you bothering me?"</p>
<p>Please (if you aren't already) check if it can be automatically fixed without help from the user before telling the user about it. Then you can say "The data to fix this could not be reached, please plug in another repo or something."</p>