From a3d7fa52f0e161d378c9f92ec25092c93f28cae3 Mon Sep 17 00:00:00 2001 From: Julie Pagano Date: Sat, 30 Jan 2016 17:14:07 -0800 Subject: [PATCH 1/8] Initial draft of roles and responsibilities. --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 77 +++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 docs/POLICY_ROLES_RESPONSIBILITIES.md diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md new file mode 100644 index 0000000..b2e1608 --- /dev/null +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -0,0 +1,77 @@ +# Roles and Responsibilities +This document outlines the major roles and responsibilities associated with the inclusivity working group. + +## Roles +The inclusivity working group has two main roles for participants. + +### Member +Members are the core group of people responsible for the inclusivity working group. Members make a regular commitment to participating in the working group and contributing to deliverables. The target size for membership is 6-12 people. + +The current list of members can be found [here](https://github.com/nodejs/inclusivity#initial-membership). + +#### Becoming a member +See the [admissions policy](https://github.com/nodejs/inclusivity/blob/master/docs/POLICY_ADMISSIONS.md) for details about the process for becoming a member. + +#### Responsibilities +Members are expected to commit at least 10 hours a month (**Question for PR: is this time commitment too much/little?**) towards the working group's responsibilities. Members are expected to contribute in some way every two weeks because the group delivers on a biweekly basis. + +A member's time commitment can be spent on a variety of contributions including, but not limited to: + +- Preparing and participating in working group meetings. See [issue #64](https://github.com/nodejs/inclusivity/issues/64) for discussion around the roles and responsibilities for meetings. +- Developing new policies, documentation, etc. for the group (e.g. [add CONTRIBUTING.md content](https://github.com/nodejs/inclusivity/pull/88)). +- Developing resources for the wider node community (e.g. [Getting Started in Node.js Program](https://github.com/nodejs/inclusivity/issues/96)). +- Reviewing [pull requests](https://github.com/nodejs/inclusivity/pulls) on the inclusivity repository. +- Moderating [issues](https://github.com/nodejs/inclusivity/issues) on the inclusivity repository. +- Assisting with moderation outside the inclusivity repository, when the group is asked for help. +- Responding to emails and other outside requests sent to the inclusivity working group. +- Participating in discussions on the private and/or public working group slack channels. +- Outreach with other communities. +- Operations (e.g. managing membership for slack, github). +- Reviewing, voting on, and responding to membership requests. + +**Question for PR: Do we want to have requirements around attending meetings? If so, I'd like them to be a little loose to account for difficulties with time zones and accessibility, so we aren't losing diversity in our membership.** + +**Question for PR: Do we want to have anything about the member-only slack channel here, since we sometimes use it for discussions?** + +**Question for PR: Do we want to add something here about responsibilities around the code of conduct? I feel like members may be held to a higher standard.** + +If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a collaborator role. + +#### Permissions + +Members have the following level of access and permissions for the working group. + +- Are allowed to speak on behalf of the group in outreach, emails, etc. +- Have access to member-only, private slack channel. +- Receive emails sent to the working group's email ([inclusivity@nodejs.org](mailto:inclusivity@nodejs.org)). +- Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. +- Has priority for participation in working group meetings (because there are limited slots available in google hangouts). + +### Collaborator +Collaborators are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. + +#### Becoming a collaborator +**QUESTION FOR PR: Do we have a policy for becoming a collaborator? Should we? How does this work?** + +### Responsibilities + +Collaborators do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. + +Collaborator contributions may include, but are not limited to: + +- Making pull requests on the inclusivity repository. +- Contribution to discussions on issues and pull requests in the inclusivity repository. +- Participating in discussions on the public working group slack channel (to be created in the near future). + +#### Permissions + +Collaborators have the following level of access and permissions for the working group. + +- Have access to public slack channel. This does not currently exist, but will be created some time in the near future. +- Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. +- May participate in working group meetings when space allows. + +Collaborators **DO NOT** have permission to do the following. + +- Collaborators can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. +- Collaborators do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). \ No newline at end of file From f19578dbed71736beab11058b5220a7d2820b67f Mon Sep 17 00:00:00 2001 From: Julie Pagano Date: Thu, 4 Feb 2016 12:08:05 -0800 Subject: [PATCH 2/8] s/collaborator/contributor --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index b2e1608..e5d98ff 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -35,7 +35,7 @@ A member's time commitment can be spent on a variety of contributions including, **Question for PR: Do we want to add something here about responsibilities around the code of conduct? I feel like members may be held to a higher standard.** -If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a collaborator role. +If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a contributor role. #### Permissions @@ -47,17 +47,17 @@ Members have the following level of access and permissions for the working group - Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. - Has priority for participation in working group meetings (because there are limited slots available in google hangouts). -### Collaborator -Collaborators are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. +### Contributor +Contributors are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. -#### Becoming a collaborator -**QUESTION FOR PR: Do we have a policy for becoming a collaborator? Should we? How does this work?** +#### Becoming a contributor +**QUESTION FOR PR: Do we have a policy for becoming a contributor? Should we? How does this work?** ### Responsibilities -Collaborators do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. +Contributors do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. -Collaborator contributions may include, but are not limited to: +Contributor contributions may include, but are not limited to: - Making pull requests on the inclusivity repository. - Contribution to discussions on issues and pull requests in the inclusivity repository. @@ -65,13 +65,13 @@ Collaborator contributions may include, but are not limited to: #### Permissions -Collaborators have the following level of access and permissions for the working group. +Contributors have the following level of access and permissions for the working group. - Have access to public slack channel. This does not currently exist, but will be created some time in the near future. - Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. - May participate in working group meetings when space allows. -Collaborators **DO NOT** have permission to do the following. +Contributors **DO NOT** have permission to do the following. -- Collaborators can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. -- Collaborators do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). \ No newline at end of file +- Contributors can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. +- Contributors do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). From 7a10e2decd571fd9928e26d296c0db4ed90044de Mon Sep 17 00:00:00 2001 From: Julie Pagano Date: Thu, 4 Feb 2016 12:09:50 -0800 Subject: [PATCH 3/8] Add code of conduct enforcement to list of member responsibilities. --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index e5d98ff..941351c 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -22,6 +22,7 @@ A member's time commitment can be spent on a variety of contributions including, - Developing resources for the wider node community (e.g. [Getting Started in Node.js Program](https://github.com/nodejs/inclusivity/issues/96)). - Reviewing [pull requests](https://github.com/nodejs/inclusivity/pulls) on the inclusivity repository. - Moderating [issues](https://github.com/nodejs/inclusivity/issues) on the inclusivity repository. +- Enforcement of the working group's [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). - Assisting with moderation outside the inclusivity repository, when the group is asked for help. - Responding to emails and other outside requests sent to the inclusivity working group. - Participating in discussions on the private and/or public working group slack channels. From f30271bd7aabe4e526792323d481d58290f87f7b Mon Sep 17 00:00:00 2001 From: Julie Pagano Date: Sat, 27 Feb 2016 15:46:26 -0800 Subject: [PATCH 4/8] Updates based on discussions. - Renamed contributors to non-members. - Added details about github permissions for members and non-members. - Added reminders about the code of conduct for members and non-members. --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 42 +++++++++++++++++---------- 1 file changed, 26 insertions(+), 16 deletions(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index 941351c..7586e73 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -18,6 +18,7 @@ Members are expected to commit at least 10 hours a month (**Question for PR: is A member's time commitment can be spent on a variety of contributions including, but not limited to: - Preparing and participating in working group meetings. See [issue #64](https://github.com/nodejs/inclusivity/issues/64) for discussion around the roles and responsibilities for meetings. +- Participation in the member slack channel. - Developing new policies, documentation, etc. for the group (e.g. [add CONTRIBUTING.md content](https://github.com/nodejs/inclusivity/pull/88)). - Developing resources for the wider node community (e.g. [Getting Started in Node.js Program](https://github.com/nodejs/inclusivity/issues/96)). - Reviewing [pull requests](https://github.com/nodejs/inclusivity/pulls) on the inclusivity repository. @@ -32,11 +33,9 @@ A member's time commitment can be spent on a variety of contributions including, **Question for PR: Do we want to have requirements around attending meetings? If so, I'd like them to be a little loose to account for difficulties with time zones and accessibility, so we aren't losing diversity in our membership.** -**Question for PR: Do we want to have anything about the member-only slack channel here, since we sometimes use it for discussions?** +If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a non-member role. -**Question for PR: Do we want to add something here about responsibilities around the code of conduct? I feel like members may be held to a higher standard.** - -If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a contributor role. +As representatives of the working group, members are expected to set an example with the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). Violations of the code of conduct may lead to loss of member status and/or removal from the working group. #### Permissions @@ -45,34 +44,45 @@ Members have the following level of access and permissions for the working group - Are allowed to speak on behalf of the group in outreach, emails, etc. - Have access to member-only, private slack channel. - Receive emails sent to the working group's email ([inclusivity@nodejs.org](mailto:inclusivity@nodejs.org)). -- Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. +- Github: + - Content: view, edit. + - Issues: view, comment, edit, close. + - Pull requests: create, comment, merge, close. + - Moderation of issues, pull requests, etc. - Has priority for participation in working group meetings (because there are limited slots available in google hangouts). -### Contributor -Contributors are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. +### Non-members +Non-members are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. + +#### Becoming a non-member +Anyone can be a non-member. Review the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. -#### Becoming a contributor -**QUESTION FOR PR: Do we have a policy for becoming a contributor? Should we? How does this work?** +***Insert steps for getting access to the public slack here.*** ### Responsibilities -Contributors do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. +Non-members do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. -Contributor contributions may include, but are not limited to: +Non-member contributions may include, but are not limited to: - Making pull requests on the inclusivity repository. - Contribution to discussions on issues and pull requests in the inclusivity repository. - Participating in discussions on the public working group slack channel (to be created in the near future). +Non-members are expected to follow the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). Violations of the code of conduct may lead to removal from the working group. + #### Permissions -Contributors have the following level of access and permissions for the working group. +Non-members have the following level of access and permissions for the working group. - Have access to public slack channel. This does not currently exist, but will be created some time in the near future. -- Have **INSERT PERMISSION/ORG LEVEL INFORMATION HERE** access on github. +- Github: + - Content: view. + - Issues: view, comment. + - Pull requests: create, comment. - May participate in working group meetings when space allows. -Contributors **DO NOT** have permission to do the following. +Non-members **DO NOT** have permission to do the following. -- Contributors can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. -- Contributors do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). +- Non-members can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. +- Non-members do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). From 4fb7926429661318b749b1b6b9f9494d996948e4 Mon Sep 17 00:00:00 2001 From: Julie Pagano Date: Mon, 29 Feb 2016 10:52:30 -0800 Subject: [PATCH 5/8] Add create issues to github permissions. --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index 7586e73..6d01040 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -46,7 +46,7 @@ Members have the following level of access and permissions for the working group - Receive emails sent to the working group's email ([inclusivity@nodejs.org](mailto:inclusivity@nodejs.org)). - Github: - Content: view, edit. - - Issues: view, comment, edit, close. + - Issues: view, create, comment, edit, close. - Pull requests: create, comment, merge, close. - Moderation of issues, pull requests, etc. - Has priority for participation in working group meetings (because there are limited slots available in google hangouts). @@ -78,7 +78,7 @@ Non-members have the following level of access and permissions for the working g - Have access to public slack channel. This does not currently exist, but will be created some time in the near future. - Github: - Content: view. - - Issues: view, comment. + - Issues: view, create, comment. - Pull requests: create, comment. - May participate in working group meetings when space allows. From ec24082067b46421b5aaf74d9c693e6e206d5abc Mon Sep 17 00:00:00 2001 From: jona Date: Thu, 17 Mar 2016 20:22:34 +0100 Subject: [PATCH 6/8] fix nits --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 44 ++++++++++++--------------- 1 file changed, 20 insertions(+), 24 deletions(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index 6d01040..44830fc 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -2,7 +2,7 @@ This document outlines the major roles and responsibilities associated with the inclusivity working group. ## Roles -The inclusivity working group has two main roles for participants. +The inclusivity working group has two main roles for participants, Member and Contributor. ### Member Members are the core group of people responsible for the inclusivity working group. Members make a regular commitment to participating in the working group and contributing to deliverables. The target size for membership is 6-12 people. @@ -13,12 +13,12 @@ The current list of members can be found [here](https://github.com/nodejs/inclus See the [admissions policy](https://github.com/nodejs/inclusivity/blob/master/docs/POLICY_ADMISSIONS.md) for details about the process for becoming a member. #### Responsibilities -Members are expected to commit at least 10 hours a month (**Question for PR: is this time commitment too much/little?**) towards the working group's responsibilities. Members are expected to contribute in some way every two weeks because the group delivers on a biweekly basis. +Members are expected to contribute in some way every two weeks because the group delivers on a biweekly basis. -A member's time commitment can be spent on a variety of contributions including, but not limited to: +A member's time commitment can be spent on a variety of contributions including, but not limited to: - Preparing and participating in working group meetings. See [issue #64](https://github.com/nodejs/inclusivity/issues/64) for discussion around the roles and responsibilities for meetings. -- Participation in the member slack channel. +- Participation in the working group Slack channel. - Developing new policies, documentation, etc. for the group (e.g. [add CONTRIBUTING.md content](https://github.com/nodejs/inclusivity/pull/88)). - Developing resources for the wider node community (e.g. [Getting Started in Node.js Program](https://github.com/nodejs/inclusivity/issues/96)). - Reviewing [pull requests](https://github.com/nodejs/inclusivity/pulls) on the inclusivity repository. @@ -31,9 +31,7 @@ A member's time commitment can be spent on a variety of contributions including, - Operations (e.g. managing membership for slack, github). - Reviewing, voting on, and responding to membership requests. -**Question for PR: Do we want to have requirements around attending meetings? If so, I'd like them to be a little loose to account for difficulties with time zones and accessibility, so we aren't losing diversity in our membership.** - -If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a non-member role. +If a member will be unavailable to meet these responsibilities, they are expected to notify the group in a timely manner, so resources can be planned accordingly. A member who cannot maintain these responsibilities for a significant amount of time will be asked to transition to a contributor role. As representatives of the working group, members are expected to set an example with the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). Violations of the code of conduct may lead to loss of member status and/or removal from the working group. @@ -44,45 +42,43 @@ Members have the following level of access and permissions for the working group - Are allowed to speak on behalf of the group in outreach, emails, etc. - Have access to member-only, private slack channel. - Receive emails sent to the working group's email ([inclusivity@nodejs.org](mailto:inclusivity@nodejs.org)). -- Github: - - Content: view, edit. +- Github: + - Content: view, edit. - Issues: view, create, comment, edit, close. - Pull requests: create, comment, merge, close. - Moderation of issues, pull requests, etc. - Has priority for participation in working group meetings (because there are limited slots available in google hangouts). -### Non-members -Non-members are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. - -#### Becoming a non-member -Anyone can be a non-member. Review the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. +### Contributors +Contributors are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. -***Insert steps for getting access to the public slack here.*** +#### Becoming a contributor +Anyone can be a contributor. Review the [Code of Conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. ### Responsibilities -Non-members do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. +Contributors do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like. -Non-member contributions may include, but are not limited to: +Contributor contributions may include, but are not limited to: - Making pull requests on the inclusivity repository. - Contribution to discussions on issues and pull requests in the inclusivity repository. - Participating in discussions on the public working group slack channel (to be created in the near future). -Non-members are expected to follow the [code of conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). Violations of the code of conduct may lead to removal from the working group. +Contributor are expected to follow the [Code of Conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md). Violations of the code of conduct may lead to removal from the working group. #### Permissions -Non-members have the following level of access and permissions for the working group. +Contributors have the following level of access and permissions for the working group. - Have access to public slack channel. This does not currently exist, but will be created some time in the near future. -- Github: - - Content: view. +- Github: + - Content: view. - Issues: view, create, comment. - Pull requests: create, comment. - May participate in working group meetings when space allows. -Non-members **DO NOT** have permission to do the following. +Contributors **DO NOT** have permission to do the following. -- Non-members can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. -- Non-members do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). +- Contributors can not speak for the working group in outreach, emails, etc. unless explicitly given permission by members. +- Contributors do not have access to private working group communications (e.g. private slack channel, emails sent to the working group email address). From 3dfbfc71f1e697f624767e6eea042f40e6799349 Mon Sep 17 00:00:00 2001 From: jona Date: Thu, 17 Mar 2016 20:35:15 +0100 Subject: [PATCH 7/8] reword 'how to become a contributor' --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index 44830fc..8beeec5 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -52,8 +52,7 @@ Members have the following level of access and permissions for the working group ### Contributors Contributors are people who contribute to the inclusivity working group, but do not have specific responsibilities and commitments. -#### Becoming a contributor -Anyone can be a contributor. Review the [Code of Conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. +Anyone can be a contributor, and there is no admissions process for becoming a contributor. Review the [Code of Conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. ### Responsibilities From fe672329e8d3df589d5799962f8773a2b211b235 Mon Sep 17 00:00:00 2001 From: jona Date: Thu, 17 Mar 2016 20:43:08 +0100 Subject: [PATCH 8/8] add extra # to 'responsibilities' --- docs/POLICY_ROLES_RESPONSIBILITIES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/POLICY_ROLES_RESPONSIBILITIES.md b/docs/POLICY_ROLES_RESPONSIBILITIES.md index 8beeec5..0db5e73 100644 --- a/docs/POLICY_ROLES_RESPONSIBILITIES.md +++ b/docs/POLICY_ROLES_RESPONSIBILITIES.md @@ -54,7 +54,7 @@ Contributors are people who contribute to the inclusivity working group, but do Anyone can be a contributor, and there is no admissions process for becoming a contributor. Review the [Code of Conduct](https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md) before participating to familiarize yourself with expected behavior when contributing to the working group. -### Responsibilities +#### Responsibilities Contributors do not have any specific time or deliverable commitments. They may contribute to the working group as much or as little as they like.