Blog post October 2023

[choldgraf]

This is a blog post that was generated from our October 2023 team update slides. I've taken the content of those slides and tried to condense it into a relatively short blog post.

Here are major considerations I took:

• I removed any partnerships-related information that was about potential or future partnerships. I feel we should talk about things once they definitely happen, not as prospects.
• I removed all of the community-specific operational and bugfixing points.
• I removed a lot of the process-focused points, though provided some process updates in our general update section
• I highlighted the community-specific usage updates from @colliand - pease check that I described these properly.
• I combined our area-specific updates into a single set of sections for the organization. Functional areas make sense for internal reporting but I think the external world just thinks of this as "2i2c".

A few thoughts for future blog posts for @colliand and @damianavila

A few thoughts I noticed as I was writing this up, for consideration in future iterations. I know this was our first run, so we'd expect the need to make some improvements for next time. Here's what stood out to me:

• Whenever you mention a community, at the least provide a link to its website, as well as a short sentence for what that community is and what it does. Most of us (and certainly external people) don't have context for who these communities are.
• Try to focus on the things that are relevant directly within the last month (as opposed to general ideas or thoughts that span many months and just came to mind as you were writing).
• Whenever you mention changes to our service or infrastructure, make it clear why it is valuable to our communities. Most people (including myself!) don't have the context to understand the reason that a particular change is made and its implications, and that reason is the most important piece of information to convey.
• We need to do a better job of highlighting improvements to the service and in upstream communities. Right now we don't report any of this because it wasn't in the slides, but I think it is critical that we do a better job of tracking this impact.
  • For example, what are the 2-3 most important improvements across the JupyterHub ecosystem that we've been involved in, and that are relevant to our communities?

[damianavila]

This is good enough to be published as is.

I also do think I need to come up with better content in the slides so you can effectively use it at the time to write this sort of blog posts.