Skip to content

Commit

Permalink
WIP - doc: allow multiple orgs and add pkgjs org (#484)
Browse files Browse the repository at this point in the history
* doc: allow multiple orgs and add pkgjs org

Refs: #470

Signed-off-by: Michael Dawson <[email protected]>
  • Loading branch information
mhdawson authored Oct 14, 2022
1 parent 0fd9ecc commit 933dd6c
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 22 deletions.
24 changes: 14 additions & 10 deletions GITHUB_ORG_MANAGEMENT_POLICY.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
# Node.js GitHub Organization Management Policy

The Node.js GitHub Organization (https://github.com/nodejs) is
a development resource under the direction
of the Node.js Technical Steering Committee (TSC).
The Node.js GitHub Organizations:

* (https://github.com/nodejs)
* (https://github.com/pkgjs)

are development resources under the direction
of the Node.js Technical Steering Committee (TSC)

## Node.js Admin Repository

Expand Down Expand Up @@ -35,24 +39,24 @@ moderation across the existing repositories.

### Members

GitHub users are added as members to the Node.js GitHub Organization when they
GitHub users are added as members to the **Node.js** GitHub Organization when they
are added to any Working Group or team. Organization Owners should add new
members to the organization when requested by a Working Group or team.

## Repositories

Any repository created under the Node.js GitHub Organization is considered to be
Any repository created under the Node.js Organizations are considered to be
a project under the ownership of the OpenJS Foundation, and thereby subject
to the Intellectual Property and Governance policies of the Foundation.

Any organization member may request the management of repositories within the
Node.js GitHub Organization by opening an issue in the
Any member of one of the Node.js organizations may request the management
of repositories within the GitHub Organizations by opening an issue in the
[Node.js admin repository][nodejs/admin]. The actions requested could be:

- Creating a new repository
- Deleting an existing repository
- Archiving an existing repository
- Transferring a repository into or out of the organization
- Transferring a repository into or out of one of the organizations

Provided there are no objections from any TSC members raised in
the issue, such requests are approved automatically after 72 hours. If any
Expand Down Expand Up @@ -87,8 +91,8 @@ to join.

## Removing or Blocking Individuals

Only Node.js GitHub Organization owners may remove an individual from the
Node.js membership or block individuals. This is due largely to
Only GitHub Organization owners may remove an individual from the
membership or block individuals. This is due largely to
limitations in the way GitHub permissions are structured.

To remove any current member from the GitHub organization, an issue must be
Expand Down
26 changes: 14 additions & 12 deletions Moderation-Policy.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Moderation policy

If you are not a member of the Node.js GitHub Organization and wish to submit a
If you are not a member of the Node.js GitHub Organizations and wish to submit a
moderation request, please see [Requesting Moderation][]

* [Applicability][]
Expand All @@ -20,10 +20,10 @@ moderation request, please see [Requesting Moderation][]

## Applicability

This policy applies to all repositories under the Node.js GitHub
Organization and all Node.js Working Groups. This policy also applies to the
[Node.js Slack Community](https://node-js.slack.com), supported by the Admin
team of the Slack organization.
This policy applies to all repositories under the Node.js
[GitHub Organizations][] and all Node.js Working Groups. This policy also
applies to the [Node.js Slack Community](https://node-js.slack.com),
supported by the Admin team of the Slack organization.

## Terms

Expand All @@ -38,10 +38,10 @@ team of the Slack organization.
address Code of Conduct violations.
* *Remove* refers to the act of removing the configured write (commit)
permissions for an individual Collaborator's GitHub account from *all*
Node.js GitHub Organization repositories as well as removing the account from
the Node.js GitHub Organization membership.
Node.js GitHub Organizations repositories as well as removing the account from
the Node.js GitHub Organizations membership.
* *Block* refers to the act of prohibiting an individual GitHub account from any
further participation in the Node.js GitHub Organization. A block may be
further participation in the Node.js GitHub Organizations. A block may be
*temporary* or *indefinite*.
* This Moderation Policy applies only to blocking from the organization.
Individuals may choose to
Expand Down Expand Up @@ -89,7 +89,7 @@ used to request Moderation.

Collaborators must never discuss the specific details of a Moderation request
in any public forum or any social media service outside of the Node.js GitHub
Organization.
Organizations.

Note that quoting the original content of a Post within a Moderation request or
nodejs/moderation repository issue is not considered a violation of the
Expand Down Expand Up @@ -119,12 +119,12 @@ a Post from Moderation.
within that repository's issue tracker.
* The Moderation Team serves as the final arbiter for all Moderation issues.
* Moderation Team members may Remove or Block an individual from the Node.js
GitHub Organization.
GitHub Organizations.
* For any Removal or Blocking action, an issue describing the reasons for the
action, and identifying the Github account being acted upon, must be posted
to the Moderation Repository with an explanation provided by the Moderation
Team member performing the action.
* Any individual Blocked from the Node.js GitHub Organization will be recommended
* Any individual Blocked from the Node.js GitHub Organizations will be recommended
for exclusion from any Node.js Foundation sponsored event or activity.
* Minor edits to the formatting of a Post or to correct typographical errors
are not considered to be "Moderation". Such edits and their intent must
Expand Down Expand Up @@ -194,7 +194,7 @@ of the [Code of Conduct][].

The Moderation Team may, at their discretion, choose to enable [GitHub's
Temporary Interaction Limits][] on any GitHub repository in the Node.js GitHub
Organization.
Organizations.

Any Collaborator may request that the Moderation Team enable the Temporary
Interaction Limits by posting an issue to the moderation repository. If the
Expand Down Expand Up @@ -347,3 +347,5 @@ any proposed change, a TSC vote in favor of the change is required.
[Modifications to This Policy]: #modifications-to-this-policy
[[email protected]]: mailto:[email protected]
[block other individuals from their personal GitHub accounts]: https://help.github.com/en/articles/blocking-a-user-from-your-personal-account
[GitHub Organizations]: https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANAGEMENT_POLICY.md

0 comments on commit 933dd6c

Please sign in to comment.