Because otherwise I would have 50 thousand contributions every month (not joking) and i dont want to mix the “real” code contributions with the “side” contributions. Maybe adding another type of contribution could be the solution you want.

I do agree with @westyler that it would be a good thing if the organizers of a community would be rewarded for their work. But I also do agree with @wabri that things could get quite messy.

Since things like applying labels is something that is often done, it might be a good idea to consider contributions like PRs/commits/reviews a “full contribution”, while labelling and assigning issues could count as a “.1” contribution. 10 of these would make one full contribution. It’s interesting to think about.

I think that you both touched on the exact reason why I think this is an extremely valuable addition - our culture inherently places a significantly higher value on code contributions than anything else.

In my daily job, some of the hardest work that has the biggest payoff for our team is not the code that I write. It’s the help, mentoring, or training that I provide to my coworkers. In the same vein DevRels are commonly disregarded as “less important” than engineers, but in my experience our industry would collapse without them doing the hard people work.

As a more tangible example, the Node.js project maintainers are constantly triaging issues. Without those people managing the backlog of issues it would be nearly impossible as a code contributor or a user to find the information you need.

any update? :)