#52384: docs: update coc to contributor covenant v3.0
Description of Change
The Contributor Covenant has been updated to v3.0 now, so I am going through and updating our code of conduct documentation throughout the organization. This code of conduct file has served as our most up to date file in the past, so I am updating it first. However, we also have our .github code of conduct that is used as the default in all repositories if a code of conduct file is not found.
I am fine with keeping both this file and the .github one (once it is also updated) if there is some reason they should remain separate, but it might make sense to get rid of this one in favor of just having the one in .github. I think both options are worth discussing further, but this PR should help us get started.
Checklist
- I have filled out the PR description
- I have reviewed and verified the changes
- relevant API documentation, tutorials, and examples are updated and follow the documentation style guide
- PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron