Add Continuous Software Delivery guideline (contractor deliveries)#64
Add Continuous Software Delivery guideline (contractor deliveries)#64JamesVarndell wants to merge 16 commits into
Conversation
|
Can we add something like "AI tools may be used to assist in writing this documentation, but the contractor is responsible for, and must ensure, the final completeness and correctness". Otherwise I am concerned we will just get the output of "Check these requirements, fill in this document" with no further verification. We all know AI would do a great and vague job of filling this in |
Co-authored-by: Eddy Comyn-Platt <53045993+EddyCMWF@users.noreply.github.com>
Added a note on the use of AI tools for documentation.
Clarify AI tools responsibility in documentation
Removed duplicate paragraph about documentation requirements.
… cross-links - Move 'Software Delivery/Technical-Handover.md' -> 'Guidelines/Continuous- Software-Delivery.md'; retitle 'Continuous Software Delivery to ECMWF' (scope is software, not only web apps). Index in Guidelines/README.md and root README. - Apply reviewer suggestions: emphasis-flipped intro (EddyCMWF); deployment architecture must be agreed with the Technical Officer (Docker/Helm/K8s are the default, not a hard requirement, so data-production workflows fit); recommend multi-container deployment config in a separate repository. - Convert absolute GitHub URLs to relative links. - Align with current Codex: licensing (Apache-2.0 + SPDX/REUSE per ADR-010), Repository Structure conventions (incl. SECURITY.md), never-commit-secrets (history scanned before publication), AI-Contributions link, and a Publication/open-sourcing paragraph (repos start private; publication via Open-Sourcing-Software + audit gates). - Bidirectional linkage with External-Contributions (which governs *how* code flows; PR-into-main is the contractual acceptance point) + reverse pointer.
|
I pushed a revision ( A few optional content additions I did not make, left for @JamesVarndell / reviewers to consider — happy to draft any of them:
|
There was a problem hiding this comment.
Pull request overview
Adds a new guideline describing what external contractors must deliver so ECMWF can assume ownership and operate delivered software/services, and links it into the existing documentation navigation.
Changes:
- Added a new “Continuous Software Delivery” guideline detailing continuous delivery expectations, deployment reproducibility, data/service dependencies, and credential handling.
- Linked the new guideline from the root README and the Guidelines index.
- Cross-referenced the new guideline from the existing “External Contributions” guidance for contractor deliveries.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Adds the new guideline to the main documentation contents list. |
| Guidelines/README.md | Adds the new guideline to the Guidelines index. |
| Guidelines/External-Contributions.md | Points contractor “full service/product” deliveries to the new continuous delivery guideline. |
| Guidelines/Continuous-Software-Delivery.md | Introduces the new contractor delivery requirements document. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Number the closing section '## 8. Publication and Open-Sourcing' to match the document's numbered structure (1-7). - Use 'Dockerfiles' consistently (was 'Docker files') in the deployment section.
Reword the External-Contributions pointer: contractors deliver credential *configuration and regeneration procedures*, never secret values themselves — consistent with Continuous Software Delivery Section 7.
… Structure Match the 'cookiecutter template' term used in Repository Structure/README.md (the doc this bullet links to).
- Make the ADR-010 reference a clickable link (matches other ADR references). - Retitle section 3 'Source Code' -> 'Repository Documentation' to match its content (cross-repo README/branch documentation).
tlmquintino
left a comment
There was a problem hiding this comment.
Ive made my reviews and pushed some commits. Its back to you @JamesVarndell and possibly @EddyCMWF
Description
Adds documentation for continuous software delivery to ECMWF from an external contractor.
Contributor Declaration
By opening this pull request, I affirm the following: