[ONBOARDING] ESLint

[jorydotcom]

Project Onboarding Checklist - ESLint

Stage: At Large

• Adopt the OpenJS Foundation Code of Conduct
  blocked pending CPC & Board Approval, see Add process for handling reports cross-project-council#271
• Update project CoC reporting methods to include OpenJS Foundation escalation path
  blocked pending CPC & Board Approval, see Add process for handling reports cross-project-council#271
• 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

[jorydotcom]

to-do: co-assign @nzakas & anyone else they would like tagged from the project when they accept the team invite

[nzakas]

cc @ivolodin

[nzakas]

Oops, I meant CC @ilyavolodin

[jorydotcom]

I've invited Ilya to the project-leads group as well! thanks Nicholas!

[ilyavolodin]

Hi @jorydotcom I'm coming in late into this discussion. What exactly is necessary for ESLint to do at this point? Most of the items that are currently not blocked are already done as ESLint has been part of JSFoundation prior to merger (so JSFoundation owns domains, copyright and logo for the project). I assume transferring those from JSFoundation to OpenJS Foundation was done as part of the merger, right? We would like to stay with CLA, we are currently using JSFoundation CLA tool, would it be updated to OpenJS Foundation CLA tool, or do we need to add it? Would adding it require everyone to re-sign CLA (that would be a pretty large undertaking, since we have a very large number of committers).

[ilyavolodin]

For all other things:

Identify and document other core project infrastructure

• 2 servers provided and maintained by OpenJS Foundation (were provided as part of JSFoundation) hosted on Digital Ocean (as far as I know) running Jenkins for releases and our bot.
• Site hosting provided by Netlify (free)
• CI/CD with Azure Pipelines (free) and GitHub actions (free)

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

• license - https://github.com/eslint/eslint/blob/master/LICENSE
• Code of conduct - https://github.com/eslint/eslint/blob/master/CODE_OF_CONDUCT.md

If project is using crowdfunding platforms, add disclaimer to platforms

We already have a disclaimer, but based on language provided by JSFoundation. Is there a language for new disclaimer for OpenJS Foundation? https://opencollective.com/eslint

Identify individuals from the project to join the CPC

For now, it will be me. ESLint TSC selected me to handle interactions with Foundation

[jorydotcom]

@ilyavolodin to answer some of your questions:

Most of the items that are currently not blocked are already done as ESLint has been part of JSFoundation prior to merger (so JSFoundation owns domains, copyright and logo for the project). I assume transferring those from JSFoundation to OpenJS Foundation was done as part of the merger, right?

That's right, if they were already transferred to the JS Foundation, OpenJSF has it now as part of the merger. We have included this step for all projects though just as a matter of good hygiene and making sure that we have correct information (that the project's understanding, and the Foundation's understanding of things is the same).

We would like to stay with CLA, we are currently using JSFoundation CLA tool, would it be updated to OpenJS Foundation CLA tool, or do we need to add it? Would adding it require everyone to re-sign CLA (that would be a pretty large undertaking, since we have a very large number of committers).

If you would like to stick with the current CLA solution that is fine. We will be updating the old JSF CLA tool to reflect the merger; we may even be changing CLA tool implementations (from CLA Assistant to something else) but if you are sticking with the Foundation's CLA it should not require re-signing.

I know you and the ESLint team are super busy; I'll try to take care of as much of this as I can for you and reach out with specific instructions on the rest. Thank you Ilya!!