I started a draft in https://hackmd.io/AqZxyS8oSyGCpWfyX3_pfA?both

@yuvipanda I've reviewed your first draft 💪

@yuvipanda just checking in case you need more help from me.

Hey! How can we get this one over the line? I think we agreed in our last sync to put a deadline on this so... I am choosing Aug 16 before you fly out! ✈️

@jnywong let's put this back on the backlog, and I'll pick this back up after I'm back from my time off.

Sounds good!

@yuvipanda or @jnywong does this card belong on the P&S wall? I'd also be ok with moving it under the broader marketing work

@yuvipanda what would you like to do with this one? I think we could repurpose the content to serve comms for the AWS rollout? #4879?

#4879 is now closed, but I am working on getting this blog post as a sister companion piece.

@yuvipanda I've opened a PR on this for you to review – I've updated parts where I could and it looks good to me 👍

Can this be closed now that the post is out?

@Gman0909 The blog post for this is not published: 2i2c-org/2i2c-org.github.io#331

I think you are maybe confusing this with #4879?

But I agree that this is a loose end that we need to either tie up or cut loose! :)

I was referring to #4879, yes, and my question was whether this is still relevant. In either case I think we should split this off into its own action and not let this hold up the closing of the parent initiative.

The idea for this post overlaps with more recent work on the tiered product menu. 2i2c and the people who buy services for communities want quotas to prevent cost explosions. I believe @Gman0909 and @yuvipanda will soon review the product menu from a technical perspective. Our recent work on cost and usage monitoring can be complimented with a nice post describing how quotas can be used to protect against explosions.

@yuvipanda I am archiving this with a view to potentially revisiting in future within the broader context of a community update.