Skip to content

Sprint Planning Meeting 2018 06 27

Jump to bottom
Erik Moeller edited this page Jun 27, 2018 · 2 revisions

Sprint Planning Meeting, SecureDrop, June 27, 2018

Sprint timeframe: BOD 6/27-BOD-7/11 BOD

0) Mini retro (max 15 minutes)

What did we get done? What do we want to change?

  • Kushal: Testing via Tor works really well if you have a faster network
  • Conor: QA Matrix: keep/iterate
  • Kushal: More detailed test plan would be useful
  • Jen: We have a maintainer guide that has those detailed steps. There's a balance between writing detailed docs and automating some of those steps. Acceptance tests should just be automated.
  • Kushal: Testing steps are really useful for new people.
  • Jen: QA section in docs would be useful.
  • Erik: Possibly something for Newsroom Support Engineer to take on.
  • Conor: Ran into some new friction with apt pinning on builder dependencies. Can lead to surprises in release flow. Could stamp a release as final with the tag.
  • Conor: Still getting into testing the 1U servers. Would be good to have more of that in the future.
  • Mike: Serial login might be useful. Keeping it in SF keeps burden on SF team.
  • Emmanuel: Would be down for that, shipping hardware across borders not fun :)
  • Kushal: Bare metal box for automated testing would be useful

1) Review important dates and time commitments.

Ensure we capture PTO/holidays (incl international).

2018-06-28 to 2018-06-30: Travel: Loic and Bernard at TCIJ conference (UX research)
2018-06-29:               Travel: Erik at OpenSourceBridge conference
2018-07-04:               Holiday: Independence Day; day off for all FPF employees
2018-07-09:               New hire: Newsroom Support Engineer starts at FPF

Time commitments: https://docs.google.com/spreadsheets/d/1iIGE0G-a58jUAaPeOC2WA-IzA3HEp0Hw4PCDoFWJ4io/edit#gid=0

2) Review our tools:

3) Decide on must-accomplish sprint goals. Proposed:

  • Land API in develop, targeting to ship it with SecureDrop 0.9.0
  • Create prototype workflow for distributing workstation code as packages
  • Automate pre-release application acceptance testing

4) We try to stick to the sprint backlog except for:

  • urgent bug fixes [outage level]
  • urgent security fixes
  • quick (< 1 hour) community PR merges + comments -- alternatively, communicate that PR will be handled next sprint
  • responding to issues

5) Estimate and pick tasks for sprint backlog => screenshare

Consider tasks not in the spreadsheet: bugs, PRs, other urgent issues

6) Mini standup

Conor will try to unblock Harris on web tasks

Clone this wiki locally