Merge Working Groups and Collaboration Spaces

Closes #1110

CPC-CHARTER.md

@@ -86,8 +86,8 @@ Voting members have the roles and responsibilities as outlined below.
 
 Subject to such policies as may be set by the Board, the CPC is responsible for:
 
-   1. When needed, members of the CPC will be expected to create subcommittees or working groups.
-      The CPC will delegate responsibilities and empower these groups to make decisions.
+   1. When needed, members of the CPC will be expected to create subcommittees or `collaboration spaces`.
+      The CPC may delegate responsibilities and empower these groups to make decisions.
       Any of the responsibilities listed below not identified as being responsibilities of the Voting members may be delegated.
       For the remaining responsibilities, day-to-day work, investigation, and building recommendations may be delegated, however, the final responsibility will remain with the Voting members.
    1. Ensuring collaboration is the driving principle within a Project, between OpenJS Foundation Projects, and between OpenJS Foundation Projects and the broader community.

README.md

@@ -84,19 +84,22 @@ The following projects are official OpenJS Foundation projects. If you are inter
 The following are official OpenJS Collaboration spaces.
 If you are interested in fostering collaboration with the support of the OpenJS foundation through a collaboration space, please read our [Collaboration Space Progression](./collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md)
 
-| Name                                         |  Repository                        | Description                                                     |
-| -------------------------------------------- |:----------------------------------:|-----------------------------------------------------------------|
-| Ecosystem Report                             | [Repository][ecosystem-report]     | JavaScript ecosystem annual end-users poll and report            |
-| Open Visualization (OpenVis)                 | [Repository][openvis]              | Visualization libraries based on JavaScript and WebGL           |
-| Package Metadata Interop                     | [Repository][pkg-metadata-interop] | Interoperability of package.json across the JS ecosystem        |
-| Package Vulnerability Management & Reporting | [Repository][pkg-vuln]             | Package vulnerability management and reporting                  |
-| Security                                     | [Repository][security]             | Documentation and coordination of the Foundation's security effort |
+| Name                                         |  Repository                        | Authority Delegation   | Description                                                     |
+| -------------------------------------------- |:----------------------------------:| ---------------------- | ----------------------------------------------------------------|
+| Ecosystem Report                             | [Repository][ecosystem-report]     | No                     | JavaScript ecosystem annual end-users poll and report            |
+| Open Visualization (OpenVis)                 | [Repository][openvis]              | No                     | Visualization libraries based on JavaScript and WebGL           |
+| Package Metadata Interop                     | [Repository][pkg-metadata-interop] | No                     | Interoperability of package.json across the JS ecosystem        |
+| Package Vulnerability Management & Reporting | [Repository][pkg-vuln]             | No                     | Package vulnerability management and reporting                  |
+| Security                                     | [Repository][security]             | No                     | Documentation and coordination of the Foundation's security effort |
+| Standards                                    | [Repository][standards]            | [Yes][standards-deleg] | Facilitate the engagement of projects and collaborators in standards organizations |
 
 [ecosystem-report]: https://github.com/openjs-foundation/ecosystem-report
 [openvis]: https://github.com/openjs-foundation/openvis-collab-space
 [pkg-metadata-interop]: https://github.com/openjs-foundation/package-metadata-interoperability-collab-space
 [pkg-vuln]: https://github.com/openjs-foundation/pkg-vuln-collab-space
 [security]: https://github.com/openjs-foundation/security-collab-space
+[standards]: https://github.com/openjs-foundation/standards
+[standards-deleg]: ./collaboration-spaces/COLLABORATION_NETWORK.md#standards-collaboration-space
 
 ## CPC Meetings
 
@@ -236,10 +239,9 @@ If an Observer fails to meet these expectations they can be excluded from future
 * [Policy Proposal Process](PROPOSAL_PROCESS.md) - Process by which the CPC creates new policies and processes.
 * [GitHub organization Management Policy](./governance/GITHUB_ORG_MANAGEMENT_POLICY.md) - Policy for managing the CPC's GitHub organization.
 
-#### Collaboration Spaces and Working Groups
+#### Collaboration Spaces
 * [Collaboration Network](./collaboration-spaces/COLLABORATION_NETWORK.md)
 * [Collaboration Space Progression](./collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md)
-* [Working Groups](./governance/WORKING_GROUPS.md)
 
 #### Community Fund
 
@@ -251,7 +253,7 @@ If an Observer fails to meet these expectations they can be excluded from future
 
 ### Policy Change Proposal Process
 
-The OpenJS CPC is chartered to oversee the technical governance of all OpenJS Projects, Collaboration spaces and Working Groups under the OpenJS Foundation. The CPC establishes the default governance, conduct, and licensing policies for all Projects and Collaboration spaces. Projects have broad powers of self-governance.
+The OpenJS CPC is chartered to oversee the technical governance of all OpenJS Projects and Collaboration spaces under the OpenJS Foundation. The CPC establishes the default governance, conduct, and licensing policies for all Projects and Collaboration spaces. Projects have broad powers of self-governance.
 
 Anyone may submit an idea for a policy or program following the [proposal process](PROPOSAL_PROCESS.md).
 

collaboration-spaces/COLLABORATION_NETWORK.md

@@ -18,10 +18,26 @@ Support includes but not be limited to:
 
 The current Collaboration Networks spaces are listed in the main README.md in the CPC repository.
 
-Collaboration spaces differ from Working Groups in that existing authority is not delegated from the CPC as is the case with a Working Group.
-Instead of delegation of authority, the goal of a collaboration space is to support collaboration in a more independent manner.
-The work of the space does not necessarily represent the Foundation (just like the views and direction of an individual project do not
-necessarily represent the views of the Foundation) but is instead fostered and supported by the Foundation.
-In this sense the relationship is more like that of projects to the Foundation versus Working Groups.
-
 The [Collaboration Space Progression](./COLLABORATION_SPACE_PROGRESSION.md) document explains how a proposal for a new Collaboration space may be submitted and how Collaboration spaces move between stages.
+
+## Authority Delegation
+
+The Cross Project Council (CPC) main delegate scoped authority to a collaboration space. In such cases, the collaboration space may formally represent the Foundation, for example in a standards organization.
+
+Collaboration Spaces to which the CPC delegates authority are listed below:
+
+### Standards Collaboration Space
+
+The purpose of the Standards Collaboration Space is to act as a facilitator for OpenJS Foundation projects to support their engagement in various Standards Organizations, Working Groups, Technical Committees, and other spaces where internationally recognized standards are collaborated upon.
+
+Responsibilities include:
+
+* approve and support OpenJS Foundation project contributors in attending meetings held by standards organizations
+* make OpenJS Foundation project contributors aware of developments in relevant standards
+* help OpenJS Foundation projects formulate a standards strategy
+* support new contributors to standards-making activities
+* mentor project contributors who are unfamiliar with standards-making processes
+* make recommendations to the Cross Project Council regarding standards organization membership
+* managing ongoing relationships with standards ogranizations
+* ensuring that OpenJS representatives are aware of the responsibility of being a delegate of the foundation as outlined in [the membership expectations](https://github.com/openjs-foundation/standards/blob/HEAD/MEMBER_EXPECTATIONS.md)
+* facilitate when different projects' needs conflict resolution

collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md

@@ -3,19 +3,15 @@
 This governance policy describes how a new `Collaboration Space` can be established within the OpenJS Foundation, hereinafter referred to as the "Foundation", via the [Collaboration Space Proposal Process](#ii-collaboration-space-proposal-process).
 It describes the [Stages](#stages) a collaboration space may be admitted under and what the criteria and expectations are for a given stage, as well as the acceptance criteria for a space to move from one stage to another.
 
-`Collaboration Spaces` are different than `Working Groups` in a number of ways:
-* `Working Groups` are formally delegated responsibility from the scope of the Cross Project Council so that they can make autonomous decisions with respect to the delegated scope.
-  The subject of a `Collaboration Space` may be completely outside of the existing scope of the Cross Project Council.
-* `Working Groups` are generally made up of an existing OpenJS members project contributors.
-  `Collaboration Spaces` are intended to expand the group of contributors to the work of the OpenJS Foundation's work by allowing people outside the OpenJS member projects to propose/collaborate on areas of importance to the JavaScript ecosystem.
+The Cross Project Council (CPC) may [formally delegate authority](./COLLABORATION_NETWORK.md#authority-delegation) to a `Collaboration Space`, so that the `Collaboration Space` can make autonomous decisions with respect to the delegated scope.
+
+`Collaboration Spaces` are intended to expand the group of contributors to the work of the OpenJS Foundation's work by allowing people outside the OpenJS member projects to propose/collaborate on areas of importance to the JavaScript ecosystem.
 
 `Collaboration Spaces` may graduate between levels as outlined in this document.
-In addition, it may make more sense for them to be converted into a `Working group` if formal delegation of responsibility is beneficial or most of the contributions/leadership is being made from those who are active in the CPC.
-If there is an existing `Working Group` in a particular area a `Collaboration Space` will only be approved by the CPC with the support and approval from the `Working Group` that the space is complimentary.
 
 `Collaboration Space` applications must include the champions who will lead the effort and the credentials of the champion and those initially involved will be a key part of the evaluation process to ensure that the work of the spaces is aligned/respectful of the foundation vision and expectations.
 
-Collaboration space progression - movement from one stage to another - allows spaces to participate at the level that is most appropriate for them given where they are in their lifecycle. Regardless of stage, all Foundation spaces benefit from access to some level of  mentorship, support, and foundation resources.
+Collaboration space progression - movement from one stage to another - allows spaces to participate at the level that is most appropriate for them given where they are in their lifecycle. Regardless of stage, all Foundation spaces benefit from access to some level of mentorship, support, and foundation resources.
 
 ## II. Collaboration Space Proposal Process
 

governance/GITHUB_ORG_MANAGEMENT_POLICY.md

@@ -23,7 +23,7 @@ The following groups are granted Ownership permissions:
 
 ### Members
 
-GitHub users are added as members to the [OpenJS 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.
+GitHub users are added as members to the [OpenJS GitHub Organization][] when they are added to any Collaboration Space. Organization Owners should add new members to the organization when requested by a Collaboration Space or team.
 
 ## Repositories
 

governance/GOVERNANCE.md

@@ -134,7 +134,10 @@ Pull requests that do not change the charter or governance of the CPC can be mer
 * There are two approvals by CPC members
 * The PR has been open for at least 72 hours
 
-Pull requests that change governance of the CPC (including approving changes to Working Groups) must meet the following conditions in addition to the ones listed for regular PRs.
+The Cross Project Council (CPC) may [formally delegate authority](./COLLABORATION_NETWORK.md#authority-delegation) to a `Collaboration Space`, so that the `Collaboration Space` can make autonomous decisions with respect to the delegated scope.
+
+
+Pull requests that change governance of the CPC (including changes to [auhtority delegation to Collaboration Spaces](./COLLABORATION_NETWORK.md#authority-delegation)) must meet the following conditions in addition to the ones listed for regular PRs.
 
 * The PR has been open for at least 14 days OR consensus is reached in a meeting with quorum of voting members.