Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Team Sync - May 31, 2021 #111

Closed
choldgraf opened this issue May 31, 2021 · 6 comments
Closed

Team Sync - May 31, 2021 #111

choldgraf opened this issue May 31, 2021 · 6 comments

Comments

@choldgraf
Copy link
Member

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

High priority issues

These issues require attention quickly:

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
@yuvipanda
Copy link
Member

Thanks I'd like to give 🙌

Updates from last week ✔

What I'm up to next ⬜

My availability for next week

  • I'll probably spend a couple days doing Berkeley stuff this week - perhaps Tuesday / Wednesday

@damianavila
Copy link
Contributor

Thanks I'd like to give 🙌

  • Thanks @yuvipanda for the continued input of things to digest 😜
  • Thanks @choldgraf for requesting my input/feedback on multiple topics

Updates from last week ✔

  • I worked towards reproducing the current AWS deployment for Farallon (learning jsonnet along the way 😉)
  • A lot of PR reviews and feedback on EBP and pilot-hubs stuff
  • Experimenting with myst support for static site generators (Nikola): Implement a MyST parser for Nikola upstream#14

What I'm up to next ⬜

  • I'd like to focus on finishing Farallon and at least have some AWS preliminary documentation (this will be an ongoing target but it would be nice to have something consumable besides the comments on issues or the very same multiple PRs)
  • Learn about recent stuff happening on the markdown-it-myst which is relevant for the parity between myst parsers.

My availability for next week

  • Available the whole week.

Links to items for discussion 💬

@consideRatio
Copy link
Contributor

consideRatio commented May 31, 2021 •
edited
Loading

Thanks I'd like to give 🙌

  • @andersy005 and @fperez for helping establishing a clear direction to head with the jupytearth.org deployment. From magic_castle to 2i2c flavored z2jh + dask-gateway.
  • @yuvipanda for caring effort to onboarding me technically into 2i2c-org/pilot-hubs and helping me along the way towards hub.jupytearth.org
  • @sgibson91 for hosting the JupyterHub team meeting and persisting notes
  • @manics for all work in z2jh

Updates from last week ✔

  • I've released JupyterHub Helm chart 1.0.0-beta.1
  • I've worked to deploy hub.jupytearth.org with 2i2c-org/pilot-hubs as a foundation

What I'm up to next ⬜

  • hub.jupytearth.org deployment refinements
  • jupytearth website content

My availability for next week

  • 100%

@GeorgianaElena
Copy link
Member

Thanks I'd like to give 🙌

Updates from last week ✔

  • Reviewed some pilot-hubs PRs
  • Switched the pilot-hubs from GenericOAuthenticator to Auth0OAuthenticator

What I'm up to next ⬜

  • Pushing forward the switch of pilot-hubs to JupyterLab v3
  • I would like to resume the work on z2jh release pulses
  • I would be super happy if this week I managed to continue some of the work I started a looooong time ago in tljh

My availability for next week

  • 100%

@github-actions github-actions bot closed this as completed Jun 1, 2021
@choldgraf
Copy link
Member Author

Hey all - sorry for the slow response, yesterday was a holiday in the states :-)

A few quick updates from me:

Thanks I'd like to give 🙌

  • Many thanks to you all for kicking so much butt. Looking at all the above updates makes me happy and excited about all the great work we are doing :-)

Updates from last week ✔

  • I spent a lot of time in conversations with ICSI as well as doing some investigations of other fiscal sponsors in order to follow up on https://github.com/2i2c-org/meta/issues/184 and https://github.com/2i2c-org/meta/issues/155 - I promise that this is a lot of work and I am not just slacking off :-)
  • I also helped the executable books team work through some more issues that surfaced as we were preparing to make a new release.

What I'm up to next ⬜

  • Continuing to follow up on discussions with ICSI / other fiscal sponsors
  • Preparing like 4 talks that I'm giving next week (seriously, when it rains it pours)

My availability for next week

  • I'm around the rest of this week!

@damianavila
Copy link
Contributor

I promise that this is a lot of work and I am not just slacking off :-)

I super appreciate the time you are investing in this topic, @choldgraf!
It is actually key work to be done to establish a long-term sustainability path for 2i2c as a project/idea/actor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@yuvipanda @damianavila @choldgraf @consideRatio @GeorgianaElena