chore: rename master references to HEAD (#716)

* change the main -> HEAD

* move some other master references to HEAD

.github/PULL_REQUEST_TEMPLATE/regular-member-pull-request.md

@@ -7,11 +7,11 @@ about: You'd like to participate in the Cross Project Council's work as a Regula
 We are thrilled that you'd like to participate in our work in a meaningful way as a Regular Member of the Cross Project Council.
 
 Requirements and rules around becoming a Regular Member can be found in our Governance:
-https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#approving-and-onboarding-regular-members
+https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#approving-and-onboarding-regular-members
 
 Please fill out information below.
 
 Thanks!
 -->
 
-Please describe your recent participation in the work of the foundation or its member projects as described in the [CPC Governance requirements for becoming a Regular Member](https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#approving-and-onboarding-regular-members)
+Please describe your recent participation in the work of the foundation or its member projects as described in the [CPC Governance requirements for becoming a Regular Member](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#approving-and-onboarding-regular-members)

CODE_OF_CONDUCT.md

@@ -45,7 +45,7 @@ For reporting issues in spaces related to a member project, please use the email
 * nvm - 
 * Pep - 
 * QUnit - 
-* Webdriver.io - [contact TSC reps](https://github.com/webdriverio/webdriverio/blob/master/AUTHORS.md)
+* Webdriver.io - [contact TSC reps](https://github.com/webdriverio/webdriverio/blob/HEAD/AUTHORS.md)
 * Webhint - `support@webhint.io`
 * webpack - [redirects here]
 
@@ -63,7 +63,7 @@ The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a founda
 
 
 For more information, refer to the full
-[Code of Conduct governance document](https://github.com/openjs-foundation/bootstrap/blob/master/proposals/stage-2/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md).
+[Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md).
 
 ---
 

CPC-CHARTER.md

@@ -333,5 +333,5 @@ policies.
 [Consensus Seeking]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making
 [Condorcet]: http://en.wikipedia.org/wiki/Condorcet_method
 [Single Transferable Vote]: http://en.wikipedia.org/wiki/Single_transferable_vote
-[Active OpenJS Collaborator]: https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#definition-of-an-active-openjs-collaborator
+[Active OpenJS Collaborator]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#definition-of-an-active-openjs-collaborator
 [OpenJS Foundation bylaws]: https://bylaws.openjsf.org/

GOVERNANCE.md

@@ -233,15 +233,15 @@ The pull request may be fast-tracked if two CPC members approve the fast-trackin
 CPC members may request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt.
 
 [cpc repo]: https://github.com/openjs-foundation/cross-project-council
-[cpc charter]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md
-[cpc charter term]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#voting-members
-[CPC charter section 5]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#section-5-responsibilities-and-expectations-of-the-cpc
+[cpc charter]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md
+[cpc charter term]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#voting-members
+[CPC charter section 5]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#section-5-responsibilities-and-expectations-of-the-cpc
 [cpc regular members team]: https://github.com/orgs/openjs-foundation/teams/cpc-regular-members
 [README]: ./README.md
-[OpenJS Foundation Directory]: https://github.com/openjs-foundation/directory-private/blob/master/cpc-private.md
+[OpenJS Foundation Directory]: https://github.com/openjs-foundation/directory-private/blob/HEAD/cpc-private.md
 [Consensus Seeking]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making
 [Active OpenJS Collaborator]: #definition-of-an-active-openjs-collaborator
-[OpenJS Foundation CPC directory]: https://github.com/openjs-foundation/directory-private/blob/master/groups/cross-project-council.yml
-[Primary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#the-primary-cpc-director-as-defined-in-43d-in-the-openjs-foundation-bylaws
-[Secondary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#the-secondary-cpc-director-as-defined-in-43e-in-theopenjs-foundation-bylaws
-[Tertiary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#the-tertiary-cpc-director-as-defined-in-43f-in-the-openjs-foundation-bylaws
+[OpenJS Foundation CPC directory]: https://github.com/openjs-foundation/directory-private/blob/HEAD/groups/cross-project-council.yml
+[Primary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#the-primary-cpc-director-as-defined-in-43d-in-the-openjs-foundation-bylaws
+[Secondary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#the-secondary-cpc-director-as-defined-in-43e-in-theopenjs-foundation-bylaws
+[Tertiary CPC Director]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#the-tertiary-cpc-director-as-defined-in-43f-in-the-openjs-foundation-bylaws

HANDLING_CODE_OF_CONDUCT_REPORTS.md

@@ -1,7 +1,7 @@
 # Handling reports and escalation
 This document describes the proposed process for handling reports and escalation, along with relevant roles in the OpenJS Foundation.
 
-This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/master/proposals/stage-2/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):
+This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):
 
 * Reports for spaces managed by the Cross Project Council (CPC) which come in through `report@opensjsf.org`
 * Escalations which come in through `coc-escalation@openjsf.org`.   
@@ -17,7 +17,7 @@ reason for reporting to coc-escalation.
 
 ## Code of Conduct
 
-The OpenJS Foundation and its member projects use the Contributor Covenant v2.0 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and esclation procedures.
+The OpenJS Foundation and its member projects use the Contributor Covenant v2.0 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and esclation procedures.
 
 ## Confidentiality and record-keeping
 Personal information is confidential. All reports should be recorded, together with the discussion of it. The following private repos will be used to record and discuss reports.
@@ -43,15 +43,15 @@ All members of the CPC are subscribed to the `report@openjsf.org` mailing list.
      1. Information gathering: Time is allocated to collect information in one place to make sure everyone involved has access.
      1. Information is discussed: The facts are discussed in context of opinions. This can be done in the issue for the report, or in a meeting in which case the key discussion points should then be added to the issue.
      1. An action to be taken is arrived at: The action to be taken is decided by consensus as per the standard CPC
-        [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#section-9-decision-making) process.
+        [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#section-9-decision-making) process.
      1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted. 
      1. Final resolution: the resolution agreed by the CPC members is implemented and the outcome reported to the reporter or target by the main contact.
 
 ## Reports to coc-escalation@openjsf.org
 
 Note: We understand that the reporter and the target can be separate persons. In this case the CPC will communicate with the reporter unless the target gives permission for the CPC to communicate with them.
 
-All members of the [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/master/proposals/stage-2/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel)
+All members of the [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel)
 are subscribed to the coc-escalation@openjsf.org mailing list. The current list of members is documented in ./CODE_OF_CONDUCT_PANEL_MEMERS.md.
 
 When a report is received the following actions will be taken:
@@ -64,7 +64,7 @@ When a report is received the following actions will be taken:
      1. Information gathering: Time is allocated to collect information in one place to make sure all CoCP members have access.
      1. Information is discussed: The facts are discussed in context of opinions. This can be done in the issue for the report, or in a meeting in which case the key discussion points should then be added to the issue.
      1. An action to be taken is arrived at: The action to be taken is decided by consensus as per the standard CPC
-        [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#section-9-decision-making) process substituting in CoCP for references to the CPC.
+        [Decision Making](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#section-9-decision-making) process substituting in CoCP for references to the CPC.
      1. The proposed action is discussed with the leadership for the space to which the report applies (ex CPC or member
         project leadership). If the leadership representatives expresses concerns then the contact person will bring these back to the CoCP members for further discussion.  This cycle can continue until the CoCP members reach consensus that the leadership representatives concerns have been adequately addressed.
      1. Resolution shared: The resolution is shared with the reporter or target by the contact person. If the reporter or target expresses concerns then the contact person will bring these back to the CPC members for further discussion. This cycle can continue until the CPC members reach consensus that the reporter or target's concerns have been adquately addressed. If no feedback is received within 7 days the resolution is considered as accepted. 

IP_POLICY_GUIDANCE.md

@@ -86,7 +86,7 @@ To do so, please [open an issue in the Cross Project Council repository](https:/
 and assign or @-mention [@brianwarner](https://github.com/brianwarner) and 
 [your Project Represenatives](https://github.com/openjs-foundation/cross-project-council#impact-project-representatives) if your are an Impact project,
 the [Growth & At Large Project Representatives](https://github.com/openjs-foundation/cross-project-council#growth--at-large-project-representatives)  if your are a Growth or At Large project,
-or [your Champion](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#application-champion) if you are an Incubating project.
+or [your Champion](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_PROGRESSION.md#application-champion) if you are an Incubating project.
 
 ## Getting help
 

MEMBER_EXPECTATIONS.md

@@ -1,7 +1,7 @@
 All participants in the OpenJS Foundation projects and groups must follow the
 [Code of Conduct](CODE_OF_CONDUCT.md). There are further expectations for
 members of leadership teams including the
-[CPC](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md).
+[CPC](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md).
 
 It is understood that members will have individual opinions and will express
 their individual opinions during discussions within the organization. All

NEW_PROJECT_APPLICATION.md

@@ -15,7 +15,7 @@ Please keep your answer to less than 100 words.
 
 ## Statement of alignment with OpenJS Foundation charter and mission
 
-Please refer to [the Cross Project Council's Charter](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md).
+Please refer to [the Cross Project Council's Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md).
 Please keep your answer to less than 250 words.
 
 ## Impact and users of the project
@@ -26,7 +26,7 @@ Please keep your answer to less than 250 words.
 
 ## Desired Initial Project Phase
 
-Please refer to [Section III, Stages - Definitions & Expectations](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#iii-stages---definitions--expectations) of PROJECT_PROGRESSION.md.
+Please refer to [Section III, Stages - Definitions & Expectations](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_PROGRESSION.md#iii-stages---definitions--expectations) of PROJECT_PROGRESSION.md.
 
 At Large / Growth / Impact
 

PROJECT_CHARTER_TEMPLATE.md

@@ -11,7 +11,7 @@ _OpenJS Foundation's governance._
 _directions: provide a concise, high-level statement about_
 _the project's long-term principles, values, or mission._
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-1-guiding-principle)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-1-guiding-principle)
 
 ## Section 1: Scope
 
@@ -21,7 +21,7 @@ _to a colleague who is familiar with related technical concepts but unfamiliar_
 _with the project. You may also want to describe the project's value to community_
 _and/or business stakeholders._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/master/sig-architecture/charter.md#scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#scope)
 
 ### 1.1: In-scope (optional)
 
@@ -31,7 +31,7 @@ _apparent. This may help differentiate the project from other solutions in the_
 _space. If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/master/sig-architecture/charter.md#in-scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#in-scope)
 
 ### 1.2: Out-of-Scope (optional)
 
@@ -41,14 +41,14 @@ _features, contributions, issues or problems the project is looking for._
 _If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/master/sig-architecture/charter.md#out-of-scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#out-of-scope)
 
 ## Section 2: Relationship with OpenJS Foundation CPC.
 
 _directions: describe how the project intersects with the Cross Project_
 _Council._ 
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-2-evolution-of-openjs-foundation-governance)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-2-evolution-of-openjs-foundation-governance)
 
 ### 2.1 Other Formal Project Relationships (optional)
 
@@ -64,14 +64,14 @@ _the project and its respective organization and repositories. If there are_
 _specific rules for membership or participation in the group, list them here or_
 _by reference to a governance.md document._
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-3-establishment-of-the-tsc)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-3-establishment-of-the-tsc)
 
 ## Section 4: Roles & Responsibilities 
 
 _directions: describe the roles and responsibilities of the ${PROJECT} Governing Body._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/master/sig-architecture/charter.md#roles-and-organization-management)
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-4-responsibilities-of-the-tsc)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-4-responsibilities-of-the-tsc)
 
 ### Section 4.1 Project Operations & Management (optional)
 
@@ -80,8 +80,8 @@ _${PROJECT} Governing Body may be responsible for regarding process or project_
 _operations and management. If you are not using this section, please indicate_
 _your intent with the phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/master/sig-architecture/charter.md#roles-and-organization-management)
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-5-nodejs-project-operations)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-5-nodejs-project-operations)
 
 ### Section 4.2: Decision-making, Voting, and/or Elections (optional)
 
@@ -90,7 +90,7 @@ _or include the information by reference your governance.md document._
 _If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-6-elections)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-6-elections)
 
 ### Section 4.3: Other Project Roles (optional)
 
@@ -101,12 +101,12 @@ _reference to your governance.md document._
 _If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-8-project-roles)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-8-project-roles)
 
 ## Section 5: Definitions (optional)
 
 _directions: include any definitions that may help clarify terms or ideas found_
 _in this charter document. If you are not using this section, please indicate_ 
 _your intent with the phrase, 'Section Intentionally Left Blank'._
 
-ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md#section-9-definitions)
+ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-9-definitions)