[ONBOARDING] WebdriverIO

[jorydotcom]

Project Onboarding Checklist - WebdriverIO

Stage: Growth

• Adopt the OpenJS Foundation Code of Conduct
• Update project CoC reporting methods to include OpenJS Foundation escalation path
• Transfer official domains to OpenJS Foundation
• Identify and document other core project infrastructure
• If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool
  blocked pending lang from board, See Update/move jsf-clabot for new fdn cross-project-council#124
• Add or Update Governance.md document (required for Impact stage)
• Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
• Project Charter is published on website or github
• Update legal copyright notice on project website and github
  blocked pending lang from board, See Update/move jsf-clabot for new fdn cross-project-council#124
• Add OpenJS Foundation logo to project website
  blocked pending lang from board, See Define & document a style guide for the foundation's name cross-project-council#280
• Add Project logo to OpenJS Foundation website; update PROJECTS.md file
• Transfer logomark to the OpenJS Foundation
• If project is using crowdfunding platforms, add disclaimer to platforms
• Identify individuals from the project to join the CPC
• Document project and foundation contacts for:
  • marketing & social media
  • infrastructure
  • legal/governance help

[christian-bromann]

• Transfer official domains to OpenJS Foundation

The domain is already signed off to the JS Foundation. I believe @brianwarner helped us back then to do that.

• Identify and document other core project infrastructure

The project infrastructure is as follows:

• CI/CD: Travis CI (free)
• Code Coverage: CodeCov (free)
• Dependency Updates: Greenkeeper (free)
• Website Hosting: AWS (S3, Route53 and CloudFront)

• If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool

I would prefer DCO as we see many issues with contributors getting confused with the email they use to commit vs. the one they sign the CLA with.

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

Done: https://github.com/webdriverio/webdriverio/blob/master/GOVERNANCE.md

• Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)

Done:

• https://github.com/webdriverio/webdriverio/blob/master/CODE_OF_CONDUCT.md
• https://github.com/webdriverio/webdriverio/blob/master/LICENSE-MIT

• Project Charter is published on website or github

This is missing and a ticket for it was created here: webdriverio/webdriverio#4699

• Add OpenJS Foundation logo to project website

Done!

• If project is using crowdfunding platforms, add disclaimer to platforms

WebdriverIO is not using any crowdfunding platform.

• Identify individuals from the project to join the CPC

I am happy to join the CPC (even though I already attend these meetings on regular basis if I can). I will follow up with the other WebdriverIO TSC members if they are interested.

I tried to provide input to the points I am able to. With the rest it would be great if we can sit together and walk through them @jorydotcom .

[christian-bromann]

• Project Charter is published on website or github

A PR with such document is proposed and about to land: webdriverio/webdriverio#4699

[christian-bromann]

@jorydotcom I added a CoC escalation path in our code of conduct docs. Is there anything missing on the WebdriverIO side that needs attention or can we close this one up as well?

[christian-bromann]

@jorydotcom is there anything I can do to close this up?