UX meeting 20190606

Attendance + Agenda

Attending: @ninavizz, @eloquence, @redshiftzero, @creviera, @huertanix, John, Olivia

Discuss:
- (5min) Introduce "LearningDesign" as a projects category
  - Print or digital materials created to help guide users in their use of SecureDrop, and in a more easily consumable, enjoyable, and absorbable fashion than RTD
  - Simplified SD ecosystem map, terminology poster, both treeware examples of good first jabs.
  - Great volunteer graphic design opties
    - Large community of do-gooder visual/graphic designers; need to get more organized w/ ticketed/labeled projects, before doing any outreach.
- (10min) Introduce to get thinking about: When to 1.0 SecureDrop?
- (20min) Footer + .onion TL;DR Safety 411_ page goodness
- (15min) Next step decisions for Source UI in 0.14 and beyond
  - SD #4500-3 have been created for color things (CSS and images)—what should be next??
Design Review:
- nope
Been Readin' + Shoutouts:
- Cross-posted this from our #training channel, to the SimplySecure Slack. Lotsa great discussion!
  - Make this into a wall poster for newsroom SecureDrop rooms? "I’d almost want to see it in a table format instead like, term, definition, usage"
  - "The emphasis it seems is on language which has been overlooked for quite some time but is actually a barrier to accessing information"
  - Lotsa "why PDF?!" discussion, which one poster astutely pointed-out is beneficial to Global South users where connectivity is limited.

David:
- Quickstart guide already kicked around
- General concept of "Learning Design" kicked around
- Work Hazard poster idea kicked around (don't scan QR codes, things to not do in SD)
- Is GitHub the right place? Could Dribble work?
Erik:
- Important to provide clear paths for design contributors
- Ecosystem map, a good example
Nina:
- GH tickets recommended to include a Problem summary, anticipated users, and links to related materials; useful to point folks to for soliciting interest... next-steps potential meet-n-chat?
David:
- Clarifies, "Just threw-out Dribble"

Jen: We should have a "breaking change" to mark this?
- Python 3?
- v3 Onion services (which we have to support at some point this year?)
  - Beginning of September?
Erik: 0.xx speaks to development-oriented releases
- How does the SD mainline version correspond to Workstation?
Jen: How many people really do look at these numbers?
- Nina: users have been observed in general webapp testing to pay attention, but w/ actual Sources its obvs unknown
Erik: Burden more likely heavy on IT department evaluators

David/Erik/Jen: "Be aware that some journalists review the metadata in your documents"
- How to address issue of informed consent in metadata w/ Sources, abreast newsroom desires to use or potential to misues?
Erik: Invites jen to look at What do you think of the GDoc?
Erik: The preamble on that wireframe is waaaay too long
David:
- Would be good to ask newsrooms about how much they rely on file metadata; may or may not be as strong of a need as we're assuming
- This should be on the same page with a news org
Erik:
- Will get input from Micah
- Jen, is there other stuff you would consider as blockers for implementation?
Jen: Nope! Also, Saptak's CSS super-tooltip PR just got merged, so hover cards are a go!
- Can we share entire document with Micah? Erik: yes!
Nina: Seeking content evaluation w/in context of wireframe to consider page hierarchies, fold presence, and ability to break-up info.

Color issues look good to Erik
Color issues look good to Jen
Erik cites to team that it will change the default logo in both Journalist and Admin UIs
Very visible change
Time's out — will review next-step Source UI priorities, next time!