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 - Mar 22, 2021 #58

Closed
choldgraf opened this issue Mar 22, 2021 · 3 comments
Closed

Team Sync - Mar 22, 2021 #58

choldgraf opened this issue Mar 22, 2021 · 3 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.

Priority Issues: The Priority Label issues are important and should be given attention over other issues.

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

Thanks I'd like to give 🙌

Updates from last week ✔

What I'm up to next ⬜

@choldgraf
Copy link
Member Author

Thanks I'd like to give 🙌

  • Thanks to @yuvipanda for making a bunch of PRs lately to improve the language around the managed jupyterhub services we offer 👍
  • Thanks @lheagy for giving your helpful input on the various team-compass / meta issues last week!

Updates from last week ✔

  • Much of last week I spent wrangling some grant opportunities (in JupyterHub and in Executable Books) for the next CZI EOSS round
  • I also spent a bit of time learning Monday.com (a project management platform) to understand whether it could be useful in helping us organize projects
  • Also did some more organization-wide stuff in the team compass, such as iterating on our CoC a bit

What I'm up to next ⬜

  • I am trying to think a bit about team process and how we can improve visibility, planning, and communication across our projects
  • I am trying to understand the divio documentation framework a bit to improve our team / project documentation
  • Finishing up the letters of intent for a few EOSS grants in the JupyterHub community

@GeorgianaElena
Copy link
Member

Thanks I'd like to give 🙌

  • @yuvipanda for sorting out old PRs and issues on TLJH
  • @yuvipanda for the great explanation on how the user storage works on the pilot hubs.
  • @yuvipanda for working on a JupyterHub configurator
  • @consideRatio for pushing forward and creating a strategy for z2jh regular releases
  • @choldgraf for docs improvements and reviews

Updates from last week ✔

What I'm up to next ⬜

  • Continue the work on the TLJH tests CI
  • Find ways to help with the z2jh regular releases

P.S. Sorry for posting after the bot closed the issue 😬

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

3 participants