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

Write a blog post about our overall cloud cost control strategy #4451

Open
yuvipanda opened this issue Jul 19, 2024 · 14 comments · May be fixed by 2i2c-org/2i2c-org.github.io#331
Open

Write a blog post about our overall cloud cost control strategy #4451

yuvipanda opened this issue Jul 19, 2024 · 14 comments · May be fixed by 2i2c-org/2i2c-org.github.io#331
Assignees

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Jul 19, 2024

As we start working on providing better cost control to our communities, we want to lay out a overarching narrative of how we are going to be doing that, in line with our principles and strengths. It has two audiences:

  1. External budget owners, who need to understand how to model cloud costs for their communities
  2. 2i2c team members, as we try to make choices in our product building process.

This overarching narrative in this blog post would help keep us aligned, and help get us out of unnecessary rabbitholes.

Deadline for complete draft: Friday 16 August

@yuvipanda
Copy link
Member Author

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

@jnywong
Copy link
Member

jnywong commented Jul 26, 2024

@yuvipanda I've reviewed your first draft 💪

@jnywong
Copy link
Member

jnywong commented Jul 31, 2024

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

@yuvipanda yuvipanda self-assigned this Jul 31, 2024
@jnywong
Copy link
Member

jnywong commented Aug 7, 2024

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! ✈️

@yuvipanda
Copy link
Member Author

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

@jnywong
Copy link
Member

jnywong commented Aug 29, 2024

Sounds good!

@aprilmj
Copy link

aprilmj commented Nov 8, 2024

@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

@jnywong
Copy link
Member

jnywong commented Nov 11, 2024

@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?

@jnywong
Copy link
Member

jnywong commented Nov 15, 2024

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

@jnywong
Copy link
Member

jnywong commented Nov 15, 2024

@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 👍

@Gman0909
Copy link
Contributor

Can this be closed now that the post is out?

@jnywong
Copy link
Member

jnywong commented Nov 20, 2024

@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?

@jnywong
Copy link
Member

jnywong commented Nov 20, 2024

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

@Gman0909
Copy link
Contributor

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.

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

Successfully merging a pull request may close this issue.

4 participants