Skip to content

Sprint Planning Meeting 2019 08 21

Jump to bottom
Erik Moeller edited this page Aug 21, 2019 · 1 revision

Sprint Planning Meeting, SecureDrop, August 21, 2019

Sprint timeframe: Beginning of Day (PDT) 2019-08-21 to Beginning of Day (PDT) 2019-09-04

0) Mini-retrospective

What we said we would do:

  1. SecureDrop Core: Land implementation of basic support for v3 onion services (including tailsconfig).

Sprint goal partially met: PRs for both issues close to done, follow-up issues identified.

  1. SecureDrop Core: Get resolution to securedrop-security #7 ready for QA and land resolution of related SD Core Issue.

Sprint goal partially met: PRs for both issues undergoing review.

  1. SecureDrop Workstation: Land minimal integration of existing export code in the SecureDrop Client, including a revision on the UI layer for presenting file actions, names & sizes.

Sprint goal partially met: Blocking dependencies for export integration resolved, PR for file widget redesign done, export integration just starting.

Other observations/comments:

  • Obviously too many fronts in parallel right now, leading to the kind of PR pile-up we've seen in the past. Shout-out to Kev for calling for reality check on release date; we could have done so earlier -- don't need to adhere to Tails calendar, look for opportunities to create breathing room where we can.

  • v3 is taking a lot of collab -- let's not view this as a negative, but more carefully build in such collaboration during planning of larger changes.

  • Deviation between prod/staging playbook caused at least one surprise during v3 testing, would be nice to combine these two at some point (I think Mike has advocated for this in the past): https://github.com/freedomofpress/securedrop/issues/3223

    • +1
    • Additional value could be gained from testing different site-specific config files - this could look like a new weekly CI job that would basically kick off different staging CI jobs (i.e. with different site-specifics) and then the testinfra test suite would need to parse that site-specific and then assert that the playbook did what is expected

  • Heavy collaboration on multiple branches, v3-related PRs developed in tandem, made possible by communicating specs

  • Test plan for Admin Workstation in v3 transition is complicated; we have many sdconfig paths now

  • Behind on testing HTTPS cert interaction with v3 (working on procuring for QA) - can at least do self-signed for QA

  • Having more complete specs prior to implementation would reduce overhead on collaboration on PRs

  • Finding issues in the v3 branch before QA time is a very good thing.

1) Review important dates and time commitments

Note: Due to Labour Day, this sprint has only 9 work days.

2019-08-19 to 2019-08-30: PTO: Mickael
2019-08-26              : PTO: John
2019-08-27              : SecureDrop QA & String Freeze (EOD PDT)
2019-08-26 to 2019-08-30: PTO: Kev
2019-08-30              : PTO: Erik (tentative)
2019-09-02              : US/Canada/India Holiday

After sprint period:

2019-09-10              : SecureDrop 1.0.0 Pre-Release Announcement
2019-09-17              : SecureDrop 1.0.0 Release

Time check: https://docs.google.com/spreadsheets/d/1QYeo9NpH7FR3hJqXa3xRTW927Ma-6H7eBIusx4N-I9c/edit#gid=0

2) Agree on must-achieve sprint goals

Same as above (v3 support, deletion fixes, basic export integration), including resolution of v3 follow-up issues that have been identified as release blockers.

3) Task selection and estimation

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

4) Abbreviated standup (if we have time)

Allie
  • Focusing in export
Conor
  • v3 testing and SSH over local issue
Erik
  • UI refresh , docs
Jen
  • SecureDrop-Security issue
John
  • Tests for SecureDrop-Security issue
Kushal

Today:

  • reviewed v3 tailsconfig PR
  • Lost 2 hours into installing Tails on a vm

Tomorrow:

  • Oh my v3! branch

Blockers or Asks:

  • None
Clone this wiki locally