[ONBOARDING] Mocha

[jorydotcom]

Project Onboarding Checklist - Mocha

Stage: Growth

• Update project CoC reporting methods to include OpenJS Foundation escalation path
  • BLOCKING: OpenJSF yet doesn't have a defined escalation path
  • would be interesting in adopting the foundation's CoC path for entire project
• has license(s) (MIT, CC BY 4), readme, and CoC md files on repo
• Project Charter is published on website or github
• Update legal copyright notice on project website and github
  • currently the JSF CoC; need to update to OpenJS Foundation CoC
• 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 in Mocha's MAINTAINERS.md
  • to do: review docs for current info & make sure linked in proper places (@jorydotcom)
• Add OpenJS Foundation logo to project website
  • to do; need svg or whatever img, and any guidance/restrictions on placement
• Transfer IP and logomark to the OpenJS Foundation
  • double check with Steve Ayr (@jorydotcom)
• 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; update to say OpenJS Foundation (@boneskull)
  • IDEA: provide some documentation for projects about what to do if this changes
• 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.
  • QUESTION: Where should we keep this information?
• 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
• 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.
  • QUESTION: Where should we keep this information?
• 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
• Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md, GOVERNANCE.md (impact only))
• Add Project logo to OpenJS Foundation website; update PROJECTS.md file
• Identify individuals from the project to join the CPC as Regular or Voting (Impact only) members
  • Christopher Hiller (@boneskull)

UPDATED: by @boneskull on Jul 23 2019: formatting

[boneskull]

to do; need svg or whatever img, and any guidance/restrictions on placement

Please point me to the relevant info here... we can just grab a logo from the OJSF website and add it to the bottom of our page otherwise.

[boneskull]

@jorydotcom Disclaimer updated on our OC page; please review

[jorydotcom]

Looks good! Thank you @boneskull!

[boneskull]

@jorydotcom

I've ticked off a few of the boxes above. In particular:

• The OpenJSF Logo has been added to our site (but not yet deployed); see add OpenJS Foundation logo to website mochajs/mocha#4008
• Point-of-contact info:
  • Craig Taub (@craigtaub; craigtaub@gmail.com) for social media & marketing-related stuff
  • me for everything else (boneskull@boneskull.com)
• We adopted the OJSF code of conduct; see Adopt the OpenJSF Code of Conduct mochajs/mocha#3971

Everything else, afaik, we're blocked on.

[boneskull]

See mochajs.org for updated copyright notices, etc. (scroll to bottom)

This leaves the "escalation path" thing as the only box unchecked above.

[voxpelli]

Is there anything we who are now maintainers of Mocha still need to do here or we can close this?

[tobie]

Thanks for asking. We've made great progress on the CoC since the last comments on this issue.

You would need to update the CoC to the foundation's latest CoC per the guidelines.

I really like the custom language you have at the top of your CoC, btw. Would you be willing to put in a different file to avoid confusion with the foundation's CoC? Maybe WORKING_TOGETHER.md or something similar?