Team Sync - May 03, 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 worfklow boards

• Activity Backlog
• Development Backlog
• Organizational Backlog

High priority issues

These issues require attention quickly:

• New Hub: OpenScapes
• Create team documentation and training for "best practices in managing services for other communities"
• Create AWS deployment infrastructure
• Improvements to the 2i2c Onboarding Documentation
• Submit an application for the CZI EOSS grant around the "Community Developer" role

Team update template

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.

Copy and paste the template below, and answer questions as you wish!

Response Template

**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 deliverable: <link-to-deliverable>
- I had a meeting with ABC

**What I'm up to next ⬜**
- I'd like to focus on deliverable <link-to-deliverable>
- I'm answering user questions this week

**My availability for next week**
- I'll be off on XXX day...
- I've got several meetings this week...

**Links to items for discussion 💬**
- Can @XXX give a comment on issue #NN ?
- I opened #NN for discussion, please chime in

[damianavila]

Thanks I'd like to give 🙌

• @yuvipanda for providing feedback on the tickets I request information about

Updates from last week ✔

• Provided feedback on several issues and PRs
• Research into a nbgitpuller issue affecting Ryan
• Keep understanding the details around the pilot-hubs repo
• Looked into the pangeo-hubs repo to understand what's happening there

What I'm up to next ⬜

• Focus on Create AWS deployment infrastructure

My availability for next week

• Usual availability
• Btw, I have adopted a split working schedule (working morning + break + working late afternoon/evening) to maximize my overlapping with India + Europe on one side and West Coast on the other side.

Links to items for discussion 💬

• If you have thoughts about how our AWS deployment should look like, please chime in on the Create AWS deployment infrastructure ticket!

[choldgraf]

Thanks I'd like to give 🙌

• Thanks @damianavila for working on the AWS hub setup! I think that's an important step to us being able to serve the Pangeo community + many others!

Updates from last week ✔

• Helping @damianavila and @yuvipanda think through our AWS deployments along w/ our first customer
• Working on some more team process documentation and planning
• Re-working the strategic plan for 2i2c a bit

What I'm up to next ⬜

• Organizational things
  • Fleshing out the strategic planning framework for 2i2c: https://github.com/2i2c-org/meta/issues/166
  • Putting together a first draft of a CZI EOSS application for JupyterHub: Submit an application for the CZI EOSS grant around the "Community Developer" role upstream#8
  • Helping edit a draft of a "Neuroscience + cloud" paper for some collaborators
• Dev things
  • Unblocking @damianavila and @yuvipanda as much as I can for getting the AWS infrastructure set up and a first hub for OpenScapes
  • Helping the executablebooks team push through the "External TOC" refactor.

My availability for next week

• I'm around for all of this week, though bouncing back and forth between "high level" things and "dev things" as you can see above :-)

[yuvipanda]

Thanks I'd like to give 🙌

• To @damianavila for code review and work on the AWS setup
• To @choldgraf for support and providing structure

What I'm up to next ⬜

• I mostly plan on working on documentation - Document our org-ops/ repository #87 Document our Terraform setup infrastructure#275 and similar
• Support @damianavila in AWS deployment
• Get vaccinated, hopefully?

My availability for next week

• Theoretically I'll get first shot of the vaccine on Tuesday - although I'll only believe it once I've had it. I think this will affect availability on Tuesday
• I'll probably spend Thursday on Berkeley stuff, and should be otherwise available

[choldgraf]

@damianavila I would be curious to hear more about your split schedule and how it goes, I'm also trying to find ways to overlap more with others (though have some constraints in the form of an 8 month old :-) )

[damianavila]

@damianavila I would be curious to hear more about your split schedule and how it goes

Ask me again in two weeks 😜 , so I have several data points (days) to come up with a general (useful) feeling.
It should work better, IMHO, but let's see the evidence first!

[consideRatio]

Thanks I'd like to give 🙌

• I'm thankful for @cmd-ntrf who has documented magic_castle thoroughly and clearly valued doing so for the projects new users! ❤️
• I'm thankful for @romainx and @mathbunnyru who have put in a lot of heart and soul into maintenance of jupyter/docker-stacks! ❤️
• I'm thankful for @manics who put in significant effort to make arm64 compatible images possible in projects across the JupyterHub org (z2jh, chp, jupyterhub)! ❤️

Updates from last week ✔

• I deployed https://github.com/ComputeCanada/magic_castle to AWS and made it available at mc.jupytearth.org. This involved learning more about that tech stack (Slurm? FreeIPA? Mokey?) and I still have more to learn. The deployment code base is available at consideratio/jupytearth.org-deploy.
• I spent some time in jupyter/docker-stacks to see if we can get the final z2jh image (jupyterhub/k8s-singleuser-sample) that depends on the jupyter/base-notebook image to become 100% arm64 compatible.

What I'm up to next ⬜

• magic_castle tech stack and associated workflow exploration
• z2jh release?

My availability for next week

• Full availability!

Links to items for discussion 💬

• jupyter/docker-stacks enhancement proposal regarding how to support multiple architectures in a somewhat more maintenance sustainable way: Support ARM architecture (multi-arch images) jupyter/docker-stacks#1019 (comment)

[choldgraf]

the magic castle stuff looks cool!