Add CodeTriage badge to nodejs/node

[codetriage-readme-bot]

Adds a badge showing the number of people helping this repo on CodeTriage.

What is CodeTriage?

CodeTriage is an Open Source app that is designed to make contributing to Open Source projects easier. It works by sending subscribers a few open issues in their inbox. If subscribers get busy, there is an algorithm that backs off issue load so they do not get overwhelmed

Read more about the CodeTriage project.

Why am I getting this PR?

Your project was picked by the human, @schneems. They selected it from the projects submitted to https://www.codetriage.com and hand edited the PR. How did your project get added to CodeTriage? Roughly 11 months ago, iamrobinpham added this project to CodeTriage in order to start contributing. Since then 108 people have subscribed to help this repo.

What does adding a badge accomplish?

Adding a badge invites people to help contribute to your project. It also lets developers know that others are invested in the longterm success and maintainability of the project.

You can see an example of a CodeTriage badge on these popular OSS READMEs:

• https://github.com/rails/rails
• https://github.com/crystal-lang/crystal

Have a question or comment?

While I am a bot, this PR was manually reviewed and monitored by a human - @schneems. My job is writing commit messages and handling PR logistics.

If you have any questions, you can reply back to this PR and they will be answered by @schneems. If you do not want a badge right now, no worries, close the PR, you will not hear from me again.

Thanks for making your project Open Source! Any feedback is greatly appreciated.

[joyeecheung]

cc @nodejs/community-committee

IIRC there was something similar developed before to get new contributors help triaging our issues?

[joyeecheung]

FTR, I did not know what this is before this PR, looks like it's sent from @schneems

[schneems]

Yep, sent from me. Let me know if you've got questions. I can also move the badge to a different location if you want. The issues page seemed appropriate.

[bnb]

@joyeecheung you may be thinking of https://www.nodetodo.org/ by @Trott?

I'm generally +1. I'd more be concerned about churn created for the Node Core team than anything.

@schneems is there a way to pull issues from the entire org? I know there are many supplementary projects that would likely benefit from this in the Node.js Foundation.

[schneems]

is there a way to pull issues from the entire org?

Right now, if you want issues from multiple repos you need to sign up for each one individually. A "quick fix" could be for me to make an org page that would let you sign up for all repos in that org at once. I could then have a button that fires of X subscription requests for X repos on the page.

You're the second team to ask for something like that, so it seems like it would be useful. Let me know if something like that would be useful/helpful or if you had something else in mind.

[bnb]

@schneems Signing up for all the repos in the org at once would be interesting and probably beneficial, though we do have quite a suite of older repos that haven't been archived. Not sure if those have dead issues 🤔

[Trott]

I'm -1 on adding badges unless they are the ubiquitous kind that are nearly universally known and understood. IMO, this does not pass that test.

(I would love to get rid of the "cii best practices" badge. It's pretty pointless IMO.)

[schneems]

I could change it to a link with some explanation text. It would probably be more actionable than a badge.

[Trott]

(To be clear, I don't feel strongly enough about it to stand in the way if the Community Committee and/or more than one or two Collaborators are all like "heck yes, let's do this!")

[BridgeAR]

-0. No strong opinion about it though.

[schneems]

I added a paragraph with call to action as an alternative. Let me know if you prefer one or the other or have any suggested changes.

[BridgeAR]

@nodejs/collaborators PTAL

[mcollina]

I'm 👎 too for the same reason @Trott mentioned.

[vdeturckheim]

I'd be 👎 too

[cjihrig]

I'm also -1.

[BridgeAR]

I am closing this due to the general negative response. @schneems thanks a lot for your contribution and the suggestion anyway!

[schneems]

The negative responses seemed to be around the badge itself. I removed the badge and left only the text.

[BridgeAR]

I personally am also -0 on that.

@nodejs/collaborators If anyone thinks the text should land, please reopen.

[gibfahn]

I like the idea of this, notification overload is something we all struggle with, so anything that helps that would be great.

However it'd be good to learn more about how used this tool is before recommending it.

I could be wrong, but this seems like a tool that could be used as part of code-and-learns, mentorship, outreach etc. So maybe something that falls under the aegis of the @nodejs/community-committee ?

So maybe the right way forward is for us to try out CodeTriage and see how well it works. If it becomes something that helps contributors, then adding it to the repo would make sense.

[bnb]

@gibfahn I honestly agree that this likely falls under the CommComm, even though it's something that would live in the README.md in nodejs/node. It's 100% community enablement, but it does affect the Core Contributors which is why I was extremely cautious of the churn it would create for the Core Contributors above all else. I very much love this idea, and think there's likely a place for it.