Merge pull request #41 from ecmwf/copilot/tidy-up-repository-structure

Tidy repository structure: reorganise content and fix typos

Author: tlmquintino

ADR/ADR-Guidelines.md

@@ -4,7 +4,7 @@ This document provides a Guidelines and a template for creating Architectural De
 
 ## Template for Architectural Decision Records (ADRs)
 
-Please find the template for creatinsg ADRs in the [ADR-Template.md](./ADR-Template.md) file. This template should be used for all ADRs to ensure consistency and clarity.
+Please find the template for creating ADRs in the [ADR-Template.md](./ADR-Template.md) file. This template should be used for all ADRs to ensure consistency and clarity.
 
 ## Purpose
 
@@ -22,7 +22,7 @@ Create an ADR when making decisions that:
 - **Require justification and analysis** - Trade-offs between options, risk assessments, cost-benefit
 - **Involve trade-offs between alternatives** - For example performance vs. maintainability, cost vs. functionality
 - **Establish important conventions** - Coding standards, deployment processes, monitoring strategies
-- **Address compliance or regulatory requirements** - Adherance to standards like OGC and Data governance, but also security policies and identity managment
+- **Address compliance or regulatory requirements** - Adherence to standards like OGC and Data governance, but also security policies and identity management
 
 ## Writing Guidelines
 
@@ -126,10 +126,10 @@ Before finalizing an ADR, ensure it meets these criteria:
 
 ## Numbering and Filing
 
-- Use sequential numbering: ADR-001-Meaningfull-Title, ADR-002-Another-Meaningfull-Title, etc.
+- Use sequential numbering: ADR-001-Meaningful-Title, ADR-002-Another-Meaningful-Title, etc.
 - Store ADRs in the central **Codex** repository under `/ADR/`
 - Use descriptive filenames: `ADR-001-Git-Branching-Model.md`
-- Use the [ADR index](./ADR/ADR-Index.md) to track all ADRs and their statuses
+- Use the [ADR index](./ADR-Index.md) to track all ADRs and their statuses
 
 ## Review Process
 

Contributing Externally/readme.md Contributing Upstream/README.mdContributing Externally/readme.md renamed to Contributing Upstream/README.md

@@ -1,5 +1,5 @@
-Documentation
-=============
+Documentation and Training
+==========================
 
 1. Documentation can be generated via any sensible tool that generates static pages (mkdocs, sphinx, etc.)
 2. Documentation should be published to readthedocs, github pages or sites.ecmwf.int

Contributing Externally/forking.md Contributing Upstream/forking.mdContributing Externally/forking.md renamed to Contributing Upstream/forking.md

@@ -0,0 +1,11 @@
+# Guidelines
+
+Development guidelines for ECMWF software projects.
+
+## Contents
+
+- [Pull Request Guidelines](./pull-requests.md) — responsibilities for reviewers and reviewees, and the PR workflow
+- [AI Contributions to Software](./ai_contributions_to_software.md) — policy guidelines for AI-assisted code generation and AI agents
+- [Containerisation](./Containerisation.md) — guidelines for containerising ECMWF software
+- [Observability](./Observability.md) — observability guidelines for ECMWF services
+- [External Contributions](./external-contributions.md) — guidelines for accepting external contributions to ECMWF projects

Documentation and Training/README.md

@@ -35,7 +35,7 @@ At ECMWF, we view AI Code Agents and Large Language Models (LLMs) as powerful pr
 
 ### Working with AI Agents
 
-* **Data Privacy and Prompt Security:** Developers must not paste sensitive ECMWF data, proprietary keys, unreleased model architectures, or sensitive infrastructure details into *public* AI prompts (e.g., consumer ChatGPT) versus approved internal enterprise tools like GitHub Copilot Enterprise. We have guarrantees from our enterprise providers that data is kept secure, but we should still avoid sharing sensitive information in prompts.
+* **Data Privacy and Prompt Security:** Developers must not paste sensitive ECMWF data, proprietary keys, unreleased model architectures, or sensitive infrastructure details into *public* AI prompts (e.g., consumer ChatGPT) versus approved internal enterprise tools like GitHub Copilot Enterprise. We have guarantees from our enterprise providers that data is kept secure, but we should still avoid sharing sensitive information in prompts.
 
 * **Warning on Intellectual Property and Licensing:** Note that AI models can occasionally reproduce snippets of copyrighted code (e.g., strictly GPL-licensed code). Developers should be reasonably confident the generated code does not violate ECMWF's open-source licensing strategy (mostly Apache 2.0).
 

Containerisation/README.md Guidelines/Containerisation.mdContainerisation/README.md renamed to Guidelines/Containerisation.md

@@ -67,7 +67,7 @@ merge commits such as "WIP" or "Fix Review Comment", commits like this make it
 more difficult in the future to reason about changes. Be aware that this means
 rewriting your PRs history. While history rewriting is strongly discourraged
 for the primary branches, it is explicitly encouraged on your development
-branch to create meaningfull commits.
+branch to create meaningful commits.
 
 ## General Guidelines