Team Sync - Apr 19, 2021

[choldgraf]

This is a @2i2c-org/tech-team sync 🎉🎉🎉! This is a way for 2i2c Team Members to triage work, point out issues that require attention, and make sure we are working well as a team. This issue will be closed at the end of the day.

Team Goals

See the Team Goal label for a list of team goals that we are currently working towards.

Issues Requiring attention

These issues require attention quickly:

New Hubs: The Needs Hub issues are new hubs that need deployments.

• Carbon Plan Hubs
• Justice Innovation Lab Hub

Needs Triage: The Needs Triage issues require an initial assessment and labeling.

• Properly installing some dependency packages
• Give admins/teachers more memory
• Embed dask dashboard into the Jupyterhub
• How should we autheticate with GitHub on the JupyterHub?

Priority Issues: The Priority Label issues are important and should be given attention over other issues.

No priority issues to tackle! 🎉

Team Updates

Please respond to this issue with your team update! That means anyone on the @2i2c-org/tech-team. You shouldn't feel forced to add content if you can't think of anything, use it as much as is useful.

Use the template below for your update.

Copy and paste these questions below, and answer them as you wish!

**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with XXX...
- Thanks for Jo's work on the XXX repo...

**Updates from last week ✔**
- I worked towards goal: <link-to-goal>
- I merged issues XYZ
- I had a meeting with ABC

**What I'm up to next ⬜**
- I'd like to focus on goal <link-to-goal>
- Developing on ABC feature
- Focusing on XXX hubs

**Links to items for discussion 💬**
- I'm have a question about goal <link-to-goal>
- Can @XXX give a comment on issue #NN ?
- I opened #NN for discussion, please chime in

[choldgraf]

Thanks I'd like to give 🙌

• Many thanks to @damianavila and @yuvipanda for talking through some team / project structure last week!

Updates from last week ✔

• We have a proposed project structure and workflow!
• Have also been playing around with a slightly more complex issue labeling system / issue structure to make it easier for us to identify important work to be done.

What I'm up to next ⬜

• I'm going to try updating our project boards / issues / etc to start implementing some of the project workflow structure that we've worked out (see link above)
• Onboarding @damianavila
• Thinking about how these team updates should be changed to adapt to our new structure
• Also need to do some docs work in Jupyter Book because I managed to break our builds 🙃

Links to items for discussion 💬

• Here are the major places to keep an eye on for the re-worked team workflow. They are still work-in-progress but should give an indication for the direction in which we're heading. (workflow overview here
  • Active Development board - contains Tasks that we are currently working on.
  • Dev projects backlog - contains major development issues that we are working on (think things that'll take several days of work). These are inspiration to generate the tasks on the Active Backlog
  • Org projects backlog - contains major organizational issues that we are working on. This is similar to the dev projects backlog, but a bit more "meta" and abstract so putting it in a different place to not clutter things.

[damianavila]

Thanks I'd like to give 🙌

• Thanks to @choldgraf for letting me brainstorm with him about team/project management

Updates from last week ✔

• I worked towards absorbing as much information as I can (mostly about jupyterbook and some Kube affinity stuff)
• I try to provide useful feedback on some PRs: 343 and 348 and some issues: 312 and 338
• I had several meeting with @choldgraf (sorry about that Chris 😉 )

What I'm up to next ⬜

• Getting a sense/intuition about the most important JB issues
• Try to execute the new proposed team workflow with a focus on improving the onboarding process
• Working on some paperwork and related stuff 😒 😉

Links to items for discussion 💬

• I think this is an interesting discussion on pods affinity, I would love to get more feedback if possible. Thanks!

[yuvipanda]

Thanks I'd like to give 🙌

• To @choldgraf for being a beacon of patience

Updates from last week ✔

• I worked on notebooksharing.space, and received a lot of feedback from users!

What I'm up to next ⬜

• I'd like to get better bearings on what would be useful things for me to do closer in-scope to 2i2c
• Cleanup architecture of pilot-hubs to make it easier to document (Improvements to developer onboarding documentation infrastructure#351)

[choldgraf]

@yuvipanda - let me know if you wanna have a brainstorm/chat about the pilot hubs documentation, I am happy to be a sounding board there

@damianavila - I am gonna try adapting whatever tag / issue structure work use at 2i2c for the executablebooks org as well (we may not be able to do some things the exact same, but can get close anyway). Hopefully this will make it easier for us to centralize information

[GeorgianaElena]

Thanks I'd like to give 🙌

• @damianavila for making time to have a quick chat and answering some of some of my vaccine-related curiosities through his biochemistry background :D

Updates from last week ✔

• I learned a bit about pilot-hubs costs and tried to reduce it by cordoning some of the nodes (also a new concept I learned :D)
• I worked towards improving the UX of the jupyterhub-configurator, learning about React along the way.
• I deployed the configurator to tljh (2 weeks ago, but failed to report it in the last week's sync)

What I'm up to next ⬜

• Update some of the last week's PRs based on feedback received
• Pick up again the migration to JupyterLab3 of the pilot-hubs and the UToronto one.