-
Notifications
You must be signed in to change notification settings - Fork 685
Standup Notes 2018 10 25
Participants (alphabetical): Conor, Emmanuel, Erik, Jen, Kevin, Kushal, Mike, Mickael, Nina
Reminder: Extended meeting today
Yesterday: Pretty light day, patching up workstation PR for automatic updates.
Today: Mostly non-SD web/infra tasks, happy toget ^^ to the finish line if needed
Blockers: None
Yesterday: Support portal cleanup and checking in with post upgrade clients
Today: Support portal information cleanup, more checking in, hw search, plus standard support
Blockers: None
Nothing to escalate
Reminder: PTO tomorrow
Yesterday: Continued on client UI messages & MIME handling review. Closed MIME issue, should be good for taking stab at svs template config. Screening candidates for Sr. Software Eng role.
Today: 1 user research session w/ Nina; more hiring & non-SD work.
Blockers: None
Flagging https://github.com/freedomofpress/securedrop-workstation/commit/64bed2b10fdbc4aba0727a49be9b32b5866050ab Found few broken reference at documentation (https://docs.securedrop.org/en/release-0.10.0/). Will reise an issue for them.
Yesterday: - Reviewed merged status bar, reviewed download UI - started updating push logic in that star PR. I missed that during release fun my star PR got 👍'd, but i might just add the updated push logic to that PR for monday (not critical for next client package)
Today: - I might just add a wee commit adding the user feedback / file storage such that we can merge file download UI - Fix push logic if time permits
Blockers: None
Yesterday Continued client work, didn't get as much done as I expected :/
Today Will be in SF office starting in the early afternoon, will have uninterrupted time for client development -- syncing of source messages from server to client (https://github.com/freedomofpress/securedrop-client/issues/40)
Yesterday: Mostly support catch-up, docs for QA
Today: More on ^^, testing new version of shim package
Blockers: None -- waiting for PR review on time.sleeps
Yesterday: Gave talk on RPM. Reviewing open issues in workstation and client repos.
Today: Workstation - there's work on RPM packaging, will pick that up. Will review time.sleeps PR.
Blockers: None
Yesterday:
Today: Still on the nested virt work. Progressing, spinning up and down boxes, trying to get code to run as efficiently as possible.
Blockers: None
Yesterday: Pushed version string bump for kernels. Worked on workstation #172, ready for review
Today: Will update apt-test to those kernels. Working on #148 in securedrop-workstation (bug with TBB gone missing)
Blockers: None
Not working today
Yesterday:
Today: Discussed PR related to update story / UX implications. Testing at 11:30 AM PDT; debugging prototype.
Blockers: Moar research participants plz
- Any RPM packaging questions from Kushal?
- Critical path review
- The plan is early next week we are going to integrate the client into securedrop-workstation master, once the client functionality allowing the download, decryption, and viewing of messages and files is complete. That work is being done in:
- https://github.com/freedomofpress/securedrop-client/issues/19 Download files (PR is made)
- https://github.com/freedomofpress/securedrop-client/issues/66 Decrypt documents (smallish)
- https://github.com/freedomofpress/securedrop-client/issues/40 Download and DL messages for display in conversation view
- https://github.com/freedomofpress/securedrop-client/issues/20 View documents (i.e. open in DispVM, smallish)
- This will enable us to parallize more, i.e. we can do QA to shake out issues while we add additional client features (reply, source deletion, etc.) in preparation of another iteration
- The plan is early next week we are going to integrate the client into securedrop-workstation master, once the client functionality allowing the download, decryption, and viewing of messages and files is complete. That work is being done in:
Conor: We should be able to remove default make clean behavior -- once we get unattended updates in
Kushal is working on RPM package for dom0 - but don't have forward momentum on svs-disp yet
Conor: If we get RPM tomorrow, are we in good position to serve it? Mike: Really easy to throw it up :) bark bark
Sprint n+1 will likely involve SVS configuration, template hardening, client functionality/iteration, QA