Weekly Update - Monday, December 13th

[github-actions]

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

Weekly Update

**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

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...
- Could somebody take a look at ...

[yuvipanda]

Thanks I'd like to give 🙌

• To @felder for taking charge of the user homedirectory archival process
• To @ryanlovett for getting latest RStudio working in JupyterHub!

Updates from last week ✔

• Helped @felder with user homedirectory archiving process.
• Fiddled a bit more with RTC stuff
• Opened a request for implementation of a more ideal home directory archiver https://discourse.jupyter.org/t/request-for-implementation-archive-user-home-directories-transparently-to-object-storage-for-massive-cost-savings/12129?u=yuvipanda

[balajialg]

Thanks I'd like to give 🙌

• Thanks a lot @ericvd-ucb for advocating additional bandwidth for the team with the CDSS leadership and initiating conversations with all relevant stakeholders involved
• Thanks @felder for unblocking @sean-morris's upgrade work with gofer grader in the Data 8x hub
• Thanks @yuvipanda for suggesting the potential pathways with EECS as part of Explore cost sharing model for EECS 16 A lab compute requirement! #3019 and @felder for helping me understand the institutional context required to move the conversation forward.

Updates from the last couple of weeks ✔

• Worked with @ericvd-ucb on a proposal to articulate the potential pathways to add additional bandwidth for the team. One tangible next step from these conversations would be a big meeting in January with many relevant stakeholders to move the conversation forward.
• Spent a lot of time tracking accessibility-related work across Jupyter ecosystem and created Track Jupyter Lab and Notebook Accessibility #3074 to highlight the required next steps from our end to move the conversation forward. Would love feedback from the team with regards to this!
• Initiated the EECS cost-sharing conversation with the team! Considering the 2 pathways identified (Re: Explore cost sharing model for EECS 16 A lab compute requirement! #3019) to share the infrastructure costs, need to start the conversation with EECS stakeholders during January
• Updated the documentation for RTC functionality based on some feedback from @ericvd-ucb!
• Did an analysis of the historical logs from 2019 present in the Google Cloud bucket as part of the Analyze logs data to list course enrollments! #2949. Need to extend this effort to analyze the log data prior to 2019 shared by @yuvipanda
• Presented an intro to Datahub to the RTL leadership and received positive feedback about the service's growth and impact!
• Demoed admin and RTC functionality to ISchool folks! Will be setting up some time with ISchool Intro to Python course instructors prior to the winter break to demo the RTC feature. Hopefully, they can use this as part of their course during Spring 2022. Working closely with them to streamline the support requests at their end

[balajialg]

@felder Closing this issue for this week, but it would be awesome if you could share necessary updates once every two weeks or suggest changes to make this process work well for you!