Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

AWS cost attribution (4/4): communicate about the functionality via a blog post and share it with the communities #4879

Closed
2 of 3 tasks
Tracked by #4872
consideRatio opened this issue Sep 24, 2024 · 3 comments · Fixed by 2i2c-org/2i2c-org.github.io#329
Assignees

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Sep 24, 2024

Now that we have a cost attribution strategy and UI, we want to make sure the out communities know about it. We should write a blog post highlighting the background to this work - how it addresses one of the more pressing concerns for hub admins, managing to keep a handle on runaway costs - some of the functional highlights, and showing off some of the UI.

  • @consideRatio to get together with @jnywong to help her download the most important functional and technical highlights
  • @jnywong to write and publish a blog post showing off the new functionality.
  • Amplify the post on linkedin and other socials.
@consideRatio consideRatio changed the title AWS cost attribution (5/n): communicate about the functionality via a blog post and share it with the communities AWS cost attribution (4/4): communicate about the functionality via a blog post and share it with the communities Sep 25, 2024
@haroldcampbell
Copy link
Contributor

There is a dependency on feedback from the community on the work that we previously released.

@Gman0909
Copy link
Contributor

Gman0909 commented Oct 1, 2024

@haroldcampbell please check if this is sufficiently refined

@jnywong jnywong self-assigned this Oct 2, 2024
@jnywong
Copy link
Member

jnywong commented Oct 2, 2024

Thanks for the knowledge exchange @consideRatio !

I will queue this piece of work up into my next sprint and reach out to you if I have any further questions.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants