-
Notifications
You must be signed in to change notification settings - Fork 685
Sprint Planning Meeting 2019 06 12
What we said we would do:
1. SecureDrop Workstation: Solidify queue operation and transition to it for core client operations (replies, message downloads)
Sprint goal partially met:
- Replies are now sent using the general queue
- Message sync (download+decrypt) now occurs whenever there is a metadata sync with
- Messages are downloaded and decrypted via MessageDownloadJob jobs
- Significant refactoring of queue codebase for maintainability
Pending:
- https://github.com/freedomofpress/securedrop-client/pull/404 - De-auth queue when user logs outs, restart threads if they fail
- https://github.com/freedomofpress/securedrop-client/pull/409 - More refactoring: Add a DownloadJob class
- https://github.com/freedomofpress/securedrop-client/issues/384 (WIP in branch) - Enable configurable number of retries for each job
- https://github.com/freedomofpress/securedrop-client/issues/412 - Star/unstar sources using general queue
2. SecureDrop Core: Significantly lower CI footprint by eliminating unnecessary jobs and optimizing resources
Sprint goal met:
- PRs from forks will now use the same rules as PRs from branches
- Builder image update PRs will no longer run unnecessary tests
3. SecureDrop Core: Address mod_wsgi blocker for Python 3 migration: https://github.com/freedomofpress/securedrop/issues/4292
Sprint goal partially met:
- Agreed upon implementation strategy and WIP PR: https://github.com/freedomofpress/securedrop/pull/4518
Free-form comments
Vigorous discussion of implementation ahead of time, e.g. mod_wsgi changes. Involves large subset of team in planning, eases review.
Desired CI improvements are clarifying, including nightly builds for packages and selective logic in PR diffs.
In general Qubes remains a pain point (kushal).
Who's using Qubes right now as their daily driver?
-
Kushal, mickael, Conor, Kev
-
Common pain points are device attachment, video conferencing
-
Automatic VM updates trigger at worst possible time -> this could impact beta deployments
Possible actions re updater:
- Limit to SD-related VMs
- Does it actually need updates?
Appreciate Harris jumping-in to make Wagtail updates asap for survey; that said, to support ongoing research it needs to be a high priority to adopt a self-hosted survey tool as resources become available (which clearly ain't this quarter or next!).
2019-06-12 : PTO: Kushal (partial)
2019-06-17 : PTO 1/2 day, Mickael
: PTO 1/2 day, John
2019-06-19 : Travel: Kushal (RootConf) - should not impact work availability
2019-06-21 : Kushal's talk in RootConf - entire day
2019-06-24 : Travel: Kushal (RootConf) - should not impact work availability; Holiday: Mickael (Saint-Jean-Baptiste Day)
2019-06-25 : SecureDrop 0.14.0 QA and String Freeze
2019-06-25 : PTO: Allie
After this sprint:
2019-07-07 : SecureDrop 0.14.0 Translation Freeze
2019-07-09 : SecureDrop 0.14.0 Release
Time check: https://docs.google.com/spreadsheets/d/1Dki-1GKgQompU1uyMRcfvo9GE6KfKFOpfrKSxf3fgsQ/edit#gid=0
Proposed:
-
SecureDrop Workstation: Address all non-infra dependencies to enable nightly builds of SecureDrop Workstation Debian packages
-
SecureDrop Workstation: Create working prototype of print functionality and a clear implementation plan for print/export iteration 1
-
SecureDrop Core: Transition to Python 3 as part of SecureDrop 0.14.0 (mod_wsgi change, dev env changes, but NOT dh-virtualenv change and NOT securedrop-admin)
https://docs.google.com/spreadsheets/d/1DU3aVJ_tTXzi9tRF94oyEXUwLkG4sW7rqNiPH7qzc0k/edit#gid=0