Team Sync - Mar 29, 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.

• Document the process of onboarding a new customer
• Create team documentation and training for "best practices in managing services for other communities"

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

[GeorgianaElena]

Thanks I'd like to give 🙌

• Thanks for Yuvi's work on deploying and documenting the Configurator

Updates from last week ✔

• I worked towards the goal of having a z2jh release cadence by creating a release pulse issue template (still a work in progress)
• I moved the tljh tests from CircleCI to GitHub actions

What I'm up to next ⬜

• I'd like to try and deploy the Configurator to TLJH
• Split the pilot-hubs deployment job into one action per cluster

Links to items for discussion 💬

• I would love feedback on:
  • TLJH CI switch:
    • Switch integration and upgrade tests from CircleCI to GitHub actions jupyterhub/the-littlest-jupyterhub#673
    • Switch unit tests from CircleCI to GitHub actions jupyterhub/the-littlest-jupyterhub#672
  • pilot-hubs default staff admins:
    • Add 2i2c staff as admins to all hubs infrastructure#311
  • pilot-hubs admin's shared directory naming:
    • [WIP] Allow admins to rename user home directories infrastructure#300

[choldgraf]

Thanks I'd like to give 🙌

• Thanks to @GeorgianaElena and @consideRatio for taking the time to catch up with me last week, it had been a while since we chatted 🌞

Updates from last week ✔

• It looks like we'll have two proposals from the JupyterHub community for this round of EOSS. Maybe also one for Jupyter Book, but unclear whether that'll go through.
• I also worked with @yuvipanda to re-work some of the 2i2c website to better-reflect the work we do, I would love feedback from the team.

What I'm up to next ⬜

• This week I am focusing a bit on strategy and strategic frameworks for 2i2c - I feel like we can do a better job of defining our overall projects, and sharpening those projects into goals and tasks.
• I'm also playing around with project management platforms to see if there is a better system than just having a bunch of GitHub issues 🙃
• I'm gonna keep re-thinking our documentation (and the Jupyter docs) with the Divio documentation in mind. Would love to hear ideas from others if you have them!

Links to items for discussion 💬

• Provide your feedback on the website re-work! Rearranging site to use Managed JupyterHubs and Projects 2i2c-org.github.io#53
• Provide your comments (quickly! it's due tomorrow!) in the JupyterHub EOSS issue: Two applications for CZI EOSS round 4 jupyterhub/team-compass#380

[consideRatio]

Thanks I'd like to give 🙌

• @choldgraf for setting aside time for a chat ❤️
• The amazing people that made a "Learning pathway" section in the README.md of jupyterlab/rtc!

Updates from last week ✔

• I spent time recuperating from some stressors and didn't do much work

What I'm up to next ⬜

• As part of JMTE work I'll be learning about jupyterlab/rtc to hopefully realize how JupyterHub itself or JupyterHub distributions can facilitate use of Real Time Collaboration.
• As part of JMTE work I'll be learning about a HPC infrastructure simulation on a cloud, using https://github.com/ComputeCanada/magic_castle.

[yuvipanda]

Thanks I'd like to give 🙌

• @choldgraf for thinking together about strategy and process
• To @zaneselvans for amazing feedback about the JupyterHub configurator!

Updates from last week ✔

• I deployed the JupyterHub configurator tentatively to all hubs.
• Worked on improving 2i2c website
• Some progress on getting TLJH to work on ARM processors

What I'm up to next ⬜

• Improve JupyterHub configurator based on @zaneselvans' feedback
• Work on strategy & team practices planning with @choldgraf
• Figure out an environment story for JIL Properly installing some dependency packages docs#66

Links to items for discussion 💬

• Read the docs on setting up a local JupyterHub configurator and provide feedback?