nodejs / inclusivity

Improving inclusivity in the node community
80 stars 22 forks source link

Creating medium-term plans #131

Closed nebrius closed 8 years ago

nebrius commented 8 years ago

Purpose

We have done a good job lately in getting all of the processes in place needed to run this working group smoothly, and now I think we're in a place to really start focusing on increasing the inclusivity and diversity of the Node.js project.

We originally planned to discuss this topic in the April 21st meeting but had to postpone due to smaller than anticipated number of members in attendance. Let's use this issue to brainstorm ideas which we can ratify at our next meeting.

Focus

This issue will have a broader than normal focus because it is something of a meta-issue. The purpose is to discuss what we should focus on in the medium-term, which I would define as the next 3 months or so. As such, we can get into discussions here about specifics related to our medium-term plans.

The results of this issue should be a series of issues, either newly created or pre-existing. We may want to consider creating a label to mark these issues.

Some off topic examples include, but are not limited to:

nebrius commented 8 years ago

I think that looking at the issues tagged with program could be a good place to start: https://github.com/nodejs/inclusivity/labels/program

nebrius commented 8 years ago

The program I would like to see worked on most is #79. This issue has morphed into effectively being a thread about improving the moderation process for the project, and attempting to prevent large-scale flare-ups and flame wars like we've seen in the past (think Promises). #44 and #66 are closely related (and perhaps should be merged).

I also think that the continuous translations issue is pretty interesting, #102, and it's attracted some attention too.

nebrius commented 8 years ago

Forgot to mention here, but our medium term plans include #132, #102, #61, #62, #96, #91, and #138