Skip to content
This repository was archived by the owner on Nov 9, 2017. It is now read-only.

Commit e07c812

Browse files
add charter 1.0
1 parent 0954087 commit e07c812

File tree

1 file changed

+115
-1
lines changed

1 file changed

+115
-1
lines changed

README.md

+115-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,117 @@
11
# Inclusivity Working Group
22

3-
This working group is still in the early stages of getting up and running. Check back soon for more info!
3+
## Proposed Charter
4+
5+
(This charter has not yet been ratified by the Node.js TSC.)
6+
7+
### Statement of Purpose
8+
9+
The Inclusivity Working Group seeks to increase inclusivity and diversity
10+
for the Node.js project:
11+
- Increasing inclusivity seeks to make the Node.js project a safe and
12+
friendly place for people from diverse backgrounds.
13+
- Increasing diversity seeks to actively onboard people from diverse
14+
backgrounds to the Node.js project and maintain their participation.
15+
16+
### Membership
17+
> This is currently In-Progress. Please join the conversation [here][1].
18+
19+
Membership and participation with the Inclusivity Working Group is open
20+
to any member of the Node.js Github Organization.
21+
22+
Additionally, membership and participation in the Inclusivity
23+
Working group may also be extended to those people who are not represented
24+
in the Node.js Github Organization but are active in the greater Node.js
25+
Community.
26+
27+
More information about joining this Working Group is available in our
28+
[Membership Policy][1].
29+
30+
### Code of Conduct
31+
> This is currently In-Progress. Please join the conversation [here][2].
32+
33+
Due to the nature of the work the Inclusivity Working Group engages in,
34+
it employs a [more specific and stricter Code of Conduct][2] than the
35+
[Node.js project][4]. It is our belief that both Codes of Conduct are in
36+
the same spirit, the Working Groups' CoC simply being an extension of
37+
Node.js' CoC, with additional operational details regarding enforcement.
38+
39+
### Scope
40+
41+
The Inclusivity Working Group shall have autonomy over enforcing its own
42+
Code of Conduct and moderating its own PRs, issues, Slacks, and other
43+
Inclusivity Working Group community spaces.
44+
45+
The Inclusivity Working Group explicitly does *not* have moderation or
46+
enforcement power in the greater Node.js community or Project. It will,
47+
however, make recommendations and provide guidance to the community
48+
of collaborators on moderation and enforcement in
49+
regards to incidents on the project and in the community. These
50+
recommendations are not binding in any way.
51+
52+
If those recommendations are controversial or cannot be resolved through
53+
normal discourse, then they can be escalated to the TSC per the normal
54+
governance process.
55+
56+
### List of Responsibilities
57+
58+
* Foster a welcoming environment that ensures participants are valued and can
59+
feel confident contributing or joining discussions, regardless of any aspect of
60+
their identity, including but not limited to:
61+
- racial or ethnic background
62+
- nationality
63+
- language
64+
- skill level or expertise
65+
- [gender or sex][3]
66+
- physical or mental ability
67+
- age
68+
- religion, or lack thereof
69+
* Proactively seek and propose concrete steps the project can take to increase
70+
inclusivity.
71+
* Serve as a resource for the development and enforcement of workflows that
72+
protect community members and projects from harassment and abuse.
73+
* Acknowledge and celebrate existing diversity accomplishments within the
74+
project while seeking to build upon them.
75+
* Identify ways to measure diversity and inclusivity within the project and
76+
report them at regular intervals.
77+
78+
### Communication Policy
79+
80+
As is the case in the TSC, the Inclusivity Working Group seeks to be as
81+
transparent and public in its communications as possible.
82+
83+
However, due to the nature of the work the WG engages in, it is necessary
84+
that some private and invite-only spaces exist.
85+
86+
Private spaces will specifically be created to discuss:
87+
- Incident Reporting
88+
- Incident Response
89+
- Early Policy Discussions
90+
91+
All private communication will be anonymized and posted publicly for discussion.
92+
In no way will any binding decisions be made in private. All decisions will be
93+
either line items in public reports or, for larger topics, be summarized in public
94+
issues, specifically to receive structured community feedback for no less than a
95+
one week review period.
96+
97+
We believe that private spaces will mitigate the intense, often unintended public
98+
backlash people can often incur when dealing with an inclusivity situation. The
99+
goal for the private spaces is to create a safe space for education and understanding.
100+
101+
### Initial Membership
102+
103+
* [@ashleygwilliams](https://github.com/ashleygwilliams) (Ashley Williams, ag_dubs)
104+
* [@beaugunderson](https://github.com/beaugunderson) (Beau Gunderson)
105+
* [@juliepagano](https://github.com/juliepagano) (Julie Pagano)
106+
* [@nathan7](https://github.com/nathan7) (Nathan Zadoks)
107+
* [@nebrius](https://github.com/nebrius) (Bryan Hughes)
108+
* [@sup](https://github.com/sup) (Jona Hugger)
109+
* [@thefourtheye](https://github.com/thefourtheye) (Sakthipriyan Vairamani)
110+
* [@Trott](https://github.com/Trott) (Rich Trott)
111+
* [@zkat](https://github.com/zkat) (Kat Marachan)
112+
* *your name here*
113+
114+
[1]: https://github.com/nodejs/inclusivity/pull/32
115+
[2]: https://github.com/nodejs/inclusivity/pull/22
116+
[3]: http://www.glaad.org/reference/transgender
117+
[4]: https://github.com/nodejs/node/blob/master/CODE_OF_CONDUCT.md

0 commit comments

Comments
 (0)