-
Notifications
You must be signed in to change notification settings - Fork 686
Standup Notes 2019 02 15
Erik Moeller edited this page Feb 16, 2019
·
2 revisions
(Async update)
Yesterday:
- Investigated codename/journalist designation "Content deleted" bug (https://github.com/freedomofpress/securedrop-client/issues/238), discussed a couple different ways to fix this with @redshiftzero
- Made and closed a PR (without merging) for Issue 238 above because further discussion was needed. Spent time reading and trying to understand how JI+SVS is different than the client wrt data transfers and the codename change feature.
- Partial review of "add alembic tests" https://github.com/freedomofpress/securedrop-client/pull/241
Today:
- Respond to @deeplow https://github.com/freedomofpress/securedrop-client/issues/144#issuecomment-463971704
- Respond to @redshiftzero https://github.com/freedomofpress/securedrop-client/issues/238#issuecomment-463864914
- Implement alternative solution for Issue 238
- Pair with @eloquence on Qubes and QA setup, review docs on SD architecture
Blockers:
- None
Yesterday:
- Mostly non-SD web/infra tasks
- Ongoing SDO repo audit
Today:
- Mostly non-SD web/infra tasks
- Ongoing SDO repo audit
Blockers:
- None
Yesterday:
- Fair bit of non-SD work (admin/IT policy land)
- Continued work w/ Nina (who's been doing the heavy lifting for the UI) on the NoScript warning messaging
- Prepped initial draft client spec for "flag for reply" https://github.com/freedomofpress/securedrop-client/issues/247 & added to must-do user stories for beta
- Finished "upgrade in place" docs with input from Conor, started draft PR - https://github.com/freedomofpress/securedrop/pull/4140
Today:
- Co-working with Allie, SecureDrop-on-hardware and Qubes walkthrough
- Will take stab at "reinstall via backup hardware" Xenial docs bits I can do without doing a reinstall myself
- More work on NoScript warning messaging
- May take stab at pre-release announcement as time allows
Blockers:
Can't do much on the "reinstall on backup hardware" docs without someone to drive the initial invsetigation / notes
Yesterday:
- my 1:1 day so meeting heavy
- finished fresh install on xenial on hardware, all went smoothly
- tested PR fixing #4109 on hardware as that was blocking merge, approved
Today:
- mostly helping get 0.12.0~rc2 up before the weekend as needed
Blockers:
- None
Yesterday: review/merge/backport of 0.12.0 PRs, there is an issue with ci for all PRs targeting release/0.12.0 branch (investigating and opened https://github.com/freedomofpress/securedrop/issues/4144)
Today: learning time
Blockers:
- CI Failures on PRs to 0.12.0 branch, debugged and fix is pushed but need review (https://github.com/freedomofpress/securedrop/pull/4145)
Yesterday:
- found cause of bug https://github.com/freedomofpress/securedrop-client/issues/144
- worked a bit on a solution
Today:
- small success on making an effective and simple solution
Blockers:
- detecting new messages might need some restucturing of the code. In the structure it seems I ended up producing some convoluted code to reach what was supposed to be simple