Improving inclusivity in the node community
Latest commit d0abcec Dec 4, 2016 @nebrius nebrius committed on GitHub Merge pull request #152 from julianduque/master
Removing myself from the WG
Permalink
Failed to load latest commit information.
docs Updated removal instructions to include README Jun 20, 2016
meetings Add notes for 2016/06/07 meeting Jun 7, 2016
policies
programs add directories for policies and programs Jan 20, 2016
CODE_OF_CONDUCT.md Added "religion or lack thereof" to CoC Jan 22, 2016
CONTRIBUTING.md Renamed files to comply with style guide Apr 21, 2016
ISSUE_TEMPLATE.md Renamed files to comply with style guide Apr 21, 2016
README.md Removing myself from the WG Dec 2, 2016

README.md

Inclusivity Working Group

If you are interested in becoming a member of the Inclusivity Working Group, please submit your application here. If you would like to participate in our slack channel, please invite yourself here.

Charter

Ratified by the TSC, 14 January 2016

Statement of Purpose

The Inclusivity Working Group seeks to increase inclusivity and diversity for the Node.js project:

  • Increasing inclusivity means making the Node.js project a safe and friendly place for people from diverse backgrounds.
  • Increasing diversity means actively onboarding people from diverse backgrounds to the Node.js project and maintaining their participation.

Membership

Membership and participation with the Inclusivity Working Group is open to any member of the Node.js GitHub Organization.

Additionally, membership and participation in the Inclusivity Working group may also be extended to those people who are not represented in the Node.js GitHub Organization but are active in the greater Node.js Community.

More information about joining this Working Group is available in our Membership Policy.

Code of Conduct

Due to the nature of the work the Inclusivity Working Group engages in, it employs a more specific and stricter Code of Conduct than the Node.js project. It is our belief that both Codes of Conduct are in the same spirit, the Working Group's CoC simply being an extension of Node.js' CoC, with additional operational details regarding enforcement.

Scope

The Inclusivity Working Group shall have autonomy over enforcing its own Code of Conduct and moderating its own PRs, issues, Slacks, and other Inclusivity Working Group community spaces.

The Inclusivity Working Group explicitly does not have moderation or enforcement power in the greater Node.js community or Project. It will, however, make recommendations and provide guidance to the community of collaborators on moderation and enforcement in regards to incidents on the project and in the community. These recommendations are not binding in any way.

If those recommendations are controversial or cannot be resolved through normal discourse, then they can be escalated to the TSC per the normal governance process.

List of Responsibilities

  • Foster a welcoming environment that ensures participants are valued and can feel confident contributing or joining discussions, regardless of any aspect of their identity, including but not limited to:
    • racial or ethnic background
    • nationality
    • language
    • skill level or expertise
    • gender or sex
    • physical or mental ability
    • age
    • religion, or lack thereof
  • Proactively seek and propose concrete steps the project can take to increase inclusivity.
  • Serve as a resource for the development and enforcement of workflows that protect community members and projects from harassment and abuse.
  • Acknowledge and celebrate existing diversity accomplishments within the project while seeking to build upon them.
  • Identify ways to measure diversity and inclusivity within the project and report them at regular intervals.

Communication Policy

As is the case in the TSC, the Inclusivity Working Group seeks to be as transparent and public in its communications as possible.

However, due to the nature of the work the WG engages in, it is necessary that some private and invite-only spaces exist.

Private spaces will specifically be created to discuss:

  • Incident Reporting
  • Incident Response
  • Early Policy Discussions

All private communication will be anonymized and posted publicly for discussion. In no way will any binding decisions be made in private. All decisions will be either line items in public reports or, for larger topics, be summarized in public issues, specifically to receive structured community feedback for no less than a one week review period.

We believe that private spaces will mitigate the intense, often unintended public backlash people can often incur when dealing with an inclusivity situation. The goal for the private spaces is to create a safe space for education and understanding.

Members

License

Copyright Node.js Inclusivity Contributors SPDX-License-Identifier: MIT