Sprint Planning Meeting: Wednesday, July 20th

[github-actions[bot]]

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]

Done

Deployment plan as comments

• we now have this yay 🎉

Static websites

• 🎉
• @yuvipanda believes useful to get into its own chart and upstream to jupyterhub itself

Waiting

Scipy update

• it went great 🎉
• @yuvipanda wants to find the slide and/or video of the presentation then close the issue

Assigned

chown /shared dirs?

• do we need to chown /shared in order for it to work? why does it work only sometimes without it?

dependabot usage

• please provide feedback about pinning dep in requirements.txt

role changes pings

• they work 🎉

Dynamic image building in a JupyterHub

• @consideRatio, @yuvipanda and @sgibson91 to be part of the team that will help shape this project

Allow access to multiple s3 buckets from the hub

• @damianavila to ping @yuvipanda to add remaining docs

Upgrade our hubs to Z2JH / JupyterHub 2.0

• will close once we update

[New Hub] COESSING Pangeo-Style Hub

• @GeorgianaElena to give feedback on the PR
• but its pretty much done
• needs new gh app for the push to work

Onboard James

• we should probably close it, but we should double check if there's anything else we could give access to
• @choldgraf believes that we should open a separate issue to "announce" James is joining the team 🎉

Switch to Google Workspaces standard plan

• 🎉

Community archetypes for documentation and engagement

• group hubs together based on the different communities 2i2c is serving
• really useful, please provide feedback if interested

Must

Automatically run script to clone a git repo on user server startup

• @2i2c-org/tech-team, lets find a resolution together today 🚀

[New Hub] Alabama Water Institute CIROH hub

• need to gather more info but we are on the right track with it

[New Hub] OceanHackWeek 2022

• there is enough info about this and we can start working on it

[New Hub] Callysto

• @yuvipanda agreed to try and push this discussion further

[damianavila]

Thanks for taking these notes, @GeorgianaElena!!