[ONBOARDING] Perspective to OpenJS

[kj-powell]

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

• [Perspective - Onboarding] Adopt the OpenJS Foundation Code of Conduct #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

[texodus]

Thanks for posting the checklist (I've been following along this version also). Let me know how you'd like us to track progress on these.

I was planning on converting the list items which will need PRs into GitHub issues so we can update them individually. Some notes from stuff that is already done, isn't applicable to the project or otherwise won't need a PR/action:

• List official domains that the project commits to transfer to the OpenJS Foundation following graduation.

  List trademarks the project commits to transfer to the OpenJS Foundation following graduation

  Identify and document other core project infrastructure

  There are no domains, trademarks or infrastructure associated with the project.

• Adopt either the Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO).

  Perspective uses a DCO model, documented in the project'sCONTRIBUTING.md and PULL_REQUEST_TEMPLATE.md, and enforced by the GitHub DCO App which prevents unsigned commits from being merge to the protected master branch.

• Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)

  CODE_OF_CONDUCT.md adopted in Move to OpenJS Foundation #3073 language borrowed from deck.gl's example

  LICENCE.md Apache2 which the project has used since the first release.

• If project is using crowdfunding platforms, add disclaimer from the OpenJS Foundation Trademark Policy to platforms

  The project doesn't crowdfund currently and don't plan to do so ever.

[kj-powell]

Thanks for these. I tried to convert the checklist into sub-issues to link to our project board, but I keep getting an error. Not the first time this has happened, but my usual solutions aren't working unfortunately. I'll add these updates to the project board in the OpenJS repo regardless.

[kj-powell]

@texodus how is the progress on this? Is there anything I can help with?

[texodus]

DONE-

• Update project CoC reporting methods to include OpenJS Foundation escalation path

CODE_OF_CONDUCT.md (amended to include OpenJS escalation language).

• Add or Update Governance.md document (required for Impact stage)

GOVERNANCE.md

• Publish Project Charter on website or GitHub (see charter template)

PROJECT_CHARTER.md

• Update legal copyright notice on GitHub

README.md

• Add copyright notices for project website footers to project website

Perspective Project site (see footer)

• Add OpenJS Foundation logo to project website

Perspective Project site (see footer)
README.md (see footer)

• If project is using crowdfunding platforms, add disclaimer from the OpenJS Foundation Trademark Policy to platforms

The project doesn't crowdfund currently and don't plan to do so ever (not changed).

• Document project and foundation contacts for:

GOVERNANCE.md (see maintainers)

• Publish security policy (see PROJECT_SECURITY_REPORTING)

SECUIRTY.md

• Work with the foundation to sign a Project Contribution Agreement (if needed)

Not applicable for this project, this was done when we joined FINOS.

• Implement an option from the Github Continuity Policy

https://github.com/perspective-dev organization has https://github.com/openjs-foundation enterprise owners.

NOT DONE

• Add Project logo to OpenJS Foundation website

We do not have a logo - I've discussed this with @timkpaine, we may run a community vote.

• Add Project to the CPC repo's README.md as an Incubating project

• Identify individuals from the project to join the CPC by opening an issue in the CPC repository