OpenJS Onboarding Tasks

[bensternthal]

🚀 Feature Proposal

This issue tracks the completion of the OpenJS onboarding tasks. Tasks are listed below. More information can be found here: https://github.com/openjs-foundation/cross-project-council/blob/main/PROJECT_PROGRESSION.md#onboarding-checklist

• Adopt the OpenJS Foundation Code of Conduct
• 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)
• 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)
• Update legal copyright notice on GitHub
• Add copyright notices for project website footers to project website
• Add OpenJS Foundation logo to project website
• 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
• Document project and foundation contacts for:
• marketing & social media
• infrastructure
• legal/governance help
• Publish security policy (see PROJECT_SECURITY_REPORTING)

[bensternthal]

@SimenB @rickhanlonii for visibility.

[SimenB]

@bensternthal what do we do with copyright notices in source code? E.g.

jest/packages/jest/src/index.ts

Lines 1 to 6 in 8dd30d0

	/**
	* Copyright (c) Meta Platforms, Inc. and affiliates.
	*
	* This source code is licensed under the MIT license found in the
	* LICENSE file in the root directory of this source tree.
	*/

[bensternthal]

@SimenB I think these are generally left alone and as-is. I poked around on node.js to see what they have done, and this looks to be the correct approach.

[SimenB]

Aight 👍 should it be added to new files (we have a script that verifies on CI), or is it fine to omit for those?

[bensternthal]

Excellent question and I am not 100% sure. Adding in @joesepi from the CPC who might know based on experience with other projects.

[bensternthal]

@SimenB would it be helpful for me to spin out the checklist items into individual issues?

[mrazauskas]

@bensternthal By the way, the following seems to be done:

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

[SimenB]

@bensternthal nah, that's fine. I've just been on vacation and started a new job this week, so haven't gotten to this. I'll start tackling the list this weekend 🙂

[bensternthal]

@SimenB ok cool! Let me know if you need help with any of the items.

p.s. congrats on the new job \o/

[SimenB]

@bensternthal Some questions 🙂

For the CoC - do I just copy the linked one into this repo and add Jest and my own email to the project list?

Identify and document other core project infrastructure

We only have a website host (Netlify) and CI (both GH Actions and CircleCI). How would this be documented?

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

Do you have some sort of template for this?

Document project and foundation contacts for:

Where should these be documented?

Publish security policy

We currently rely on the Meta one. Is there a similar one from OpenJS we can use?

Oh, and any news on #14323 (comment)?

---

@rickhanlonii maybe you can help with some of this, if your head is above water after becoming a dad (congrats, again! 😀 )

Specifically

• Publish Project Charter on website or GitHub
• List trademarks the project commits to transfer to the OpenJS Foundation following graduation
• If project is using crowdfunding platforms, …

[tobie]

@SimenB wrt copyright notice, please see Section 2 of the IP Policy Guidance, in particular the italicized note.

In a nutshell, unless you have specific permission to remove existing copyright notices from Meta, don't. Just add the suggested ones below.

[christian-bromann]

We only have a website host (Netlify) and CI (both GH Actions and CircleCI). How would this be documented?

Mentioning it here should suffice.

Do you have some sort of template for this?

I assume Jest never defined any governance policies for the project, which based on the project history makes total sense. For inspiration you can take a look at WebdriverIO which defines different roles and teams and the requirements to become a member of the team to gain more influence to the project. Node.js has a similar structure. As a start you can maybe define the responsibilities of Jest core contributors and define a nomination process to have someone become a Jest core contributor. Then you can adapt and create more complex processes if the project demands it.

Where should these be documented?

This should actually say:

Document project and foundation contacts for:

• marketing & social media
• infrastructure
• legal/governance help

I believe GitHub handles will be sufficient here and can be shared in this thread.

We currently rely on the Meta one. Is there a similar one from OpenJS we can use?

Can you share where the Meta one is defined? I'ld suggest to create a SECURITY.md that can be as simple as the one used by WebdriverIO or a more comprehensive version used by Node.js.

[tobie]

Folks, you also should make sure to back port your updates here to the upstream issue at openjs-foundation/project-status#67 which is the one that the CPC will be looking at.

[bensternthal]

@SimenB would you be OK if we closed this issue. When I created it I was not aware of this already be tracked here openjs-foundation/project-status#67

I'd prefer not to have the lists in two places :)

[bensternthal]

OK going to close this issue so that all discussion and status are in one spot. Again apologies for creating this one, I did not know the other existed!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.