initial stab at repo cleanup (#841)

* initial stab at repo cleanup

* fixing links

Author: joesepi

CPC-CHARTER.md

@@ -160,10 +160,10 @@ Subject to such policies as may be set by the Board, the CPC is responsible for:
    1. Voting members are responsible for approving funds for budgets delegated
       to the project.
    1. Voting members are responsible for approving new `collaboration spaces` as outlined in the OpenJS
-      [COLLABORATION_NETWORK.md](COLLABORATION_NETWORK.md) process.
+      [COLLABORATION_NETWORK.md](./collaboration-spaces/COLLABORATION_NETWORK.md) process.
    1. Voting members are responsible for making final decisions on aligning `collaboration spaces`,
       removing or archiving `collaboration spaces`, as outlined in the
-      OpenJS [COLLABORATION_NETWORK.md](COLLABORATION_NETWORK.md) process.
+      OpenJS [COLLABORATION_NETWORK.md](./collaboration-spaces/COLLABORATION_NETWORK.md) process.
    1. Following and be up to date on Board/OpenJS Foundation initiatives and communicate them to the projects.
    1. Defining common practices to be implemented across OpenJS Foundation projects, if any.
    1. Mediating technical conflicts between OpenJS Foundation Projects when attempts to resolve

PROJECT_PROGRESSION.md

@@ -73,7 +73,7 @@ The Application Champion is a member of the CPC who commits to do the following:
         (ex. perhaps a different foundation would be a more suitable endeavor.)
    * Discussion/agreement between applicant, application manager and Foundation media team to agree on announce date.
 1. Project goes through process of adhering to [on-boarding checklist](#onboarding-checklist).
-1. Project completes a charter review process by the CPC as outlined in the [CPC Governance](./GOVERNANCE.md#approving-project-charters). NOTE: this process takes two weeks to complete
+1. Project completes a charter review process by the CPC as outlined in the [CPC Governance](./governance/GOVERNANCE.md#approving-project-charters). NOTE: this process takes two weeks to complete
 1. Project graduates from incubation by a pull request adding the project to the [README.md](./README.md) file at its appropriate initial stage. The merging of this pull request proceeds as any other pull request to the README.md file.
 
 ##### Initial fit checklist

README.md

@@ -74,7 +74,7 @@ The following projects are official OpenJS Foundation projects. If you are inter
 ### OpenJS Collaboration spaces
 
 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_SPACE_PROGRESSION.md)
+support of the OpenJS foundation through a collaboration space, please read our [Collaboration Space Progression](./collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md)
 
 * There are currently no collaboration spaces.
 
@@ -90,7 +90,7 @@ CPC members should attend as many meetings as possible, and non-members are welc
 
 #### Impact Project Representatives
 
-Each Impact Project may appoint 2 representatives to the CPC as outlined in the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#voting-members)
+Each Impact Project may appoint 2 representatives to the CPC as outlined in the [CPC Charter](./CPC-CHARTER.md#voting-members)
 
 - **Appium**: Isaac Murchie ([@imurchie](https://github.com/imurchie), Sauce Labs) & Jonah Stiennon([@Jonahss](https://github.com/Jonahss), Origin Labs)
 - **Dojo**: Dylan Schiemann ([@dylans](https://github.com/dylans), Site Pen)
@@ -101,13 +101,13 @@ Each Impact Project may appoint 2 representatives to the CPC as outlined in the
 
 #### At Large Project Representatives
 
-According to the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#voting-members), each of the At Large and Incubating Projects may nominate a candidate to fill one of two voting seats on the CPC which represent this group of projects as a whole. From those nominees, two voting members are chosen via an [election process outlined in the CPC Governance](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#election-process-for-non-impact-voting-cpc-members).
+According to the [CPC Charter](./CPC-CHARTER.md#voting-members), each of the At Large and Incubating Projects may nominate a candidate to fill one of two voting seats on the CPC which represent this group of projects as a whole. From those nominees, two voting members are chosen via an [election process outlined in the CPC Governance](./governance/GOVERNANCE.md#election-process-for-non-impact-voting-cpc-members).
 
 - Eemeli Aro ([@eemeli](https://github.com/eemeli), Mozilla)
 - Tobie Langel ([@tobie](https://github.com/tobie), UnlockOpen)
 
 #### Elected by Regular Members
-According to the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#voting-members), up to two regular
+According to the [CPC Charter](./CPC-CHARTER.md#voting-members), up to two regular
 members can be elected as voting members. The two regular members elected as voting members are currently:
 
 - Michael Dawson ([@mhdawson](https://github.com/mhdawson), IBM)
@@ -118,7 +118,7 @@ Members of the Collaboration spaces at the `Core` stage may nominate a candiate
 
 ### Regular Members
 
-Anyone who has been active in the foundation or one of its member projects, as described in the [CPC Governance](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#approving-and-onboarding-regular-members) may request to become a regular member by opening a PR to add themselves to the list of regular members. Outgoing Voting members automatically become Regular members, although they must remain active to retain their status.
+Anyone who has been active in the foundation or one of its member projects, as described in the [CPC Governance](./governance/GOVERNANCE.md#approving-and-onboarding-regular-members) may request to become a regular member by opening a PR to add themselves to the list of regular members. Outgoing Voting members automatically become Regular members, although they must remain active to retain their status.
 
 - Abraham Jr Agiri ([@codeekage](https://github.com/codeekage))
 - Antón Molleda ([@molant](https://github.com/molant))
@@ -152,8 +152,8 @@ Observers are free to attend meetings and participate in the work of the CPC as
 as the consensus seeking process. Observers are encouraged to participate and
 volunteer but should refrain from disrupting or blocking progress. Observers
 are expected to participate in a positive and collaborative manner as well as
-following the [code of conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md)
-and [member expectations](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/MEMBER_EXPECTATIONS.md)
+following the [code of conduct](./CODE_OF_CONDUCT.md)
+and [member expectations](./conduct/MEMBER_EXPECTATIONS.md)
 like other CPC participants. If an Observer fails to meet these expectations they can
 be excluded from future CPC meetings based on a standard CPC motion.
 
@@ -164,25 +164,25 @@ be excluded from future CPC meetings based on a standard CPC motion.
 * [New Project Application Template](NEW_PROJECT_APPLICATION.md) - Template document that should be used by projects that want to apply to the Foundation.
 * [Project Charter Template](PROJECT_CHARTER_TEMPLATE.md) - Template document to be used by new projects to write their charter as part of onboarding.
 * [Project Security Reporting](PROJECT_SECURITY_REPORTING.md) - Describes the requirements for reporting security vulnerabilities.
-* [IP_Policy Guidance](IP_POLICY_GUIDANCE.md) - Outlines the relevant aspects of the Foundation's IP policy to make it easier for new projects to implement them.
+* [IP_Policy Guidance](./governance/IP_POLICY_GUIDANCE.md) - Outlines the relevant aspects of the Foundation's IP policy to make it easier for new projects to implement them.
 
 #### Code of Conduct
 * [Code of Conduct](CODE_OF_CONDUCT.md) - This is the canonical version of the code of conduct adopted by the Foundation and all of its projects.
-* [Foundation Code of Conduct Requirements](FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md) - This describes what projects need to do to properly implement the Foundations's code of conduct.
-* [Handling Code of Conduct Reports and Escalation](HANDLING_CODE_OF_CONDUCT_REPORTS.md) - This explains how projects need to handle code of conduct violations and how, when, and to whom they need to be escalated.
-* [Member Expectations](MEMBER_EXPECTATIONS.md) - Additional behavior expectations of CPC members and project leaders.
+* [Foundation Code of Conduct Requirements](./conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md) - This describes what projects need to do to properly implement the Foundations's code of conduct.
+* [Handling Code of Conduct Reports and Escalation](./conduct/HANDLING_CODE_OF_CONDUCT_REPORTS.md) - This explains how projects need to handle code of conduct violations and how, when, and to whom they need to be escalated.
+* [Member Expectations](./conduct/MEMBER_EXPECTATIONS.md) - Additional behavior expectations of CPC members and project leaders.
 
 #### The CPC itself
 * [CPC Charter](CPC-CHARTER.md) - The CPC's charter describes the CPC's mission as defined in the Bylaws.
-* [OpenJS Cross Project Council Governance](GOVERNANCE.md) - Describes how the CPC operates.
-* [Expectations of the Community Board of Directors Representatives](COMMUNITY_BOARD_SEAT_EXPECTATIONS.md) - Description of the role and responsabilities of the Community Board of Directors Representatives.
+* [OpenJS Cross Project Council Governance](./governance/GOVERNANCE.md) - Describes how the CPC operates.
+* [Expectations of the Community Board of Directors Representatives](./governance/COMMUNITY_BOARD_SEAT_EXPECTATIONS.md) - Description of the role and responsabilities of the Community Board of Directors Representatives.
 * [Policy Proposal Process](PROPOSAL_PROCESS.md) - Process by which the CPC creates new policies and processes.
-* [GitHub organization Management Policy](GITHUB_ORG_MANGEMENT_POLICY.md) - Policy for managing the CPC's GitHub organization.
+* [GitHub organization Management Policy](./governance/GITHUB_ORG_MANAGEMENT_POLICY.md) - Policy for managing the CPC's GitHub organization.
 
 #### Collaboration Spaces and Working Groups
-* [Collaboration Network](COLLABORATION_NETWORK.md)
-* [Collaboration Space Progression](COLLABORATION_SPACE_PROGRESSION.md)
-* [Working Groups](WORKING_GROUPS.md)
+* [Collaboration Network](./collaboration-spaces/COLLABORATION_NETWORK.md)
+* [Collaboration Space Progression](./collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md)
+* [Working Groups](./governance/WORKING_GROUPS.md)
 
 #### Other 
 
@@ -212,7 +212,7 @@ Discussion should be held in the open whenever possible.  However, if you need t
 
 OpenJS Foundation projects and their community members are able to take advantage of several services and benefits, including the [Travel Fund Program](./project-resources/MEMBER_TRAVEL_FUND.md). Details can be found in the [/project-resources](./project-resources) directory.
 
-OpenJS Foundation Collaboration spaces are able to take advantage of several services and benefits as outlined in [COLLABORATION_NETWORK.md](COLLABORATION_NETWORK.md).
+OpenJS Foundation Collaboration spaces are able to take advantage of several services and benefits as outlined in [COLLABORATION_NETWORK.md](./collaboration-spaces/COLLABORATION_NETWORK.md).
 
 
 ### Help with project infrastructure

COLLABORATION_NETWORK.md renamed to collaboration-spaces/COLLABORATION_NETWORK.md

@@ -1,6 +1,6 @@
 # The OpenJS Collaboration Network
 
-The formation of the OpenJS Foundation was in support of a number of goals. 
+The formation of the OpenJS Foundation was in support of a number of goals.
 The first was to support JavaScript projects, providing a neutral place for people
 to collaborate and resources needed by those projects
 (legal, marketing, best practices governance support, infra, etc.).
@@ -24,7 +24,7 @@ a particular area.  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 
+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
 independant manner. The work of the space does not necessarily represent the

COLLABORATION_SPACE_PROGRESSION.md renamed to collaboration-spaces/COLLABORATION_SPACE_PROGRESSION.md

@@ -9,12 +9,12 @@ This governance policy describes how a new `Collaboration Space` can be establis
 * `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 ecosytem.
- 
+
 `Collaboration Spaces` may graduate between levels as outlined in this documented. 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.
@@ -57,7 +57,7 @@ The Application Champion is a member of the CPC or Foundation staff who commits
 1. Initial acceptance as an [Incubating] Collaboration Space. Before public announcement there will be:
    * Private email to the CPC members which asks for +1 or objections to the application becoming public. This email will include:
      * The name of the application champion for the application
-     * Completed application 
+     * Completed application
      * Completed Initial-fit checklist.
      * Confirmation that the Foundation Executive Director has received an FYI and there were no objections.
      * Confirmation that there are no existing objections from CPC members.
@@ -79,10 +79,10 @@ The Application Champion is a member of the CPC or Foundation staff who commits
 1. Fit with OpenJS Foundation (not all of these need to be met, but provide different ways of assessing strategic fit).
    1. Impact on JavaScript Community.
    1. How much and how broad of importance is the topic for the JavaScript Community.
-   1. Expected level of activity and progress within the space. 
+   1. Expected level of activity and progress within the space.
    1. Synergy or overlap with existing projects and collaboration spaces in the Foundation.
-   1. Level of comfort that collaboration space will be successful.  
-  
+   1. Level of comfort that collaboration space will be successful.
+
 ## Onboarding Checklist
 
 This is an informational checklist to help start up a collaboration space into the OpenJS Foundation - tasks we will complete together after your proposed collaboration space has been accepted into the incubation process. If you have any questions or need help, the OpenJS Foundation CPC is available to assist.
@@ -105,7 +105,7 @@ At Large collaboration spaces cover topics which the CPC believes are, or have t
 
 At Large collaboration spaces are expected to operate with little support from the CPC and the foundation. They will have access to the following resources:
 
-* A repository under the open-js foundation gihub organization. 
+* A repository under the open-js foundation gihub organization.
 * Support/mentoring from the CPC with respect to setting up appropriate governance.
 * Use of the Foundation Zoom and Youtube streaming
 * A slack channel within the Foundation Slack organization
@@ -114,7 +114,7 @@ At Large collaboration spaces are expected to operate with little support from t
 * 2 re-tweets from the OpenJS Foundation twitter account per month. These will be requested through DM.
 
 An at Large collaboration space must have at least one active 'Space Leader' leading the activities of the space.
-All activities of the collaboration space must conform to the Foundation's Code-of-Conduct and the Space Leader 
+All activities of the collaboration space must conform to the Foundation's Code-of-Conduct and the Space Leader
 must agree to participate in any escalations made to the Foundation Code of Conduct Panel.
 
 #### Acceptance Criteria
@@ -136,7 +136,7 @@ of collaboration and wish to work more closesly with the Cross Project Council a
 #### Expectations
 
 Core collaboration spaces are expected to have regular meetings, activity and demonstrable forward progress in their area of collaboration.
-In addition it should be well documented how the results of the collaboration are benefitting the JavaScript ecosystem, the Foundation projects, or 
+In addition it should be well documented how the results of the collaboration are benefitting the JavaScript ecosystem, the Foundation projects, or
 the activities of other collaboration spaces.
 
 In addition to the resources made available to At large collaboration spaces they will have access to:
@@ -190,6 +190,6 @@ It is expected that incubating collaboration spaces will make an active effort t
 
 ## IV. Annual Review Process
 
-The CPC shall develop an annual review process to determine whether projects are in the stage that accurately reflects their needs and goals. 
+The CPC shall develop an annual review process to determine whether projects are in the stage that accurately reflects their needs and goals.
 
 [Incubating]: #incubating

NEW_COLLABORATION_SPACE_APPLICATION.md renamed to collaboration-spaces/NEW_COLLABORATION_SPACE_APPLICATION.md

@@ -22,11 +22,11 @@ Why is the proposed area/topic important to the JavaScript Ecosystem?
 
 Which [resources](./COLLABORATION_SPACE_PROGRESSION.md#expectations)
 would the space need from those listed as available to
-Collaboration spaces? 
+Collaboration spaces?
 
 ## Existing assets
 
-Are there an existing assets, documentation etc. that would be transferred into 
+Are there an existing assets, documentation etc. that would be transferred into
 a Foundation repo upon formation of the Collaboration space?
 
 ## Questions?