Add Code of Conduct for ECMWF software development - #58
Conversation
Introduces a Code of Conduct adapted from the Contributor Covenant v2.1, aligned with ECMWF's Open Source Principles and the UN Open Source Principles. Based on the Code of Conduct established in the tensogram project (ecmwf/tensogram).
There was a problem hiding this comment.
Pull request overview
Adds an ECMWF-aligned Code of Conduct (adapted from Contributor Covenant v2.1) to the codex repository so downstream projects can reference a single source of truth.
Changes:
- Added a new Code of Conduct document under
Principles/. - Linked the Code of Conduct from the main
README.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
README.md |
Adds a Contents link pointing to the Code of Conduct document. |
Principles/CODE_OF_CONDUCT.md |
Introduces the Code of Conduct text, including enforcement contact and attribution. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| # Contents | ||
|
|
||
| - [Code of Conduct](./Principles/CODE_OF_CONDUCT.md) |
There was a problem hiding this comment.
The PR description says a CODE_OF_CONDUCT.md is added at the repository root, but the actual file is Principles/CODE_OF_CONDUCT.md and the README links to that path. If the intent is to have GitHub automatically detect and surface the Code of Conduct, it needs to be placed in a supported location (typically the repo root or .github/). Please either move/duplicate the file accordingly and update this link, or adjust the PR description to match the chosen location.
There was a problem hiding this comment.
adjust the PR description.
Summary
CODE_OF_CONDUCT.mdunder thePrinciples/directory, adapted from the Contributor Covenant v2.1emailto:→mailto:typo from the originalContext
As the codex defines standards for all ECMWF software development, having the Code of Conduct here establishes a single reference that individual projects (like tensogram) can point to, rather than each project maintaining its own copy. The file lives in
Principles/alongside the existing Open Source Principles, since the Code of Conduct is a foundational principle rather than an operational guideline.Test plan
./open-source-principles.mdfrom withinPrinciples/)mailto:link works in the enforcement section