From 36f7bbbaae70936e74ecd97decbfccc9f58118fe Mon Sep 17 00:00:00 2001 From: Sendil Kumar N Date: Tue, 23 Feb 2021 19:48:38 +0100 Subject: [PATCH] chore: rename master references to HEAD (#716) * change the main -> HEAD * move some other master references to HEAD --- .../regular-member-pull-request.md | 4 +- CODE_OF_CONDUCT.md | 4 +- CPC-CHARTER.md | 2 +- GOVERNANCE.md | 16 ++-- HANDLING_CODE_OF_CONDUCT_REPORTS.md | 10 +-- IP_POLICY_GUIDANCE.md | 2 +- MEMBER_EXPECTATIONS.md | 2 +- NEW_PROJECT_APPLICATION.md | 4 +- PROJECT_CHARTER_TEMPLATE.md | 26 +++--- PROJECT_PROGRESSION.md | 12 +-- PROJECT_SECURITY_REPORTING.md | 2 +- README.md | 80 +++++++++---------- WORKING_GROUPS.md | 8 +- meetings/2020-09-29.md | 2 +- project-resources/MEMBER_TRAVEL_FUND.md | 8 +- .../COMMUNITY_BOARD_REPRESENTATION/README.md | 2 +- .../NEW_PROJECT_APPLICATION.md | 4 +- .../PROJECT_PROGRESSION.md | 2 +- .../approved/SECURITY_REPORTING/README.md | 2 +- .../CHARTER_REVIEW/charter_review.md | 2 +- transfer-repo-into-org.md | 4 +- 21 files changed, 99 insertions(+), 99 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE/regular-member-pull-request.md b/.github/PULL_REQUEST_TEMPLATE/regular-member-pull-request.md index 44d801e57..7a071c8c9 100644 --- a/.github/PULL_REQUEST_TEMPLATE/regular-member-pull-request.md +++ b/.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) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 473556ea0..09a0b1ed6 100644 --- a/CODE_OF_CONDUCT.md +++ b/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). --- diff --git a/CPC-CHARTER.md b/CPC-CHARTER.md index 47b38ed61..fd1e34384 100644 --- a/CPC-CHARTER.md +++ b/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/ diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 87e994681..d739e2c41 100644 --- a/GOVERNANCE.md +++ b/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 diff --git a/HANDLING_CODE_OF_CONDUCT_REPORTS.md b/HANDLING_CODE_OF_CONDUCT_REPORTS.md index cbc0b425e..865b9b1e8 100644 --- a/HANDLING_CODE_OF_CONDUCT_REPORTS.md +++ b/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,7 +43,7 @@ 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. @@ -51,7 +51,7 @@ All members of the CPC are subscribed to the `report@openjsf.org` mailing list. 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. diff --git a/IP_POLICY_GUIDANCE.md b/IP_POLICY_GUIDANCE.md index 477c78f8c..dffb617c5 100644 --- a/IP_POLICY_GUIDANCE.md +++ b/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 diff --git a/MEMBER_EXPECTATIONS.md b/MEMBER_EXPECTATIONS.md index 28edc1e69..e9a749684 100644 --- a/MEMBER_EXPECTATIONS.md +++ b/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 diff --git a/NEW_PROJECT_APPLICATION.md b/NEW_PROJECT_APPLICATION.md index be221c754..6dfc49ca3 100644 --- a/NEW_PROJECT_APPLICATION.md +++ b/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 diff --git a/PROJECT_CHARTER_TEMPLATE.md b/PROJECT_CHARTER_TEMPLATE.md index e49ece570..3ef794386 100644 --- a/PROJECT_CHARTER_TEMPLATE.md +++ b/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,7 +101,7 @@ _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) @@ -109,4 +109,4 @@ _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) diff --git a/PROJECT_PROGRESSION.md b/PROJECT_PROGRESSION.md index f3aa6928c..502b931a3 100644 --- a/PROJECT_PROGRESSION.md +++ b/PROJECT_PROGRESSION.md @@ -103,15 +103,15 @@ This is an informational checklist to help projects onboard into the OpenJS Foun - [ ] Update project CoC reporting methods to include OpenJS Foundation escalation path - [ ] List official domains that the project commits to transfer to the OpenJS Foundation following graduation - [ ] Identify and document other core project infrastructure -- [ ] Adopt either the [Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)](https://github.com/openjs-foundation/cross-project-council/blob/master/IP_POLICY_GUIDANCE.md#4-adopting-the-dco-or-a-cla) +- [ ] Adopt either the [Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/IP_POLICY_GUIDANCE.md#4-adopting-the-dco-or-a-cla) - [ ] Add or Update Governance.md document (required for Impact stage) - [ ] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md) -- [ ] Publish Project Charter on website or GitHub (see [charter template](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_CHARTER_TEMPLATE.md)) -- [ ] Update [legal copyright notice](https://github.com/openjs-foundation/cross-project-council/blob/master/IP_POLICY_GUIDANCE.md#2-copyright-notices) on GitHub +- [ ] Publish Project Charter on website or GitHub (see [charter template](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_CHARTER_TEMPLATE.md)) +- [ ] Update [legal copyright notice](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/IP_POLICY_GUIDANCE.md#2-copyright-notices) on GitHub - [ ] Add [copyright notices for project website footers](https://github.com/openjs-foundation/artwork#copyright-notices-for-project-website-footers) to project website - [ ] Add [OpenJS Foundation logo](https://github.com/openjs-foundation/artwork#openjs-foundation-logos) to project website - [ ] [Add Project logo](https://github.com/openjs-foundation/artwork#preparing-artwork-for-contribution) to OpenJS Foundation website -- [ ] Add Project to the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/master/README.md#incubating-projects) as an Incubating project +- [ ] Add Project to the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/README.md#incubating-projects) as an Incubating project - [ ] List trademarks the project commits to transfer to the OpenJS Foundation following graduation - [ ] If project is using crowdfunding platforms, add disclaimer to platforms - [ ] Identify individuals from the project to join the CPC @@ -119,11 +119,11 @@ This is an informational checklist to help projects onboard into the OpenJS Foun * marketing & social media * infrastructure * legal/governance help -- [ ] Publish security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_SECURITY_REPORTING.md)) +- [ ] Publish security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_SECURITY_REPORTING.md)) ## Post-graduation Checklist - + This is a checklist to help projects complete the post-graduation tasks they committed to during onboarding - tasks we will complete together after your project has graduated from the incubation process. If you have any questions or need help, the OpenJS Foundation CPC is available to assist. diff --git a/PROJECT_SECURITY_REPORTING.md b/PROJECT_SECURITY_REPORTING.md index a7a85c917..aeba345f3 100644 --- a/PROJECT_SECURITY_REPORTING.md +++ b/PROJECT_SECURITY_REPORTING.md @@ -6,7 +6,7 @@ Each OpenJS Foundation project must publish a security policy in an easily acces Projects that have their own organization on GitHub are advised to place the `SECURITY.md` file in the `.github` repository for the organization. -The [Node.js Ecosystem Security WG Template](https://github.com/nodejs/security-wg/blob/master/processes/responsible_disclosure_template.md) can be used by projects that do not have their own security reporting infrastructure. +The [Node.js Ecosystem Security WG Template](https://github.com/nodejs/security-wg/blob/HEAD/processes/responsible_disclosure_template.md) can be used by projects that do not have their own security reporting infrastructure. ## Reporting diff --git a/README.md b/README.md index 323c3c4fd..97eb9a952 100644 --- a/README.md +++ b/README.md @@ -16,64 +16,64 @@ The following projects are official OpenJS Foundation projects. If you are inter | | Project | Charter | Contributing | Code of Conduct | |-|----------------|:-----------------:|:------------------:|:---------------------:| -| logo of project Appium | [Appium](https://appium.io/) | | [Contributing Guide](https://github.com/appium/appium/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/appium/appium/blob/master/CONDUCT.md) | -| logo of project Dojo | [Dojo](https://dojo.io/) | | [Contributing Guide](https://github.com/dojo/framework/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/dojo/framework/blob/master/CODE_OF_CONDUCT.md) | -| logo of project Electron | [Electron](https://electronjs.org) | | [Contributing Guide](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) | -| logo of project jQuery | [jQuery](https://jquery.com/) | | [Contributing Guide](https://github.com/jquery/jquery/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project Node.js | [Node.js](https://nodejs.org) | | [Contributing Guide](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/nodejs/node/blob/master/doc/guides/contributing/code-of-conduct.md) | -| logo of project webpack | [webpack](https://webpack.js.org/) | | [Contributing Guide](https://github.com/webpack/webpack/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/webpack/webpack/blob/master/CODE_OF_CONDUCT.md) | +| logo of project Appium | [Appium](https://appium.io/) | | [Contributing Guide](https://github.com/appium/appium/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/appium/appium/blob/HEAD/CONDUCT.md) | +| logo of project Dojo | [Dojo](https://dojo.io/) | | [Contributing Guide](https://github.com/dojo/framework/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/dojo/framework/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project Electron | [Electron](https://electronjs.org) | | [Contributing Guide](https://github.com/electron/electron/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/electron/electron/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project jQuery | [jQuery](https://jquery.com/) | | [Contributing Guide](https://github.com/jquery/jquery/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project Node.js | [Node.js](https://nodejs.org) | | [Contributing Guide](https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/nodejs/node/blob/HEAD/doc/guides/contributing/code-of-conduct.md) | +| logo of project webpack | [webpack](https://webpack.js.org/) | | [Contributing Guide](https://github.com/webpack/webpack/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/webpack/webpack/blob/HEAD/CODE_OF_CONDUCT.md) | #### Growth Projects | | Project | Charter | Contributing | Code of Conduct | |-|----------------|:-----------------:|:------------------:|:---------------------:| -| logo of AMP project | [AMP](https://amp.dev/) | | [Contributing Guide](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/ampproject/meta/blob/master/CODE_OF_CONDUCT.md) | -| logo of project architect | [architect](https://arc.codes/) | | [Contributing Guide](https://github.com/architect/architect/blob/master/.github/contributing.md) | [Code of Conduct](https://github.com/architect/architect/blob/master/.github/code_of_conduct.md) | -| logo of project Fastify | [Fastify](https://fastify.io) | | [Contributing Guide](https://github.com/fastify/fastify/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/fastify/fastify/blob/master/CODE_OF_CONDUCT.md) | -| logo of project Intern | [Intern](https://theintern.github.io/) | | [Contributing Guide](https://github.com/theintern/intern/blob/master/CONTRIBUTING.md) | | -| logo of project Mocha | [Mocha](https://mochajs.org/) | | [Contributing Guide](https://github.com/mochajs/mocha/blob/master/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/mochajs/mocha/blob/master/.github/CODE_OF_CONDUCT.md) | +| logo of AMP project | [AMP](https://amp.dev/) | | [Contributing Guide](https://github.com/ampproject/amphtml/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/ampproject/meta/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project architect | [architect](https://arc.codes/) | | [Contributing Guide](https://github.com/architect/architect/blob/HEAD/.github/contributing.md) | [Code of Conduct](https://github.com/architect/architect/blob/HEAD/.github/code_of_conduct.md) | +| logo of project Fastify | [Fastify](https://fastify.io) | | [Contributing Guide](https://github.com/fastify/fastify/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/fastify/fastify/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project Intern | [Intern](https://theintern.github.io/) | | [Contributing Guide](https://github.com/theintern/intern/blob/HEAD/CONTRIBUTING.md) | | +| logo of project Mocha | [Mocha](https://mochajs.org/) | | [Contributing Guide](https://github.com/mochajs/mocha/blob/HEAD/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/mochajs/mocha/blob/HEAD/.github/CODE_OF_CONDUCT.md) | | logo of project Node-RED | [Node-RED](https://nodered.org/) | | [Contributing Guide](https://nodered.org/about/contribute/) | [Code of Conduct](https://nodered.org/about/conduct/) | -| logo of project WebdriverIO | [WebdriverIO](https://webdriver.io/) | | [Contributing Guide](https://github.com/webdriverio/webdriverio/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/webdriverio/webdriverio/blob/master/CODE_OF_CONDUCT.md) | -| logo of project webhint | [webhint](https://webhint.io/) | | [Contributing Guide](https://github.com/webhintio/hint/blob/main/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | +| logo of project WebdriverIO | [WebdriverIO](https://webdriver.io/) | | [Contributing Guide](https://github.com/webdriverio/webdriverio/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/webdriverio/webdriverio/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project webhint | [webhint](https://webhint.io/) | | [Contributing Guide](https://github.com/webhintio/hint/blob/HEAD/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | #### At-Large Projects | | Project | Charter | Contributing | Code of Conduct | |-|----------------|:-----------------:|:------------------:|:---------------------:| -| logo of project ESLint | [ESLint](https://eslint.org/) | | [Contributing Guide](https://github.com/eslint/eslint/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://eslint.org/conduct) | -| logo of project Esprima | [Esprima](https://esprima.org/) | | [Contributing Guide](https://github.com/jquery/esprima/blob/master/CONTRIBUTING.md) | | -| logo of project Express | [Express](https://expressjs.com/) | | [Contributing Guide](https://expressjs.com/en/resources/contributing.html) | [Code of Conduct](https://github.com/expressjs/express/blob/master/Code-Of-Conduct.md) | -| logo of project Globalize | [Globalize](https://github.com/jquery/globalize) | | [Contributing Guide](https://github.com/globalizejs/globalize/blob/master/CONTRIBUTING.md) | | -| logo of project Grunt | [Grunt](https://gruntjs.com/) | | [Contributing Guide](https://github.com/gruntjs/grunt/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/gruntjs/grunt/blob/master/CODE_OF_CONDUCT.md) | -| logo of project HospitalRun | [HospitalRun](https://hospitalrun.io/) | | [Contributing Guide](https://github.com/HospitalRun/hospitalrun/blob/master/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/HospitalRun/hospitalrun/blob/master/.github/CODE_OF_CONDUCT.md) | -| logo of project Interledger.js | [Interledger.js](https://interledger.org/) | | [Contributing Guide](https://github.com/interledger/rfcs/blob/master/CONTRIBUTING.md) | | -| logo of project JerryScript | [JerryScript](https://jerryscript.net/) | | [Contributing Guide](https://github.com/jerryscript-project/jerryscript/blob/master/CONTRIBUTING.md) | | +| logo of project ESLint | [ESLint](https://eslint.org/) | | [Contributing Guide](https://github.com/eslint/eslint/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://eslint.org/conduct) | +| logo of project Esprima | [Esprima](https://esprima.org/) | | [Contributing Guide](https://github.com/jquery/esprima/blob/HEAD/CONTRIBUTING.md) | | +| logo of project Express | [Express](https://expressjs.com/) | | [Contributing Guide](https://expressjs.com/en/resources/contributing.html) | [Code of Conduct](https://github.com/expressjs/express/blob/HEAD/Code-Of-Conduct.md) | +| logo of project Globalize | [Globalize](https://github.com/jquery/globalize) | | [Contributing Guide](https://github.com/globalizejs/globalize/blob/HEAD/CONTRIBUTING.md) | | +| logo of project Grunt | [Grunt](https://gruntjs.com/) | | [Contributing Guide](https://github.com/gruntjs/grunt/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/gruntjs/grunt/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project HospitalRun | [HospitalRun](https://hospitalrun.io/) | | [Contributing Guide](https://github.com/HospitalRun/hospitalrun/blob/HEAD/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/HospitalRun/hospitalrun/blob/HEAD/.github/CODE_OF_CONDUCT.md) | +| logo of project Interledger.js | [Interledger.js](https://interledger.org/) | | [Contributing Guide](https://github.com/interledger/rfcs/blob/HEAD/CONTRIBUTING.md) | | +| logo of project JerryScript | [JerryScript](https://jerryscript.net/) | | [Contributing Guide](https://github.com/jerryscript-project/jerryscript/blob/HEAD/CONTRIBUTING.md) | | | logo of project Libuv | [Libuv](https://libuv.org/) | | [Contributing Guide](https://github.com/libuv/libuv/blob/v1.x/CONTRIBUTING.md) | | -| logo of project Lodash | [Lodash](https://lodash.com/) | | [Contributing Guide](https://github.com/lodash/lodash/blob/master/.github/CONTRIBUTING.md) | | -| logo of project Marko | [Marko](https://markojs.com/) | | [Contributing Guide](https://github.com/marko-js/marko/blob/master/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/marko-js/marko/blob/master/.github/CODE_OF_CONDUCT.md) | -| logo of project messageformat | [messageformat](https://messageformat.github.io/messageformat/) | | [Contributing Guide](https://github.com/messageformat/messageformat/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | +| logo of project Lodash | [Lodash](https://lodash.com/) | | [Contributing Guide](https://github.com/lodash/lodash/blob/HEAD/.github/CONTRIBUTING.md) | | +| logo of project Marko | [Marko](https://markojs.com/) | | [Contributing Guide](https://github.com/marko-js/marko/blob/HEAD/.github/CONTRIBUTING.md) | [Code of Conduct](https://github.com/marko-js/marko/blob/HEAD/.github/CODE_OF_CONDUCT.md) | +| logo of project messageformat | [messageformat](https://messageformat.github.io/messageformat/) | | [Contributing Guide](https://github.com/messageformat/messageformat/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | | logo of project Moment | [Moment](https://momentjs.com/) | | [Contributing Guide](https://github.com/moment/moment/blob/develop/CONTRIBUTING.md) | | -| logo of project PEP | [PEP](https://github.com/jquery/pep) | | [Contributing Guide](https://github.com/jquery/PEP/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project QUnit | [QUnit](https://qunitjs.com/) | | [Contributing Guide](https://github.com/qunitjs/qunit/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/qunitjs/qunit/blob/master/CODE_OF_CONDUCT.md) | +| logo of project PEP | [PEP](https://github.com/jquery/pep) | | [Contributing Guide](https://github.com/jquery/PEP/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project QUnit | [QUnit](https://qunitjs.com/) | | [Contributing Guide](https://github.com/qunitjs/qunit/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/qunitjs/qunit/blob/HEAD/CODE_OF_CONDUCT.md) | #### Emeritus Projects | | Project | Charter | Contributing | Code of Conduct | |-|----------------|:-----------------:|:------------------:|:---------------------:| -| logo of project Chassis | [Chassis](https://github.com/jquery/css-chassis) | | [Contributing Guide](https://github.com/jquery/css-chassis/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project jQuery Mobile | [jQuery Mobile](https://jquerymobile.com/) | | [Contributing Guide](https://github.com/jquery/jquery-mobile/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project jQuery UI | [jQuery UI](https://jqueryui.com/) | | [Contributing Guide](https://github.com/jquery/jquery-ui/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project RequireJS | [RequireJS](https://requirejs.org/) | | [Contributing Guide](https://requirejs.org/docs/contributing.html) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | -| logo of project Sizzle | [Sizzle](https://sizzlejs.com/) | | [Contributing Guide](https://github.com/jquery/sizzle/blob/master/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) | +| logo of project Chassis | [Chassis](https://github.com/jquery/css-chassis) | | [Contributing Guide](https://github.com/jquery/css-chassis/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project jQuery Mobile | [jQuery Mobile](https://jquerymobile.com/) | | [Contributing Guide](https://github.com/jquery/jquery-mobile/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project jQuery UI | [jQuery UI](https://jqueryui.com/) | | [Contributing Guide](https://github.com/jquery/jquery-ui/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project RequireJS | [RequireJS](https://requirejs.org/) | | [Contributing Guide](https://requirejs.org/docs/contributing.html) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project Sizzle | [Sizzle](https://sizzlejs.com/) | | [Contributing Guide](https://github.com/jquery/sizzle/blob/HEAD/CONTRIBUTING.md) | [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) | #### Incubating Projects | | Project | Charter | Contributing | Code of Conduct | |-|----------------|:-----------------:|:------------------:|:---------------------:| -| logo of project ajv | [Ajv](https://ajv.js.org/) | | [Contributing Guide](https://ajv.js.org/contribute.html) | [Code of Conduct](https://github.com/ajv-validator/ajv/blob/master/CODE_OF_CONDUCT.md) | -| logo of project NativeScript | [NativeScript](https://nativescript.org/) | | [Contributing Guide](https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md) | [Code of Conduct](https://github.com/NativeScript/codeofconduct) | -| logo of project nvm | [nvm](http://nvm.sh/) | | [Contributing Guide](https://github.com/nvm-sh/nvm/blob/master/CONTRIBUTING.md) | | +| logo of project ajv | [Ajv](https://ajv.js.org/) | | [Contributing Guide](https://ajv.js.org/contribute.html) | [Code of Conduct](https://github.com/ajv-validator/ajv/blob/HEAD/CODE_OF_CONDUCT.md) | +| logo of project NativeScript | [NativeScript](https://nativescript.org/) | | [Contributing Guide](https://github.com/NativeScript/NativeScript/blob/HEAD/tools/notes/CONTRIBUTING.md) | [Code of Conduct](https://github.com/NativeScript/codeofconduct) | +| logo of project nvm | [nvm](http://nvm.sh/) | | [Contributing Guide](https://github.com/nvm-sh/nvm/blob/HEAD/CONTRIBUTING.md) | | ### OpenJS Collaboration spaces @@ -95,7 +95,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/master/CPC-CHARTER.md#voting-members) +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) - **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) @@ -106,13 +106,13 @@ Each Impact Project may appoint 2 representatives to the CPC as outlined in the #### Growth & At Large Project Representatives -According to the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#voting-members), each of the Growth, 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/master/GOVERNANCE.md#election-process-for-non-impact-voting-cpc-members). +According to the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md#voting-members), each of the Growth, 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). - Christopher Hiller ([@boneskull](https://github.com/boneskull), IBM) - 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/master/CPC-CHARTER.md#voting-members), up to two regular +According to the [CPC Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/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: - Eemeli Aro ([@eemeli](https://github.com/eemeli), Vincit) @@ -124,7 +124,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/master/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](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. - Abraham Jr Agiri ([@codeekage](https://github.com/codeekage)) - Antón Molleda ([@molant](https://github.com/molant)) @@ -156,8 +156,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/master/CODE_OF_CONDUCT.md) -and [member expectations](https://github.com/openjs-foundation/cross-project-council/blob/master/MEMBER_EXPECTATIONS.md) +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) 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. diff --git a/WORKING_GROUPS.md b/WORKING_GROUPS.md index ad719440e..1cd9a08ee 100644 --- a/WORKING_GROUPS.md +++ b/WORKING_GROUPS.md @@ -123,8 +123,8 @@ The [OpenJS Moderation Policy][] applies to this Working Group. Moderation Polic The [OpenJS Code of Conduct][] applies to this Working Group. -[OpenJS Code of Conduct]: https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md -[OpenJS Moderation Policy]: https://github.com/openjs-foundation/cross-project-council/blob/master/Moderation-Policy.md +[OpenJS Code of Conduct]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md +[OpenJS Moderation Policy]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/Moderation-Policy.md ``` ## Current Working Groups @@ -139,7 +139,7 @@ The purpose of the Code of Conduct Working Group is to define and maintain a set Responsibilities include: * Define and maintain overarching Code of Conduct and moderation processes, documentation and resources as they pertain to the Foundation and the Cross Project Council. -* Provide guidance/resources to implement the minimum Code of Conduct and moderation requirements for projects as part of Foundation membership as defined in the [Foundation Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/master/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md). +* Provide guidance/resources to implement the minimum Code of Conduct and moderation requirements for projects as part of Foundation membership as defined in the [Foundation Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md). * Define and maintain template Code of Conduct and moderation processes and documentation as resources for the Foundation’s projects to use in whole or as guidance to develop their own processes, documentation, and resources, including training materials * Define and maintain Code of Conduct and moderation processes on handling violations within Foundation and its teams and groups (excluding Foundation projects). * Define and maintain Code of Conduct and moderation processes on handling escalations from Foundation projects, including communication @@ -159,7 +159,7 @@ Responsibilities include: * 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/master/MEMBER_EXPECTATIONS.md) +* 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 [Cross Project Council (CPC)]: ./CPC-CHARTER.md diff --git a/meetings/2020-09-29.md b/meetings/2020-09-29.md index bd92e6c2d..92efdf2a9 100644 --- a/meetings/2020-09-29.md +++ b/meetings/2020-09-29.md @@ -45,7 +45,7 @@ * No license in the repo right now? * Possibly MIT but unclear. * Can we relicense CC? - * MIT is OK for documentation (see https://github.com/openjs-foundation/cross-project-council/blob/master/IP_POLICY_GUIDANCE.md#1-licensing + * MIT is OK for documentation (see https://github.com/openjs-foundation/cross-project-council/blob/HEAD/IP_POLICY_GUIDANCE.md#1-licensing * There’s a license in the repo, so we are all set. Closing. * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) diff --git a/project-resources/MEMBER_TRAVEL_FUND.md b/project-resources/MEMBER_TRAVEL_FUND.md index a2f616487..bcd2d7a1d 100644 --- a/project-resources/MEMBER_TRAVEL_FUND.md +++ b/project-resources/MEMBER_TRAVEL_FUND.md @@ -5,9 +5,9 @@ To establish and administer a fund for members of the OpenJS Foundation to travel and spread knowledge about and support the Javascript ecosystem and the Foundation. -### [Current Year Fund](https://github.com/openjs-foundation/cross-project-council/blob/master/TRAVEL_FUND/2020.md) +### [Current Year Fund](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/TRAVEL_FUND/2020.md) -### [2019 funds](https://github.com/openjs-foundation/cross-project-council/blob/master/TRAVEL_FUND/Achived_Travel_Fund_Records/2019.md) +### [2019 funds](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/TRAVEL_FUND/Achived_Travel_Fund_Records/2019.md) ## Requirements @@ -36,11 +36,11 @@ a visa at least 6 months prior to an event. ### For Industry Events If you need a visa for the country in which the OpenJS Foundation event you are -attending is being held, [see the document on preparing for a visa application](https://github.com/openjs-foundation/cross-project-council/blob/master/TRAVEL_FUND/travel-visas.md). +attending is being held, [see the document on preparing for a visa application](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/TRAVEL_FUND/travel-visas.md). ### What The Foundation Can Do To Help: -The Foundation [provides guidance on preparing your visa application](https://github.com/openjs-foundation/cross-project-council/blob/master/TRAVEL_FUND/travel-visas.md), +The Foundation [provides guidance on preparing your visa application](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/TRAVEL_FUND/travel-visas.md), including information on visa processing times and a checklist of items that a visa application could require. diff --git a/proposals/approved/COMMUNITY_BOARD_REPRESENTATION/README.md b/proposals/approved/COMMUNITY_BOARD_REPRESENTATION/README.md index e81e642ab..0f580e437 100644 --- a/proposals/approved/COMMUNITY_BOARD_REPRESENTATION/README.md +++ b/proposals/approved/COMMUNITY_BOARD_REPRESENTATION/README.md @@ -15,7 +15,7 @@ Currently the Node.js foundation has up to 3 community board seats: * 1 board seat for Community Committee * 1 board seat for Individual Membership Program -There are some limitations on these seats as noted in [Section 4.3](https://github.com/nodejs/board/blob/master/by-laws.md#section-43-nomination-election-and-term-of-office-of-directors), +There are some limitations on these seats as noted in [Section 4.3](https://github.com/nodejs/board/blob/HEAD/by-laws.md#section-43-nomination-election-and-term-of-office-of-directors), specifically that: 4.3 d) There must be 3 platinum directors for the individual membership theo elect a board member diff --git a/proposals/approved/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md b/proposals/approved/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md index b99a995b3..36693d290 100644 --- a/proposals/approved/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md +++ b/proposals/approved/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md @@ -10,7 +10,7 @@ A rough description of the project in 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. ## List of all repos that are part of the project @@ -35,7 +35,7 @@ For each repository, please provide: ## 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 diff --git a/proposals/approved/PROJECT_PROGRESSION/PROJECT_PROGRESSION.md b/proposals/approved/PROJECT_PROGRESSION/PROJECT_PROGRESSION.md index c9d85b9c4..282fe6c72 100644 --- a/proposals/approved/PROJECT_PROGRESSION/PROJECT_PROGRESSION.md +++ b/proposals/approved/PROJECT_PROGRESSION/PROJECT_PROGRESSION.md @@ -5,7 +5,7 @@ Project progression - movement from one stage to another - allows projects to pa For more information about how your project can benefit from Foundation membership and services, please see [TBD Document](). -This proposal has been modified from the [CNCF process documentation](https://github.com/cncf/toc/tree/master/process). +This proposal has been modified from the [CNCF process documentation](https://github.com/cncf/toc/tree/HEAD/process). ## II. Project Proposal Process diff --git a/proposals/approved/SECURITY_REPORTING/README.md b/proposals/approved/SECURITY_REPORTING/README.md index c0bccac75..32d3d823d 100644 --- a/proposals/approved/SECURITY_REPORTING/README.md +++ b/proposals/approved/SECURITY_REPORTING/README.md @@ -11,7 +11,7 @@ Currently OpenJS Foundation projects do not have consistently documented standar See also: - [Security reporting in OpenJS Foundation projects](https://gist.github.com/MarcinHoppe/b13a870770522c31a8386ada48b2e40f) -- [Guidelines for responsible reporting and disclosure of security vulnerabilities](https://github.com/nodejs/package-maintenance/blob/master/docs/drafts/security-guidelines.md) +- [Guidelines for responsible reporting and disclosure of security vulnerabilities](https://github.com/nodejs/package-maintenance/blob/HEAD/docs/drafts/security-guidelines.md) ## Required Resources diff --git a/proposals/incubating/CHARTER_REVIEW/charter_review.md b/proposals/incubating/CHARTER_REVIEW/charter_review.md index f09aca82e..b3b754a29 100644 --- a/proposals/incubating/CHARTER_REVIEW/charter_review.md +++ b/proposals/incubating/CHARTER_REVIEW/charter_review.md @@ -44,4 +44,4 @@ CPC members should add themselves as reviewers to the associated charter issue. Project Charters should be reviewed and approved within two weeks of submission. An exception may be made if the charter is submitted during a holiday period (such as the end of the year) or in the event either the project or CPC has requested legal review. -Charters are approved when they meet the requirements outlined in the 'Approving Charters' section of [GOVERNANCE.md](https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#approving-project-charters). +Charters are approved when they meet the requirements outlined in the 'Approving Charters' section of [GOVERNANCE.md](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md#approving-project-charters). diff --git a/transfer-repo-into-org.md b/transfer-repo-into-org.md index 729f9f1ad..2dbecd07f 100644 --- a/transfer-repo-into-org.md +++ b/transfer-repo-into-org.md @@ -5,7 +5,7 @@ Ideally, the repository should have the following documents in place: - `CODE_OF_CONDUCT.md`: it can be a reference to - [the OpenJS Foundation's Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md). + [the OpenJS Foundation's Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md). - `CONTRIBUTING.md`: if there isn't one already, [the contributing guide][] of Node.js core could be a good example. Consider including the Developer's Certificate of Origin section in the document to avoid potential copyright @@ -41,6 +41,6 @@ See [GitHub's documentation on transferring repos][] on how to perform the neces [GitHub's documentation on transferring repos]: https://help.github.com/articles/about-repository-transfers/ -[OpenJS Foundation GitHub Organization Management Policy]: https://github.com/openjs-foundation/cross-project-council/blob/master/GITHUB_ORG_MANGEMENT_POLICY.md +[OpenJS Foundation GitHub Organization Management Policy]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GITHUB_ORG_MANGEMENT_POLICY.md [the contributing guide]: ./CONTRIBUTING.md [the issue tracker of the Cross Project Council repository]: https://github.com/openjs-foundation/cross-project-council/issues