Skip to content

Superseded by #167: the same four-document change with a DCO sign-off - #166

Closed
iderex wants to merge 1 commit into
mainfrom
licence/three-documents-and-a-triage-that-say-the-file-is-absent
Closed

Superseded by #167: the same four-document change with a DCO sign-off#166
iderex wants to merge 1 commit into
mainfrom
licence/three-documents-and-a-triage-that-say-the-file-is-absent

Conversation

@iderex

@iderex iderex commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Refs #163

Why this is closed

The head here carries no Signed-off-by trailer, and the DCO gate refused it by
name:

FAIL  36a05d603d6cdb6943d9801d2daedc6ad758dc85 is missing: Signed-off-by: Nils Lehnen <30603423+iderex@users.noreply.github.com>

The repair is the same commit cherry-picked with the trailer onto a new branch,
because the alternative is rewriting a branch that has already been pushed. That
is #167, which carries the whole body this one had, the same four-file diff and
its own run of the checks.

This branch is left where it is rather than deleted. Nothing was lost, and
nothing here is waiting on anybody.

What it changed

LICENSE is on the default branch and carries AGPL-3.0. Three documents and one
triage paragraph still said, in the present tense, that this repository has no
licence file. docs/operator-guide.md, docs/promotion.md and SECURITY.md say
what the tree holds instead, and the triage paragraph under License, 0 in
docs/supply-chain.md says the file has since landed and names the commit, with
the heading and the quoted warning left as the run that document declares
reported them.

None of the four says the licence declaration is made. DeclaredLicence is still
empty and the licence leg still reports that it was not asked, so each document
that mentions it points at #47.

The evidence for all of that is in #167 rather than restated here, because two
copies of one transcript drift apart and a reader cannot tell which one was run.

…say it holds nothing

LICENSE is on the default branch carrying AGPL-3.0, and three documents plus one
triage paragraph still said in the present tense that this repository has no
licence file. Each of the three resolved fine and read as current, so a reader
who believed them concluded they may not reuse anything here, which is the
opposite of the terms the tree carries.

docs/operator-guide.md tells a downloader what terms the thing arrived under.
docs/promotion.md says what the code carries out and keeps the hand-over of
somebody else's work blocked on entry three of #46, which carries no answer.
SECURITY.md keeps the licence out of the set of things that are vulnerabilities.
The triage paragraph in docs/supply-chain.md says the file has since landed and
names the commit, with the License, 0 heading and the quoted warning left as the
run this document declares reported them.

None of the four says the declaration is made. DeclaredLicence is still empty
and the licence leg still reports that it was not asked, so each document that
mentions it points at #47 instead.

Refs #163
@iderex iderex changed the title Say what the tree holds about the licence in the four documents that say it holds nothing Superseded by #167: the same four-document change with a DCO sign-off Aug 22, 2026
@iderex iderex closed this Aug 22, 2026
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.

1 participant