Basic print/export support

[eloquence]

For the beta, we want to support two ways of moving documents off the SecureDrop Workstation:

• export to a storage medium attached to a USB port
• print to a supported printer

This involves a lot of work across the workstation repos. This epic tracks all must-have issues to provide basic print/export support.

Shared concerns

• Consider renaming VMs for clarity - Consider renaming VMs for clarity #285
• Package export code - Packaging securedrop export code #271

Export

• Finalize high level export approach - Finalize document export approach #84
• Create proof-of-concept implementation - Add sd-export VMs and basic export flow #259
• (UX) Complete UX design for basic export workflow - Beta Export Flow securedrop-ux#57
• Finalize metadata format for exports - Finalize export metadata format #280
• Return USB device state details as part of export attempts - Return export device state details as part of export attempts #264
• Implement pre-flight checks - Implement pre-flight check for USB export #281
• Handle filename conflicts - Handle filename conflicts during exports #270
• (Client) Implement basic export workflow - Add support for exporting documents/messages securedrop-client#21
• (Stretch) Detect disk space availability prior to export - [securedrop-export] Detect if sufficient storage space is available prior to exporting files securedrop-client#1739

Print

• Create proof-of-concept print workflow - Create proof-of-concept print workflow #267
• (UX) Complete UX design for basic print workflow - Beta Print Flow securedrop-ux#63
• Return printer job status to client
• Add support for common HP laser printer
• Select final print front-end - Switch printer front-end for SecureDrop Workstation securedrop-client#2156
• Ensure all supported file formats are printable - Ensure all supported file formats are printable #295
• (Client) Implement basic print workflow - Add support for printing documents securedrop-client#477
• Decide whether we should support user-installed printers (in sd-export, the DispVM template) instead of relying on fully unattended printer setup (which limits compatibility)

[eloquence]

We've delivered the core functionality we need for the pilot and there are several other follow-up tweaks not tracked in this epic, so it serves limited organizing purpose at this point. Closing, but note that several of the issues cross-referenced from here are still relevant, and we'll want to prioritize them for future iterations.