[ONBOARDING] Jest

[jorydotcom]

Project Onboarding Checklist - Jest

Stage: At Large (post incubation)

• Adopt the OpenJS Foundation Code of Conduct [Docs]: Adopt OpenJS Code Of Conduct jestjs/jest#14899
• Update project CoC reporting methods to include OpenJS Foundation escalation path [Docs]: Adopt OpenJS Code Of Conduct jestjs/jest#14899
• List official domains that the project commits to transfer to the OpenJS Foundation following graduation
• Identify and document other core project infrastructure OpenJS Onboarding: Document Core Infrastructure By Filling Out Google Form  jestjs/jest#14921
• Adopt either the Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)
• 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) OpenJS Onboarding: Create & Publish Project Charter jestjs/jest#14927
• Update legal copyright notice on GitHub Onboarding: Update README.md To Have Copyright jestjs/jest#14922
• Add copyright notices for project website footers to project website [Docs]: Update Footer On Jest Website jestjs/jest#14903
• Add OpenJS Foundation logo to project website [Docs]: Update Footer On Jest Website jestjs/jest#14903
• Add Project logo to OpenJS Foundation website
• Add Project to the CPC repo's README.md 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 from the OpenJS Foundation Trademark Policy to platforms
• Identify individuals from the project to join the CPC by opening an issue in the CPC repository
• Document project and foundation contacts for:
  • marketing & social media
  • infrastructure
  • legal/governance help
• Publish security policy (see PROJECT_SECURITY_REPORTING) OpenJS Onboarding: Publish Security Policy jestjs/jest#14926

[bensternthal]

@tobie & @joesepi I'd like to file a PR against the jest repo with an OpenJS compatible COC policy. I did not find a template for this. Would it be acceptable to use Fastify's as an example and just customize the top section on reporting?

[tobie]

Is Jest planning to opt-in to manage CoC violation reports directly or will this fall to the CoC Team?

We should definitely have better material and clearer instructions for how to adopt the foundation's CoC.

[bensternthal]

Unknown, I asked in the issue. Depending on their answer I can draft a policy based on an existing version. I can use Fastify, or if you have another one you would prefer, let me know.

[bensternthal]

@tobie they will want the COC team to handle these reports.

[tobie]

I like @ljharb's answer in openjs-foundation/cross-project-council#1251 (comment): reference the foundation's CoC (https://code-of-conduct.openjsf.org/) from your CoC file.

[bensternthal]

All items are complete. Closing!