Yellow Squad Weekly Project Report: July 20

Summary:

• This was gmb's last week with us. Farewell from Yellow squad, and best wishes for leading Green squad!
• We're still hiring for five openings in a very cool Python & cloud position, so please apply soon! The interview process largely consumed 3/5 of the squad; next week it will affect 3/4 of us. We've had some good interviewees, and we hope to have more.
• We did not have as many test runs this week because of the interviews. Our successful test run from last week stopped this week after 42 consecutive passing runs, after which we had instances of 974617/1011847 and 1014916.
• The parallel testing machines in the data center are reportedly ready for configuration and we are now waiting for IS to get to the task.
• We tested a new package of the lpsetup code, fixed some problems, and have a working package for both the developer use case and the testing use case. The next step is to design the interactive story.
• The lpsetup code has a second integration test, this time for the LXC approach.

[introduction] [project report] [tricks] (no topics this week)

Weekly Goal Progress

gmb, benji, and gary_poster had very limited availability this week because of transition and interview tasks. We should have accommodated this in our goals.

• Continue running parallel tests on the EC2 32 core machine and aggregating results.
  Missed three days because of interview focus. Our successful test run from last week stopped this week after 42 consecutive passing runs, after which we had instances of 974617/1011847 and 1014916.
• Add diagnostics for trying to solve 974617/1011847.
  NOT DONE.
• Make a new deb release of lpsetup.
  DONE.
• Successfully incorporate the release into our automatic test structure.
  NOT DONE.
• Land integration tests for the LXC lpsetup story.
  DONE.
• Provide a reasonable first cut of a "developer friendly" lpsetup story.
  NOT DONE.
• Give IS complete, tested instructions on how to set up a test machine in the data center.
  NOT DONE. IS is not ready to consume them.
• Get confirmation from IS about the approach to configuring the two new machines.
  NOT DONE.

Action Items

• ACTION due August 17: squad will evaluate the personal feedback loop experiment.
  NOT DUE. Experiment started. This week and the following two to four weeks will be unusual for the squad because of hiring and other unavailability, but we will continue to practice doing this. We may extend the experiment.
• ACTION: gary_poster will add checklists for starting a kanban card and creating a kanban card.
  NOT DONE.
• ACTION: gary_poster will add "high" markers to cards that represent the weekly goals. We should do that after each weekly retrospective call.
  DONE. It helped us focus: all of the project cards done were goal-related. We didn't complete all the weekly goals in part because we were too ambitious given the interview focus.
  

Other Status

None.

Goals for Next Week

gmb has now officially left the squad. bac, benji and gary_poster already have between 12 and 18 hours of interviewing scheduled for next week with more possible, so frankban will primarily be the one working furiously to try and keep lpsetup development moving.

• Continue running parallel tests on the EC2 32 core machine and aggregating results.
• Add diagnostics for trying to solve 974617/1011847.
• Successfully incorporate the release into our automatic test structure.
• Agree on an initial plan for a "developer friendly" lpsetup story.
• Give IS complete, tested instructions on how to set up a test machine in the data center.
• Get confirmation from IS about the approach to configuring the two new machines.

Thanks for reading the project report!  See the links at top of the post for reports on other parts of our Friday meeting.