Skip to content

Chore/reuse inline headers#36

Draft
yreyricord wants to merge 5 commits into
developfrom
chore/reuse-inline-headers
Draft

Chore/reuse inline headers#36
yreyricord wants to merge 5 commits into
developfrom
chore/reuse-inline-headers

Conversation

@yreyricord

Copy link
Copy Markdown
Collaborator

Linked issue

Closes #25

  • The linked issue is labelled status:approved, good-first-issue or help-wanted.

What this PR changes

  • Adds inline SPDX-FileCopyrightText and SPDX-License-Identifier headers to legacy textual files across the repository (~800 files), replacing bulk coverage in REUSE.toml.
  • Shrinks REUSE.toml to its minimal form: binary assets and LICENSES/** only.
  • Adds .license companion files where inline headers are not possible (JSON, per-package LICENSE.txt, LICENSE.md, Dockerfile-from-yml, IERS bulletin).

Notes for reviewers

  • Large mechanical diff (header-only on most files); no runtime or API behaviour changes.
  • Python sources keep MIT (SPDX-License-Identifier: MIT); Apache-2.0 applies to config, CI, Docker, XSD/XML, and README-style assets as annotated.
  • This branch is currently based on chore/repository-config-foundation (PR Chore/repository config foundation #24). Plan is to rebase onto develop after Chore/repository config foundation #24 merges so the diff against develop is clean.

User-facing change

  • This PR introduces a user-facing change (API, CLI, output format, performance, documentation).

If yes, write one short release-note sentence here (it will be picked up in CHANGELOG.md):

Documentation

  • This PR modifies the documentation (Sphinx site, README, wiki, ATBD, Science Guide).
  • This PR does not modify the documentation, and no documentation update is needed.
  • This PR does not modify the documentation, but a documentation update is needed and tracked in issue #_____.

Tier rationale

  • Expected tier: 0
  • Why: Mechanical REUSE/SPDX header migration only. No processor logic, locked paths, VERSION, or heavy regression paths touched. Validation is reuse lint (and existing baseline CI).

AI assistance disclosure

  • No AI tools were used to prepare this PR.
  • AI tools were used. Tool(s): Cursor (Claude)

    What was generated (code, tests, documentation, commit messages): copyright attribution, commit/PR draft text; no processor logic changes.

    I have reviewed the generated content and take responsibility for it.

Checklist

  • This PR closes exactly one tracking issue, linked above.
  • The scope of the diff matches the approved scope in the linked issue. No drift, no extras.
  • A breaking change is explicitly flagged in the release note sentence above (if applicable).
  • The reviewer assigned has the relevant domain knowledge for this change.

CODEOWNERS currently routes every path to the single primary maintainer.
SME team handles for the L1, L2, Stack, docs and legal areas are pending
confirmation by maintainers and will be applied in a follow-up PR.

Signed-off-by: yreyricord <yoann.rey-ricord@acri-st.fr>
Weekly schedule covering Python (pyproject.toml per bps-* package)

Signed-off-by: yreyricord <yoann.rey-ricord@acri-st.fr>
REUSE.toml covers legacy files in bulk by category.

Signed-off-by: yreyricord <yoann.rey-ricord@acri-st.fr>
Replace the transitional REUSE.toml bulk manifest with inline SPDX headers
on legacy source files, so licence and copyright are visible in each file
and coverage no longer depends on path globs.

- Annotate ARESYS legacy files as ARESYS - European Space Agency (ESA)
- Add .license companions for JSON, MIT licence texts, and Dockerfiles
- Download LICENSES/CC-BY-4.0.txt for IERS and OGC schema declarations
- Reduce REUSE.toml to binary assets and LICENSES/** only

Closes #25

Signed-off-by: yreyricord <yoann.rey-ricord@acri-st.fr>
@rpiantanida

Copy link
Copy Markdown
Collaborator

@yreyricord here applies this comment from @matteoaletti #24 (comment) about the files header and also my comment on the same PR on the need to involve someone from ESA in the review process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[feature] Migrate REUSE bulk annotations to inline SPDX headers

2 participants