Kevin O'Gorman

General sentiment is that we could just have the config in the dom0 user home dir (`$HOME/.config/securedrop-workstation`?), allowing us to leverage Qubes own backup functionality, but more discussion required as...

moving to ~/.config is still the best option and is an easy fix if done for 4.2, as we don't have to worry about migrations

Already in progress as part of the pilot migration script - needs to be promoted to the repo proper.

To the first point, IMO it's better in general to be able to define what keys are expected to be present, so you can tell if there are are deviations...

Yikes. Probably not a regression but it is a nasty bug in backup/restore procedure when restoring over updated data. I think one mitigating factor in practice is that the inaccessible...

running the orphaned submission job as part of the restore operation seems doable. We'd need to be more intentional about quiescing the app first tho, otherwise there would be more...

Closing this initial ticket with the changes in https://github.com/freedomofpress/securedrop-dev-docs/pull/191 - @ben-grande or others, please feel free to make further reccomendations!

Good stuff @deeplow - there might be an argument for just dropping the client app print functionality altogether, letting the user open the file in the appropriate viewer app and...

Thumbs up from me, we keep the release/u.v.0 branch around anyway, can easily use it for subsequent hotfixes.

Also relevant to potential system integrity checks. There's some outstanding scope questions: - do we want to push notices from server to client? - do we want to push notices...