Sprint plan 3 for goal Image Management, Q3 2023

[damianavila]

Where are we now in relation to our goal?

We were able to deploy interventions to facilitate the usage of custom images in selected communities but the results of interventions usage surfaced bugs located in upstream projects.

What is the biggest uncertainty or obstacle to reaching our goal?

The bigger obstacle is being able to see the results of our interventions in the very same sprint.
Additionally, we are usually overambitious about the things we plan to do.

What should we do in the next sprint to learn and make progress?

Make sure the intervention we did actually works (fix upstream issues) and deploy it to start getting feedback.
Measurement of usage of custom images (Grafana graph to measure it already exists).
Create an actual flowchart to use existing and/or build your own image.
Carryovers from the previous sprints.

What do we expect to happen (hypothesis)?

---

Sprint plan for this sprint

Tasks

Preview Give feedback

1. API Calls to spawn user servers do not handle defaults in profileList correctly jupyterhub/kubespawner#758
   bug +1
2. [leap hub-experimental image]: Investigate kubespawner unlisted_choice cannot be changed a second time #2887
   +0
   
3. Revert temp fix for leap health check #2869
   +0
   
4. Measure use of unlisted_choice in LEAP hub to see if anyone is actually using it. #2875
   +0
   
5. Deploy unlisted_choice to researchdelight hub, so it acts as a demo #2873
   +0
   
6. Update the imagebuilding-demo hub use a hub-experimental image with the prototype kubespawner UI #2884
   +0
   
7. [Docs] Create documentation on how to choose a tag for pangeo-docker images #2793
   4 of 4
   +0
   
8. Create an actual flowchart to use existing and/or build your own image #2963
   +0
   

---

What actually happened, and what did we learn? Did we confirm our hypothesis?

[damianavila]

@consideRatio, can you do a first push on jupyterhub/kubespawner#758 before your away time?
Then, I will ask @GeorgianaElena and @yuvipanda to follow up with this one next week.

[damianavila]

#2887, #2869 and #2875 depends on the upstream fix referenced above, so I am not yet assigning some of issues until we have more clarity on the upstream resolution.

[damianavila]

@jmunroe, I think you opened some new issues some hours ago (I have not read them yet) that might capture better little improvements we might want to do on the community side. If you think we should add some of them to the sprint, let me know and we can discuss it. I want to make sure we are not at overcapacity so open to removing something from the actual plan if we needed to move forward with other pieces.