Sprint Planning Meeting: Wednesday, March 30th

[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]

Operations and support items updates from planning meetings:

Leap hub

Next action: Finish up/merge the scratch bucket PR, but the hub is up and running

TF + keras utoronto:

openssl version mismatch in RStudio. We cannot fix this at the moment without an ugly hack.

Next action: Let utotonto folks know about this in freshdesk (@damianavila agreed to follow up on this)

Pangeo access for 2i2c engineers

Next action: Needs @consideRatio input/confirmation about the columbia id

Update k8s version for toronto and carbonplan

Next action: Waiting for a response from utoronto about the best time to perform the update. @choldgraf will ping them again today.

Community representative from utoronto

Next action: @colliand and @choldgraf agreed to follow-up about this again with utortonto folks

Toronto credentials

Next action: @yuvipanda will follow-up with utoronto again because they also need to provide utoronto ids and they already agreed to this.

[GeorgianaElena]

Team Projects meeting updates:

CI/CD infra

Helm update logic in place waiting for review
Next action

• Setup CI/CD to actually use the new helm upgrade logic

Cloud costs

Did some research about costs of different type of hubs, but needs more work.
Next action
@yuvipanda wants to invest more time in this during next sprint. @choldgraf will provide a more complete update on this in the original issue

Pydata

Next action
@damianavila will update and possibly close the issue. Needs a big PR merged and cut a new release after this first iteration.

CILogon

Next action
@choldgraf agreed to update the initial issue about the scope of this issue and open up another issue tracking the auth0 replacement.

Config connector

Next action
Review + merge 🚀

[GeorgianaElena]

Team Projects meeting discussions - Issues with no assignees:

1. Cloud usage monitoring -> there is consensus to prioritize this

2. Binderhub for Pangeo

• @sgibson91 would like to tackle this after she has bandwidth (sometime after CI/CD and conference)

3. User image customization -> should be prioritized and discussed

• needs feedback from @2i2c-org/tech-team in (insert link here when you find it)

4. Profile list options based on GitHub membership

• needs upstream work in oauthenticator

[damianavila]

Lovely notes, @GeorgianaElena. Thanks for taking them!!