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

• 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

[yuvipanda]

Thanks I'd like to give 🙌

• To @choldgraf for review on docs PRs (Document aspirational documentation structure infrastructure#293, Re-organize documentation to match new structure docs#55)

Updates from last week ✔

• I worked on two big docs PRs: Document aspirational documentation structure infrastructure#293, Re-organize documentation to match new structure docs#55
• I kinda worked towards goal Documentation Sprint: March 1-5, 2021 infrastructure#274, with mixed result
• I discussed our environment customization needs with @choldgraf and @colliand
• I discussed ways to price hubs and what they cost us with @choldgraf and @colliand
• I wrote some rough documentation on our NFS / mounting setup: [WIP] Allow admins to rename user home directories infrastructure#300 (comment)

What I'm up to next ⬜

• Focus on goal to document our story around environments
• Get Re-organize documentation to match new structure docs#55 merged
• Respond @colliand's https://github.com/2i2c-org/meta/issues/162 about a 'base' hub
• Think of the cheapest hub we could possibly run for people from an infrastructure perspective

Links to items for discussion 💬

• Please share thoughts on short-time bound goals: Documentation Sprint: March 1-5, 2021 infrastructure#274
• Push on having a z2jh upgrade process - perhaps thoughts from @consideRatio on what we can do to help the release process? And who else to involve in the community

[consideRatio]

Updates from last week ✔

• I took some time out to recover from feeling a bit stressed out generally
• I tried to ensure manics/minrk/kafonek wasn't blocked in PRs of relevance to release jupyter-server-proxy/dockerspawner/kubespawner through review efforts

What I'm up to next ⬜

• address a 3 year old z2jh security issue in the guide for AWS EKS setup https://github.com/orgs/jupyterhub/teams/jupyterhubteam/discussions/8
• overview work for the next z2jh release
• try come up with a concrete suggestion for release process of kubespawner/oauthenticator/chp and other dependency projects to z2jh, and perhaps also tljh, or even jupyterhub itself, or just ignore those and have a process for z2jh not aligning at all with dependency projects... Hmmm

[GeorgianaElena]

Thanks I'd like to give 🙌

• To @choldgraf for coordinating and writing about the last year's CZI EOSS grant
• To @yuvipanda for explaining me how the pilot-hubs storage works [WIP] Allow admins to rename user home directories infrastructure#300 (comment)

Updates from last week ✔

• Worked on the CIR blog post
• I worked towards goal Have a robust set of authentication methods that can serve different users infrastructure#276 and Documentation Sprint: March 1-5, 2021 infrastructure#274

What I'm up to next ⬜

• I'd like to focus on goal https://github.com/2i2c-org/pilot-hubs/issues/261
• Add more docs

[choldgraf]

Omg it actually worked! Bless you github actions 😅

[choldgraf]

Thanks I'd like to give 🙌

• Thanks to @GeorgianaElena for writing that great EOSS / CIR blog post with me!
• Thanks to @damianavila for volunteering some of his time to provide feedback on the team-sync updates PR

**Updates from last week ✔ **

• Trying to kick-start a new Contributor in Residence / EOSS push: Two applications for CZI EOSS round 4 jupyterhub/team-compass#380
• Re-wrote the infra/process for this team sync issue! :-)
• Doing some more work to "formalize" the governance and structure of 2i2c so everyone is on the same page! Adding information about structure and governance. #38
• I also played around with Monday.com to help us manage our "leads/sales" pipeline and think it might be useful! ICSI is playing around with getting a site license.

What I'm up to next ⬜

• I'm going to focus on helping @yuvipanda improve the pilot documentation
• Try and make progress on some community discussions about JupyterHub infra: Coordinate use-cases / infra around JupyterHubs+other applications on Kubernetes jupyterhub/team-compass#382
• Doing something similar for some ExecutableBooks shared theme infrastructure: Discuss shared theme infrastructure between EBP and other themes executablebooks/meta#279

Links to items for discussion 💬
I would love people to think about (and discuss if you wish) whether this weekly process for a team sync is an improvement on our old 2-week process!

[damianavila]

Thanks to @damianavila for volunteering some of his time to provide feedback on the team-sync updates PR

It was a pleasure to contribute even with just a little bit!
Btw, a LOT of interesting things you are all discussing/working on here... 😉
Exciting!!

[consideRatio]

Great to have you with us @damianavila!!! ❤️ 🎉 👍 🌻 💯

Also hurray for the github workflow that made this PR issue automatically close =)