Define a system for managing our blog and its content

[choldgraf]

Description

We have a blog at 2i2c.org/blog . It contains a collection of "notable updates" (some short, some long) from 2i2c to the external world. It is the primary way for us to communicate our actions and progress in a "long-form" style of writing.

Historically, @choldgraf has written most of the content there. In addition, we have had many (reference list at the bottom for example) examples of "this would be great as a blog post" issues that get lost because there is no process for turning an idea for a blog post into action.

We should improve this system so that there's more clarity and reliability in posting content to our blog.

Linked goal or project

This goal is not yet created, but I think it feeds into an organizational goal of improving the efficiency of our organizational delivery and operations. Given that communication is an important part of our organization's lifecycle, tightening up processes around communication will reduce friction and coordination burden.

Why is this important?

Because our blog is the primary way that we communicate with the outside world, it's important that we have a system for regularly pushing content. This boosts our visibility, gives us a chance to own our own narrative, provides transparency to our external stakeholders, and gives a useful "notable events" trail of posts for when we need to put together reports.

Measures and definition of done

We should have a system that reliably posts content on 2i2c's blog. It needs to define the roles, responsible parties, and processes to follow so that there's clarity on the "next step" when there's something worth posting publicly.

Tasks

Preview Give feedback

1. A growing list of tasks and actions used to coordinate work around this initiative.
2. Each should be an actionable issue that we track independently.
3. This may be empty when the initiative is created! The initiative's goals should be used to decide what action issues to create next.

Examples of dangling issues on the blog

• [blog] Cloud billing guide #825
• [blog] CZI three year report  #824
• https://github.com/2i2c-org/meta/issues/933
• Write a blog post with devseed about unlisted_choice development infrastructure#3107
• Blog post: Pangeo hub deployment #244
• Blog Post: Pangeo optimization updates #31
• Blog post: NASA TOPS-T grant #717
• Co-write a blog post with Rocker folks about using Rocker on JupyterHub infrastructure#3543
• Blog Post: Cost optimization for the Berkeley DataHub #30
• Drafts of several blog posts from our recent activity #331
• Write a blog post about the U. Toronto hub deployment #141
• Write a blog post about the AWS infrastructure in the pilot hubs #101
• [blog] Cloud cost considerations for single-VM vs. Kubernetes #366
• Create content for a blog post for the section "Some roles and directives on Nikola via Myst" upstream#35

[aprilmj]

This initiative looks like it's largely been replaced by work @jnywong did to organize the blog posts and boost them via social media. Can we close it?

[jnywong]

Yes, let's close this.

(ref https://github.com/2i2c-org/meta/issues/1388)

[choldgraf]

@jnywong could you take a look at the dangling issues list at the top, add any that seems worthy to the upcoming blog posts table, and close all those issues?

[jnywong]

Hey yep! Just saw this comment, I'll make sure all of your precious work above does not get lost in the system 👍