admin
admin copied to clipboard
nodejs
Next steps for Black Lives Matter support
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.
First off, let me state up front that I'm locking this issue immediately to outside contributors.
To clarify, I assume this is to prevent troll spam (which I don't doubt would happen) and not because we want to exclude folks, right?
I think one of the first steps we need to take is follow through on making ourselves available for working with Black members of the ecosystem, either 1:1 or however they're comfortable. Providing multiple methods to approach us - a GitHub issue, a Calendly booking, and anything else that would be a path folks would reasonably connect with us - is going to be important for that.
One thing I will note: we shouldn't do this and expect people to show up. We should be proactive about outreach in a respectful way.
FWIW the black lives matter email address has continued to receive emails which we have actively been responding to and working with folks who have asked for support
FWIW the black lives matter email address has continued to receive emails which we have actively been responding to and working with folks who have asked for support
We should probably quantify that. Might be useful to share somewhere as evidence of action on the commitment. And is definitely useful as a metric we can look at for internal discussion about how we're doing and what next steps might be.
@Trott here are an idea of some numbers we could report. I'm not saying that we should, and we would likely want to talk with the people we are working more closely with to see if they are comfortable with this kind of data being shared.
- how many emails we received
- how many emails we received that were supportive of the message
- how many emails we received that were critical of the message
- how many emails we received that violated the code of conduct
- how many emails we received were actionable requests for support
- how many individuals felt that the project was successful in offering them support
- how many individuals felt that the project was unsuccessful in offering them support
I'd be interested in this one:
how many emails we received were actionable requests for support
The related ones about how people felt about our attempts to give them that support...that would be useful too, but not strictly necessary for that one above to be useful, and it seems like that one above is one we can count up more-or-less immediately, I would think.
some success criteria (that can be refined):
- n number of people mentored per year (define n)
- ~~n~~ m number of people on-boarded per year (define m)
- a survey conducted per year whose result shows visible and positive response about the initiative
Worth noting: only people with write access to this repository can now comment, which excludes much of the project's collaborators. We should probably unlock this.