Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ONBOARDING] Mocha #27

Open
15 of 16 tasks
jorydotcom opened this issue Jul 19, 2019 · 5 comments
Open
15 of 16 tasks

[ONBOARDING] Mocha #27

jorydotcom opened this issue Jul 19, 2019 · 5 comments
Assignees
Labels
At Large At Large Stage related

Comments

@jorydotcom
Copy link
Member

jorydotcom commented Jul 19, 2019

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
  • Adopt the OpenJS Foundation Code of Conduct - update the project's Code of Conduct file
    • 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
  • 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

UPDATED: by @boneskull on Jul 23 2019: formatting

@boneskull
Copy link

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
Copy link

@jorydotcom Disclaimer updated on our OC page; please review

@jorydotcom
Copy link
Member Author

Looks good! Thank you @boneskull!

@boneskull
Copy link

@jorydotcom

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

Everything else, afaik, we're blocked on.

@jorydotcom jorydotcom transferred this issue from openjs-foundation/cross-project-council Nov 5, 2019
@jorydotcom jorydotcom added this to doing in Project Onboarding Nov 5, 2019
@jorydotcom jorydotcom added the Growth Growth Stage related label Nov 5, 2019
@boneskull
Copy link

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

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

@tobie tobie added At Large At Large Stage related and removed Growth Growth Stage related labels Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
At Large At Large Stage related
Projects
Development

No branches or pull requests

3 participants