Sprint Planning Meeting: Wednesday, July 6th

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

[choldgraf]

Engineering project updates

• BinderHubs are pretty much ready to go, @yuvipanda would like to get a demo working before SciPy
• @GeorgianaElena set up GitHub authentication for the Grafana dashboards so any member of @2i2c-org/2i2c-team will have access to our grafana! This means that @jmunroe automatically has access without needing to manually add.
• We decommissioned a bunch of hubs!
• Our cert-manager helm chart is upgrade which will make our infrastructure more stable
• Plan to close Cloud usage monitoring and alerting infrastructure and process infrastructure#328 once the last PR is merged in there
  • Then track progress on the alerting side
• Updating to JupyterHub 2.0
  • Were waiting on the Grenoble image to be updated but this is now unblocked

Organization

• We have a new support process and incident commander process: https://team-compass.2i2c.org/en/latest/projects/managed-hubs/incidents.html
• We have a new link-checking workflow that will auto-check our links each day and open an issue with anything that is broken
• We're planning to hire an engineering person

Issues we must follow up on

• [New Hub] PaleoCube and PaleoHack hubs infrastructure#1418 : in good shape
• [EVENT] NeuroHackademy 2022 infrastructure#1300 : should be ready to go quite soon
  • As part of this, @yuvipanda is working on making it possible for hubs to provide authenticated web services (such as docs that you can only access after auth)
  • @damianavila will find folks that can help with deploying the hub
• Two remaining hubs should start around July 15th but the actual events they'll serve come a bit later
  - [New Hub] Alabama Water Institute CIROH hub infrastructure#1444
  - [New Hub] Allen Institute Summer Workshop on the Dynamic Brain infrastructure#1440

Project shaping

• We'd like to push forward conversations around dynamic image building, @damianavila will start wrangling people soon: GESIS Collaboration - Dynamic image building in a JupyterHub infrastructure#1382
• Understand the difference between our "Product and Community Lead" role and a "Community Manager" #446 : @jmunroe and @choldgraf will be brainstorming this in the coming weeks, but nothing specific to work on now. @choldgraf will meet with some folks at the Turing and report back some ideas as well.
• [blog] Quarter 2 update #452 : Please share any updates about the blog post!

[damianavila]

Thanks for taking these notes, @choldgraf!!
Super useful content 👍.