Sprint Planning Meeting: Wednesday, May 25th

[github-actions]

2i2c Sprint Planning meeting

This is a 60 minute recurring meeting every other Wednesday at 7:30AM Pacific time (here's a timezone converter, ignore the date!).

Our goal is to synchronize the team on the most important things to work on, and to divide work between one another so we know what to work on next.

• Team backlog
  • list of items with people assigned to them
  • list of items without any people assigned
• Meeting facilitator:

Meeting agenda

Review operations and support items (20 min)

For each operations or support item, we should:

• Assign a team member to items that don't yet have one
• Discuss any quick blockers or major questions that need to be answered
• Discuss the next steps to resolve this item

Review team projects. (30 min)

For each project, its champion does the following:

• Share accomplishments since the last sprint, demos, etc
• Discuss any quick blockers or major questions to answer
• Discuss the work plan for the next sprint for this project

Context share from admin and sustainability (5 min, if time)

A representative that has been working on these parts of 2i2c shares any significant updates or upcoming items.

[GeorgianaElena]

Meeting notes

Operations and support

1. Docs to help debug issues

• In progress
• Todo: discuss how to treat long ongoing issues in the team backlog

2. LEap metrics

• in progress
• needs the dashboards to be created and iterate to improve them

3. Move openscapes to github teams

• still needs work, we will keep it here for another cycle

4. Dask workers limit

• there was a meeting betweeen Yuvi and Ryan

• we don't have details about that yet

• todo: @damianavila agreed to ping again to get more info

  @choldgraf suggested using a stale label to close issues when they become inactive
  @damianavila wants to add a status in the board to flag this, but it's worried that are too many already

5. dask workers didn't respect no of cores

• done, yay! 🎉

6. Support chart

• in progress
• @GeorgianaElena needs to remeber to check when there aren't any users on the meom-ige cluster in order to run the manual steps

7. GPU support and university of washington hub

• deployed for the hackweeks cluster
• yuvi waiting for feedback

8. leap login failures

• solved?
• @damianavila agreed to check before closing it

[GeorgianaElena]

Eng projects

Monitoring

• in progress

Release plan on pydata team

• action points: close it as resolved on our end
• small things might still need to happen

BinderHub for Pangeo

• deploy the infra

  • do it in a GCP account that we manage, otherwise some people might not have access to it

• yuvi did a pass through the values files and marked the things that needed to be in the binderhub chart

• problem: if/else doesn't work in helm value files only in templates

• next step -> use jsonnet

• improving actions to tupdate hub and helm images

• Erik emphasized the complexity of the project

• binderhub might cease to exist when/if it becomes a z2jh deployment

• where to look for info about this project and its project ->

  • project board
  • discussions happen in the sub-issues there

• we might need to phrase a proposal for the broader juypyterhub community

• many people still seem to prefer having a separate binderhub chart

Oauthenticator release

Profile list on the pangeo hub

• lots of progress here from Yuvi already

Role change events

• wait to see if the bot correctly triggers next cycle then we'll release this
• todo: @sgibson91 agreed to write a bot to update the calendar with the roles changes

Help communities manage their image

• @damianavila wants to invest some time in the upcoming cycle

[GeorgianaElena]

Ops and Support Unassigned

New hub for Jack Eddy Symposium

• due on June 1st (but wanted asap)
• ok to deploy on gcp
• @yuvipanda agreed to be the primary assignee
• @damianavila will assign somebody else too to help Yuvi

Org projects

1. @tech-team please provide feedback tot the support PR Add incident commander role + more steps to support process #422

Admin projects

utoronto meeting details

• maybe split the hub into multiple hubs because it because pretty complex already
• follow up with them about support once we have more details about our current proccess
• @colliand agreed to work with them on improving the contract we currently have to better reflect our relationship

[damianavila]

Thanks for taking all these notes, @GeorgianaElena!
Closing here now!