Sprint Planning Meeting: Wednesday, April 13th

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

[damianavila]

• Adding a point for the last minutes of the meeting to briefly talk about the changes outlined in Remove sprint concept and center the coordination in the backlog #408

[consideRatio]

Meeting notes

These notes are organized based on the structureu in our team backlog, see https://github.com/orgs/2i2c-org/projects/22/views/9.

Engineering - Operations and support

I've failed to capture notes that made sense about quick brief status updates on operations/support issues.

Engineering - Projects

Sarah/Erik on CI/CD: has worked on the CI system in 2i2c-org/ifnrastructure. Parallel deployments of prod hubs, following staging deployment. We have opted to retry various health checks etc and decouple them from deployments. Some items remain such as not stopping the deployment of prod hubs when a single cluster staging hub has failed in some cluster.

Chris on Cloud invoicing costs: manual lookup of cloud billing is currently used, the long term action option is to automate inspection of cloud billing. Jim is the person that works on invoices that may get feedback of what kind of information will be relevant to pass to customers.

Damián about pydata docs: a lot of work has been done and also cleanup of misc PRs.

Georgiana about CILogon instead of Auth0: worked to provide a fix of a security issue discovered by Yuvi. ANU hub is using the CILogon authenticator, Work to replace Auth0 is ongoing.

Georgiana about cloud usage monitoring and alerting: not started but with input from Yuvi

Yuvi on debugging "config connector": if we want misc extra utilities such as a s3 bucket, we have done it with config connector in the past, but now we have terraform to get it done.

Yuvi on GitHub team membership -> auth_state: Yuvi hopes to get it done in ~2 weeks

Damian/Chris about Pydata theme release: very happy about progress, restructure layout to be more compatible with current standards of the ecosystem. Making a release right away is considered, but otherwise its a small part remaining only.

Damian about document object storage and scratch bucket: Ryan is writing this documentation and getting feedback from Yuvi. Review help appreciated! 2i2c-org/docs#138

Unassigned

• Sarah to work on BinderHub deployment.
• "Define a process for helping communities with image changes" is highlighted as high priority to resolve.

Meta

• Damián notes that that if someone is to work on something and someone is happy to contribute as a helper in some way, that is encouraged! Being two to iterate on something is often helpful.
• Damián has made updates to the team backlog board
• Damián describes that a sprint board (perhaps to be named cycle board) will allow Damián to overview what is ongoing right now. Damián clarifies that we have done a bunch of things by highlighting smaller issues behind the bigger ones that we otherwise typically overview.

Organization - Projects

• Chris reports progress towards hiring a Product and Community Lead
• Jim has provided a document about a sustainability team role and look for additional feedback.
• Chris describes the need to prototype a monthly invoicing process, Jim contributes with this and iterating with CS&S

[damianavila]

Lovely notes @consideRatio! Super appreciated.
Closing now!