Skip to content

Conversation

@nwanduka
Copy link
Contributor

This pull request adds the blog post for the proposal discussed in #2759

Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
@nwanduka
Copy link
Contributor Author

@juliusv @bwplotka when you get a chance, could you please take a look at this? thank you :)

@juliusv
Copy link
Member

juliusv commented Oct 31, 2025

Thank you @nwanduka, I think it's great! 🥳 Do you prefer @bwplotka to have a look as well before merging, or should we just do it?

One little thing though: Could you add a <!-- more --> marker line after the introductory section? This is processed by the docs site so that only the initial excerpt is shown as a preview on https://prometheus.io/blog/. I see now that this is missing for the latest blog post on there by @bwplotka as well, so it doesn't show any preview snippet for that currently.

Copy link
Member

@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing write up! Love the structure. Let's ship it! Do you want to merge it now?

Comment on lines +47 to +48
pull request that got merged. So, even when people are organizing events, supporting users, or conducting research, their work doesn't show up in
the same prominent ways code does.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing point. Wonder what can we do more here to improve visibility of this work (:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Different communities address this challenge in different ways. For example, some maintain a contributors list where people whose work isn’t reflected on GitHub can manually add their names. Others use a badging program to recognize non-technical contributions. In some cases, teams find creative ways to integrate GitHub into non-code workflows. For instance, a designer might create a PR that adds their design files to an assets folder so their work is also visible on GitHub.

Ultimately, I think it comes down to what works best for the Prometheus community. That could be adopting practices from other projects or coming up with our own unique approach to recognize all forms of contribution.

time parsing what users actually need instead of building solutions. A project manager or someone with triage experience could turn
that chaos into a clear roadmap, allowing maintainers to spend their time building solutions.

**It needs community support.** Imagine a user who joins the Slack workspace, excited to contribute. They don't know where to start.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's way more!

  • Product management
  • UX
  • Consensus management
  • coordinating work
  • marketing
  • events, mentoring

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely way more. Wish I could cover all of them in the article 😄

@bwplotka
Copy link
Member

One little thing though: Could you add a  marker line after the introductory section? This is processed by the docs site so that only the initial excerpt is shown as a preview on https://prometheus.io/blog/. I see now that this is missing for the latest blog post on there by @bwplotka as well, so it doesn't show any preview snippet for that currently.

Ah I was curious how to enable that! Wasn't easy to find :P

Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
@nwanduka
Copy link
Contributor Author

One little thing though: Could you add a <!-- more --> marker line after the introductory section? This is processed by the docs site so that only the initial excerpt is shown as a preview on https://prometheus.io/blog/. I see now that this is missing for the latest blog post on there by @bwplotka as well, so it doesn't show any preview snippet for that currently.

I've done that now. Thanks for pointing that out. I think I should update the blog guidelines with this info so future contributors don't miss it.

And thanks a lot for reviewing 😊

@nwanduka
Copy link
Contributor Author

Amazing write up! Love the structure. Let's ship it! Do you want to merge it now?

Thank you @bwplotka. I think we're good to merge 👍

Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
@juliusv
Copy link
Member

juliusv commented Nov 1, 2025

I've done that now. Thanks for pointing that out. I think I should update the blog guidelines with this info so future contributors don't miss it.

Thanks! Yeah, I totally forgot to mention that in my Markdown guidelines as well 🙈

Gonna merge this then :)

@juliusv juliusv merged commit 1189f16 into prometheus:main Nov 1, 2025
5 checks passed
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 this pull request may close these issues.

3 participants