---
# System prepended metadata

title: Untitled
tags: [OpenJS, ' Onboarding']

---

---
tags: OpenJS, Onboarding
---

## Project Onboarding Checklist - Mocha

- [ ] Adopt the [OpenJS Foundation Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md) - update the project's Code of Conduct file
  * currently the JSF CoC
  * possibly further define their reporting path
   
//blocking: OJSF doesn't have a defined escalation path
- [ ] Update project CoC reporting methods to include OpenJS Foundation escalation path
  * would be interesting in adopting the OJSF path for project 


- [x] Transfer official domains to OpenJS Foundation
  * mochajs.org - only domain; other services have sub domains
  * May be interested in moving other services over but will need to retain admin access
- [x] Identify and document other core project infrastructure, including hosting, CDNs, CI/CD tooling, etc. If the project anticipates anticipate additional needs, document that as well. 
  * mochajs.org: netlify hosted (free)
  * CI: public travis (free)
  * analytics: matomo (formerly piwik)(free)
  * May have, don't need: Jenkins droplet. 
- [x] If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool
  * Currently uses JSF CLA, may want to switch to DCO
  * May be interested in re-licensing under Apache 2.0
- [ ] Add or Update GOVERNANCE.md document (required for Impact stage); Growth & At Large projects can choose a simpler approach to documenting project leadership and decision-making such as including the info in the README or Contributing.md file.
  * Mocha has a maintainer handbook; there are contributing guidelines to review & possibly update. Have expectations/rights/responsibilities/roles described. file on [/mocha/maintainers.md](https://github.com/mochajs/mocha/blob/master/MAINTAINERS.md)
  * to do: review docs for current info & make sure linked in proper places
- [x] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md, GOVERNANCE.md (impact only))
  * has license(s) (MIT, CC BY 4), readme, and CoC Md

// blocking on the charter template
- [ ] Project Charter is published on website or github

// blocking- waiting on copy from board
- [ ] Update legal copyright notice on project website and github

- [ ] Add OpenJS Foundation logo to project website
  * to do; need svg or whatever img, and any guidance/restrictions on placement

- [x] Add Project logo to OpenJS Foundation website; update PROJECTS.md file
- [ ] Transfer IP and logomark to the OpenJS Foundation
  * double check with Steve  
- [x] List any crowdfunding platforms (such as Open Collective) used by the project. If project is using crowdfunding platforms, add appropriate disclaimer to platforms.
  * Open Collective - disclaimer is on page; Chris updating to say OJSF

// idea: provide some documentation for projects about what to do if this changes
- [x] Identify individuals from the project to join the CPC as Regular or Voting (Impact only) members
  * Chris Hiller

// blocking on where this info should live
- [ ] Document contacts from the project and the foundation for:
  * marketing & social media - Chris
  * infrastructure & technical leadership - Chris
  * legal/governance help - Chris
  * OpenJS communications channels (slack, project mailing lists). Project has a [gitter](https://gitter.im/mochajs/contributors).

