You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
Project Onboarding Checklist - Mocha
Stage: Growth
UPDATED: by @boneskull on Jul 23 2019: formatting
The text was updated successfully, but these errors were encountered: