-
Notifications
You must be signed in to change notification settings - Fork 685
Sprint Planning Meeting 2021 08 04
-
Do we want to continue with asynchronous standups on Tuesday/Thursday?
-
+1, I'm a fan. Can dovetail nicely with ad-hoc meetings too (see below)
-
I like this one, easier due to my timezone.
-
Definitely felt this as lower contact with the rest of the team while I (Cory) was part-time Tuesday – Thursday; think it will be less of an impedance now that I'm full-time Monday - Thursday. +1
- great point cfm, thanks. we also are silent on gitter those days, we should be mindful of passive watchers seeing less activity from us.
-
-
+1, like not being interrupted, but maybe add optional working group standup (server/ws) once a week to allay others' concerns?+1
-
-
Do we want to continue with simplified sprint planning process?
- +1, haven't seen much of it yet =) -Conor +1
-
How do we best convene technical meetings & informal chats?
-
with or without any regular standing meetings?
-
given that tues/thurs are async, strikes me as a great time to call ad-hoc meetings (preferably with 1-2d notice) on tech deep dives. e.g. Allie just called a dep mgmt meeting recently around that time, worked well.+1 +1
-
Ideally we would have fewer standing meetings + good inter-team communication, but I feel like it's difficult to get everyone together to talk without much notice (unlike being in a physical office). It's much harder to have regular conversations with the team without a physical office, and waiting for someone to respond to my github comment or DM doesn't feel the same.
^ +1
- Getting calendar free is easier to discuss more technical things during the week.
-
Proposal 1: Declare Tuesday / Thursday 8:30 AM - 9:30 AM PDT to be free of scheduled meetings but open to unscheduled ad hoc chatter
Proposal 1a: Declare Mon-Thur 8:30 AM - 9:30 AM PDT to be free of recurring meetings when we all try to be available more to our team for in-person calls if needed+1+1
Proposal 2: Ping people as you feel, people can check those messages when they check slack and reply back. 1 message or 20 lines, everything is okay.
Proposal 3: Consider porting DMs to group messaging where appropriate, to increase visibility and create an office-like environment. +1+1+1+1
- SecureDrop 2.0.1 has been released
- Safe Deletion PR for SecureDrop Client was merged
- Reproducible builds in SecureDrop Workstation should be fixed per https://github.com/freedomofpress/securedrop-debian-packaging/pull/254
- New kernels and 2.0.2 RC1 packages have been prepared for testing
- A new version of SecureDrop SDK has been released
- Major improvements to SecureDrop accessibility are close to merge
- We published secure-fs and it is ready for use
- We have begun setting SecureDrop Client up for internationalization via Weblate
- HTTPS on Source Interface is now TLSv1.3 only
- We held a mini-summit during which we:
- discussed overall team health & process sustainability
- started capacity planning for the remainder of the year
- reviewed our findings from the SecureDrop Workstation pilot to-date
- prioritized work on the SecureDrop Workstation for the remainder of the year
2021-08-04 : Cory switches to full-time (Mon–Thu) until end of year
2021-08-05 to 2021-08-06: DEFCON
2021-08-04 to 2021-08-05: Time off: Kevin
2021-08-05 to 2021-08-08: DEFCON - Kushal
2021-08-06 : FPF Holiday (Summer Friday)
2021-08-09 to 2021-08-12: Time off: Ro
2021-08-09 : John's last day
2021-08-10 : Tails 4.21 release
2021-08-12 : SecureDrop 2.0.2 release (kernel update)
2021-08-13 : Time off: Erik
2021-08-14 : Debian Bullseye release (Buster EOL == one year later)
Opportunity to switch SDW to new kernel series
SOON? : Qubes 4.1 release
NB. cfm might need to trade around one working day weeks of August 9 and 16 (TBD).
After sprint period:
2021-08-17 to 2021-08-20: Kushal Packet Decoding training (participant) 4 hours daily
2021-08-20 : FPF Holiday (Summer Friday)
2021-08-24 : Jen's last day as a contractor
Late August : Time off: Ro
Learning time: Conor/Kushal have continued their Rust adventures
-
Release SecureDrop 2.0.2 with kernel update to >=5.4.136
-
Prepare kernel release for SecureDrop Workstation & begin QA for SecureDrop Client 0.5.0 release
-
Organize a knowledge share, including discussion of improvement opportunities. Dependency management (managing an ignore list for safety and other errors, maintaining upstream wheels, diff reviews, and how frequently we upgrade dependencies)