Skip to content

Sprint Planning Meeting 2019 11 06

Jump to bottom
Erik Moeller edited this page Nov 6, 2019 · 1 revision

Sprint Planning Meeting, SecureDrop, November 6, 2019

Sprint timeframe: Beginning of Day (PST) 2019-11-06 to Beginning of Day (PST) 2019-11-20

0) Retrospective

What we said we would do:

SecureDrop Core: Test 4.14 kernels on supported hardware and prioritize findings Stretch: Resolve first compatibility issues

Sprint goal fully met: Built and tested 4.14 kernel, proposed fix for EFI issue discovered in hardware testing

SecureDrop Workstation: Solidify export workflow Resolve USB detection issues and implement near-final language and presentation of export-related dialogs for beta

Sprint goal partially met:

  • Good progress on narrowing down edge cases of USB detection failures
  • Received guidance from upstream and started prototyping auto-attachment
  • Further progress on UI blocked on final implementation choice (auto-attach vs. device menu)

SecureDrop Workstation: Resolve blockers for Buster migration and finalize migration plan Provision grsec kernel in Debian Buster VM template

Sprint goal partially met:

Additional accomplishments:

  • Landed fix for screenshot generation in docs (community PR by @DRGFreeman)
  • Landed high priority improvements to reply box styling and behavior in the SecureDrop client (community PRs by @deeplow)
  • Centralized logging service prototyped by Kushal

Other observations:

Things that went well:

  • Excellent UX/dev collaboration with deeplow on client changes!
  • good collaboration on kernel testing, appreciated emkll's patience with process.
  • Franklin met Allie! (co-working was incredibly productive; helped understand Export/Print interests a lot!)
  • Erik ALWAYS responds to my Slack pings
  • Kushal now has a fast Internet connection.
  • Meeting with Creviera about securedrop-client codebase

Things to improve:

  • Nina really needs a laptop for Qubes/Debian... now, for Print stuff w/ CUPS
  • the workflow to build, test, and deploy kernels is very manual and error prone. We did make some improvements this sprint by having distinct filenames and lfs repos, but we should document these steps in the future (I have started working on a google doc that describes the various steps)
    • New kernel build manager role for future builds, docs in progress

1) Review important dates and time commitments

Last sprint before

2019-11-06 to 2019-11-08: Conference: Conor at Aspiration Dev Summit
2019-11-08              : Time off: Jen (offset for hackathon), Allie 0.5 day, John 1 day, Erik a tiny bit
2019-11-09              : Aaron Swartz Day (remote hackathon)
2019-11-11              : US Holiday: Veteran's Day
2019-11-15              : Time off: Mickael 0.5 day
2019-11-18 to 2019-11-19: Conference: Mickael at PyCon Canada sprints
2019-11-19              : QA for SecureDrop 1.2.0 begins

After sprint period:

2019-12-03              : Tails 4.1 / SecureDrop 1.2.0

Time check: https://docs.google.com/spreadsheets/d/1v85RaG_lHeH5Vwg06VrcikvFD2TEIHDKQ4rR7tAVCLc/edit#gid=0

2) Agree on must-achieve sprint goals

  • SecureDrop Core: Land must-have deliverables for 1.2.0: grsec 4.14 kernel && systemd migration
  • SecureDrop Workstation: Resolve showstopper issues for workstation demos in week of November 11
  • SecureDrop Workstation: Finalize export USB logic (auto-attach vs. device manager) and remove persistent attachment to sd-export-usb

3) Task selection and estimation

https://docs.google.com/spreadsheets/d/1-nxnk3I7h1J0AYw4PH2JGBYyj9mVeZgouD7LphpicxM/edit#gid=0

4) Board review

https://github.com/orgs/freedomofpress/projects/1

Clone this wiki locally