[ONBOARDING] Perspective to OpenJS

This issue tracks all the tasks needed to fully onboard the Perspective project to OpenJS.

• #3069
• [Perspective - Onboarding] Update project CoC reporting methods to include OpenJS Foundation escalation path
• [Perspective - Onboarding] List official domains that the project commits to transfer to the OpenJS Foundation following graduation
• [Perspective - Onboarding] Identify and document other core project infrastructure
• [Perspective - Onboarding] Adopt either the Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)
• [Perspective - Onboarding] Add or Update Governance.md document (required for Impact stage)
• [Perspective - Onboarding] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
• [Perspective - Onboarding] Publish Project Charter on website or GitHub (see charter template)
• [Perspective - Onboarding] Update legal copyright notice on GitHub
• [Perspective - Onboarding] Add copyright notices for project website footers to project website
• [Perspective - Onboarding] Add OpenJS Foundation logo to project website
• [Perspective - Onboarding] Add Project logo to OpenJS Foundation website
• [Perspective - Onboarding] Add Project to the CPC repo's README.md as an Incubating project
• [Perspective - Onboarding] List trademarks the project commits to transfer to the OpenJS Foundation following graduation
• [Perspective - Onboarding] If project is using crowdfunding platforms, add disclaimer from the OpenJS Foundation Trademark Policy to platforms
• [Perspective - Onboarding] Identify individuals from the project to join the CPC by opening an issue in the CPC repository
• [Perspective - Onboarding] Document project and foundation contacts for:
• [Perspective - Onboarding] Publish security policy (see PROJECT_SECURITY_REPORTING)
• [Perspective - Onboarding] Work with the foundation to sign a Project Contribution Agreement (if needed)
• [Perspective - Onboarding] Implement an option from the Github Continuity Policy