jmunroe
commented
2 years ago Attendance: @GeorgianaElena @jmunroe @damianavila @sgibson91
Review of PRs merged and issues closed on Sprint Board and thanks for progress in the last cycle both on operations and projects.
1684 is blocked but we will cover that later
Any "Waiting" status can be updated if need. Let @damianavila know.
Operational waiting issues:
1440 - New hub request Allen Institute. Before shutting down this hub, there is an outstanding issue that needs to be handled. @damianavila will have a meeting with @yuvipanda today. Please respond with any additional information.
1666 - CarbonPlan AWS. Being resolved -- see ticket for additional context
1693 - Discussion is ongoing with UToronto
Project waiting issues:
440 - JupyterHub Commmunity Strategic Lead. JupyterHub have come up with three Outreachy projects. Next step is the contribution phase -- applicants have one month to make a contribution to be a project. We need to identify some appropriate issues. Once contributor have made a contribution, that will allow them to make a application to be an intern. (This is a significant project of @sgibson91 50% time on upyterHub)
450 - @GeorgianaElena has opened a PR that moves this forward. Feedback will be requested from specific people. @damianavila will be following up.
84 - AGU Fall @jmunroe is moving forward trying to get time on a shared table or booth. AGU seems less likely. Maybe NASA? The more important deliverable will be formally exhibiting at AGU Fall 2023.
In Progress issues:
919 - update from @sgibson91 on conversation with @rabernat two weeks ago. We are working to get a new AWS account to deploy a BinderHub (without DaskGateway) and get this linked with the other MyBinder deployments
1382 - Meeting to be scheduled by @damianavila for next week . Armin Bleier has been a key person behind persistent binderhub.
374 - PagerDuty account created but we need see if we can get a non-profit discount.
(For Community-Partnership related issues, @jmunroe and @damianavila need to meet to trying to hide them from this Engineering cycle meeting)
Shaping Issues:
1705 - We need to work on to "right to replicate" our workflow to a laptop.
389 - @jmunroe and @damianavila have had a Product and Engineering meeting on this. All are welcome contribute to this decision.
Must issues (operational pipelines)
1546 - Project VICTOR. Active conservation ongoing between community partner and @jmunroe
1650 - gridSST Hack-A-Thon. We are waiting on confirmation of the dates.
1702 - NASA cryocloud - needs engineering resources assigned soon (pending confirming that all information has been collected)
1440 - Allen Institute - needs to be decommision but that is waiting on a PR to be merged.
Documentation issues
There are many open engineering documentation issues that need be pursued. Currently 12 open documentation issues need to be move forward. If anyone has spare capacity, it is important to move those forward.
High impact PRs to look at and awaiting feedback
- Splitting new hub issues into multiple issues (#1733)
- Finalizing allen-swdb hub (#1585)
- Replace GitHub with PagerDuty (#508)
damianavila
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.
Meeting agenda
Review operations and support items (20 min)
For each operations or support item, we should:
Review team projects. (30 min)
For each project, its champion does the following:
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.