-
Notifications
You must be signed in to change notification settings - Fork 685
Standup Notes 2018 10 30
Participants (alphabetical): Conor, Emmanuel, Erik, Jen, Kevin, Kushal, Mike, Mickael, Nicholas, Nina
Reminder: New sprint starts tomorrow - final pre-alpha sprint.
Yesterday: Mostly non-SD; revisited securedrop.org website changes, looking good.
Today: Will merge automatic upgrades Workstation PR (Josh just approved). Weblate migration! (See forum for updates). Eager to hear where Mike's at with nested virt! Holler if help needed. =)
Blockers: None
Yesterday: Started reviving the SF instance, support, non-SD EA work
Today: Finish reviving SF instance, intensive hardware search, standard support, non-SD work
Blockers: None
Support Sync is today! :-)
Yesterday: Hiring (3 phone screens); UX outreach (secured 2 new testers so far); start on sprint prep
Today: More hiring work (phone screens, task review, etc.), more sprint prep
Blockers: None
Working on client response workflow. PR for GUI only needs to be merged in independently of PR that will add gpg support, so we can encrypt replies. Once both are in, will wire them together so DB/backend will respond to actions in GUI.
(Jen prefers doing it in one PR)
Yesterday:
- Review / merged https://github.com/freedomofpress/securedrop-client/pull/81 (if there is a PR for any ticket on the alpha milestone that is not getting review, yell at me)
- Reprovisioned my Qubes workstation again so that I could test the client threading stuff in Qubes with the proxy
- Did test threading stuff
- Found minor issue https://github.com/freedomofpress/securedrop-client/issues/83 which I will fix as part of the decrypt file ticket
Today:
- Decrypt file ticket
- I have a doc with a test plan starting to take shape which I'm gonna share with you Kevin EOD so we can at least start testing current functionality
Blockers:
- The more people that want to get the client running in Qubes, the better at this point (so far me and Josh, but getting Kushal also would be 100 and anyone else that has the hardware - just kidding he did this! K is the best).
If I'm feeling up to it later, I'm going to continue my message downloading work, and help with thread-related stuff as needed. Thanks!
Yesterday: Fixing up functional testing PR
Today: Mostly support tasks. Reviewing docs PR, kernel testing, more support work.
Blockers: None
Yesterday: Started with issues pointed at me: #2, #30, #31. Also looking into package creation (#22). While working on this, found out that python-devutils binary wheel has different file naming system, had to release new version of hash compute tool. PR for debian package guidelines explaining this exception. Created PR #86 in securedrop-client which handles #2, #30, #31. Commented on details we discussed in UX/client sync.
Today:
Blockers: ^^ Need review
Yesterday: Got whole nested virt suite running. Hitting legit grsec failures. Can get time down to 29 mins.
Today: Running with that for now, may have to peg CI environment to only run per-PR
Blockers:
Yesterday: Working on debugging kernel issues. Only does not work on my NUC, asked Kev to sanity-check. Also looking into vanilla kernel build. Updated workstation threat model based on fixes introduced recently, e.g., automatic updates. Opened ticket for a CVE associated with requests package -- no impact, but will cause safety check fails. Did pass on update logic; some packages may not get updated, needs more manual testing.
Today:
Blockers:
Yesterday: [Tuesday] Reviewed the threading PR on GitHub. I also spent some time working with Kushal on packaging things. As requested by Jen, I've refactored the threading some more (stacked on Josh's PR) and submitted my work as #85 (which fixes #71 and #80). I also addressed #75 with the PR #87 (the client will automagically sync with the API every 5 minutes). US meeting late afternoon. Will not be able to attend stand-up due to a teaching commitment.
Today: [Wednesday] I'll pull off the next ticket on the tagged-for-alpha list or else do whatever Jen says I should do. FWIW, getting a sense of what to do next is really helpful! Please keep pushing work in my direction.
Blockers: None.
Yesterday:
Today: Going through GitHub to ensure that issues in progress for alpha or alpha stretch have UX screens/clickables. Research participants lined up, yay! In research cave.
Blockers: None