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.

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

Team Sync - Apr 26, 2021 #75

Closed
choldgraf opened this issue Apr 26, 2021 · 4 comments
Closed

Team Sync - Apr 26, 2021 #75

choldgraf opened this issue Apr 26, 2021 · 4 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 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.

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

No issues need triage! 🎉

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

yuvipanda commented Apr 26, 2021

Thanks I'd like to give 🙌

  • Thanks a lot to @choldgraf for helping with morale, and helping me ask for things I need :)
  • Thanks to @damianavila for code review :)

Updates from last week ✔

What I'm up to next ⬜

Availability this week

  • Monday & wednesday I'll be focusing on Berkeley's DataHub
  • Otherwise available, although limited headspace given the grim pandemic situation in India

@GeorgianaElena
Copy link
Member

Thanks I'd like to give 🙌

Updates from last week ✔

  • I mostly addressed the feedback received to some PRs I had already started (in between doctor appointments)

What I'm up to next ⬜

  • Not to much, since there's a national holiday coming (orthodox Easter) 🐰 , but I plan to finish up switching pilot-hubs to JupyterLab3 and start the same process for the UToronto hub

@consideRatio
Copy link
Contributor

Thanks I'd like to give 🙌

  • I'm thankful for @choldgraf that has taken time to help me find ways to structure my work better.
  • I'm thankful for work to make the team workflow very concrete.

Updates from last week ✔

  • I've looked into and deployed https://github.com/ComputeCanada/magic_castle experimetally workflow exploration as part of the Jupyter Meets the Earth project
  • I've tracked down some bugs for dask-gateway (Sandvik funded)
  • I've tried addressing GitHub action's security regarding the secrets.GITHUB_TOKEN across the JupyterHub org
  • Connected a bit with the Jupyter RTC efforts

What I'm up to next ⬜

  • MagicCastle deployment, dask-gateway robustness, learn more about intake
  • Explore the needs for Jupyter RTC from a JupyterHub standpoint

Links to items for discussion 💬

@damianavila
Copy link
Contributor

Thanks I'd like to give 🙌

  • Thanks to @choldgraf for providing me with more context about 2i2c and ICSI relationship
  • Thanks to @yuvipanda and @GeorgianaElena for being receptive to my reviews 😉
  • Thanks @yuvipanda for the AWS access and follow up conversation about the stuff deployed there

Updates from last week ✔

  • Sneak peek into 2i2c AWS deployment
  • Provided feedback on several team member issues and PRs (configurator UI, pilot homepage, project management, etc)
  • Some admin stuff (insurance brokers, some ICSI forms)

What I'm up to next ⬜

  • Explore the JupyterBook ecosystem
  • Provide feedback on other team members active PRs/discussions (so I get more insight into the hubs deployment by reading/reviewing code 😉)
  • Explore the 2i2c meta space to get more contextual information

Links to items for discussion 💬

  • I will insist 😉 on an interesting discussion on pods affinity: link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants