Next steps for Black Lives Matter support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content
Research direction
Start with the existing full-page support message and banner referenced in the issue, then review the eight-comment discussion. There are no files, tests, or implementation entry points named. Done would require an agreed course of action with clear measurable goals and actions, but the issue is locked to outside contributors and has been inactive for years.
Written by the indexing model from the issue text.
Description
First off, let me state up front that I'm locking this issue immediately to outside contributors.
@nodejs/tsc @nodejs/community-committee :
We need to discuss and decide upon the next stage of our committed support for Black Lives Matters. Our first step was to create the full page message of support which has now transitioned into a banner. In that message, we commit to taking proactive steps to continue improving diversity and inclusion across the project, as well as provide more opportunities to mentor black engineers (as well as other underrepresented groups). In order for that not to be an empty promise we should discuss and decide upon a course of action with clear measurable goals and actions.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sugarlabs/musicblocks#8924 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ArduPilot/ardupilot_wiki#8088 ·
-
[BUG] createTool tools cannot be registered with Mastra when exactOptionalPropertyTypes is enabled Opencustomer-eng status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100