OpenJS Foundation Finish Line

[bnb]

This is an annotated version of the checklist at openjs-foundation/project-status#36, specific to Electron's current state. Once completed, I will respond in that issue with the completed checklist which will then (hopefully!) be passed to the CPC for approval. If completed, I can't foresee any non-trivial roadblocks.

• Adopt the OpenJS Foundation Code of Conduct
  • docs: update code of conduct electron#23137
• Update project CoC reporting methods to include OpenJS Foundation escalation path doesn't need to be done :)
  • note from @bnb: There does not seem to currently be clear and documented guidance on what this is, how to implement it, or what it fully entails from the OpenJS Foundation CPC. There is work being done to improve this, but that work is not completed. One specific point - the ability for CoC rulings to be escalated above and outside of Electron's Community and Safety structure to the CoCP group within the OpenJS Foundation for an "appeal" - is something that Electron would likely want to have feedback on.
• Transfer official domains to OpenJS Foundation #439
  • @groundwater owning working on the Foundation with this.
• Identify and document other core project infrastructure
  • document by @codebytere: https://hackmd.io/@codebytere/rk2-IRPaL
• Add or Update Governance.md document (required for Impact stage)
  • In speaking with @jorydotcom and @brianwarner, it seems that the electron/governance repo is sufficient for this.
• Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
  • Documented in the repositories list: electron/governance
• Project Charter is published on website or github
  • electron/governance/charter/
• Update legal copyright notice on project website and github
  • feat: add OpenJSF copy and logo to footer electronjs.org-old#3895
  • TODO: merge on join
• Add OpenJS Foundation logo to project website
  • feat: add OpenJSF copy and logo to footer electronjs.org-old#3895
  • TODO: merge on join
• Add Project logo to OpenJS Foundation website; update PROJECTS.md file
• If project is using crowdfunding platforms, add disclaimer to platforms
  • About section of the Electron OpenCollective
• Transfer logomark to the OpenJS Foundation #440
  • Need update on this from the Foundation / GitHub.
• Choose DCO or CLA #441
  • Document decision here, if applicable. Is admin the correct team to update on this?
• Identify individuals from the project to join the CPC
  • Admin / WGs to decide upon joining.
• Document project and foundation contacts for:
  • marketing & social media (listed: Outreach WG)
    • @jdalton
    • @ckerr
    • @bnb
    • @cruzerld
    • @felixrieseberg
    • @codebytere
    • @sofianguy
    • @VerteDinde
    • @MarshallOfSound
    • @erickzhao
  • infrastructure (listed: the people I'm aware of who handle infra for Electron, since there's not an apparent Infra WG)
    • @codebytere
    • @MarshallOfSound
    • @jkleinsc
  • legal/governance help (listed: Admin WG)
    • @mgc
    • @groundwater

[jkleinsc]

electron/electron#23137 updates our code of conduct to match the OpenJS foundation.

[bnb]

@jkleinsc added that to the checklist above. Also checked off and updated the OpenCollective items since @groundwater updated the "About" section of the Electron OpenCollective with the appropriate paragraph.

[erickzhao]

I can take a stab at the website stuff next week.

For this:

Update legal copyright notice on project website and github

What's the exact wording we need for the legal notice?

[bnb]

Thank you for taking the website work @erickzhao! 🙇

I am not a lawyer so I'd probably not be comfortable asserting that myself, so I've asked Brian Warner who does theoretically have context from Foundation lawyers. Will follow up here when I've heard back.

[bnb]

Updated two bullets above with a reference to electron/electronjs.org-old#3895. I think we can mark them as done and merge once everything is approved.

[bnb]

Final TODOs with owners to drive them:

• Update project CoC reporting methods to include OpenJS Foundation escalation path
  • @bnb: working on this with the CPC. Does not seem to be a hard blocker on Electron joining.
• Transfer official domains to OpenJS Foundation
  • @groundwater
• If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool
  • @groundwater
• Transfer official domains to OpenJS Foundation
  • @groundwater
• Identify and document other core project infrastructure
  • @codebytere (https://hackmd.io/@codebytere/rk2-IRPaL)

Unowned TODOs:

• Transfer logomark to the OpenJS Foundation
  • Need update on this from the Foundation / GitHub.
• Identify individuals from the project to join the CPC
  • Admin / WGs

On-join TODOs:

• Merge feat: add OpenJSF copy and logo to footer electronjs.org-old#3895 on join
  • @erickzhao

[bnb]

Update project CoC reporting methods to include OpenJS Foundation escalation path

Tiny update: I've created an issue in the new CoC WG in the OpenJS GitHub org to address the concerns currently mentioned in the OP. I've opened this both as an OpenJS Foundation CPC Regular Member and as someone from the Electron project helping with onboarding. openjs-foundation/code-of-conduct#8

[bnb]

Checked a few more off that have been completed for some time. I'm not sure if the logomark was / will be transferred, if the domains will be/were transferred (or some acceptable accommodation can be met), and we need to choose a DCO or CLA.

I can follow up on the Code of Conduct stuff with the Foundation. AFAIK it was WIP and nothing was ever landed on so... :P

[bnb]

After following up with Jory, the CoC updates don't need to be done.