-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add post about non-code contributions #2765
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
Conversation
Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
|
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 |
bwplotka
left a comment
There was a problem hiding this 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?
| 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. |
There was a problem hiding this comment.
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 (:
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 😄
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>
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 😊 |
Thank you @bwplotka. I think we're good to merge 👍 |
Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
Thanks! Yeah, I totally forgot to mention that in my Markdown guidelines as well 🙈 Gonna merge this then :) |
This pull request adds the blog post for the proposal discussed in #2759