Allow to use short SPDX licence identifier for selected files#62073
Merged
potiuk merged 1 commit intoapache:mainfrom Feb 17, 2026
Merged
Allow to use short SPDX licence identifier for selected files#62073potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
area:helm-chart
Dev-iL
approved these changes
Feb 17, 2026
Collaborator
Dev-iL
left a comment
Dev-iL
left a comment
There was a problem hiding this comment.
I thank you in the name of all agents and their users!
1 task
1 task
jscheffl
approved these changes
Feb 17, 2026
While we have some discussion on-going whether we should use some shorter, machine-readable friendly versions of licence specification in our source code headers here [1], the notion is that: a) PMC can make judgment calls when to include different versions of the licence b) This expectation only applies to the code we actually release in our official releases. This change makes some judgment call on using much shorter, SPDX driven licence headers in some specific files: * markdown files that are intended to be consumed by agents (AGENTS.md, SKILLS.md, CLAUDE.md and so on) * all the markdown .github/* files that are clearly meta-data for GitHub and which we exclude from released sources We also make sure all those files are excluded from the official source releases and distribution packages we prepare. [1] https://lists.apache.org/thread/j1tn63r2lf13v3d1tnnqff8fkcl4nx53
potiuk
force-pushed
the
use-short-licences-for-some-files
branch
from
b66e88e to
a2bea2d
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…iles (#62073) While we have some discussion on-going whether we should use some shorter, machine-readable friendly versions of licence specification in our source code headers here [1], the notion is that: a) PMC can make judgment calls when to include different versions of the licence b) This expectation only applies to the code we actually release in our official releases. This change makes some judgment call on using much shorter, SPDX driven licence headers in some specific files: * markdown files that are intended to be consumed by agents (AGENTS.md, SKILLS.md, CLAUDE.md and so on) * all the markdown .github/* files that are clearly meta-data for GitHub and which we exclude from released sources We also make sure all those files are excluded from the official source releases and distribution packages we prepare. [1] https://lists.apache.org/thread/j1tn63r2lf13v3d1tnnqff8fkcl4nx53 (cherry picked from commit eb96837) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-1-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While we have some discussion on-going whether we should use some shorter, machine-readable friendly versions of licence specification in our source code headers here [1], the notion is that:
a) PMC can make judgment calls when to include different versions of
the licence
b) This expectation only applies to the code we actually release
in our official releases.
This change makes some judgment call on using much shorter, SPDX driven licence headers in some specific files:
markdown files that are intended to be consumed by agents (AGENTS.md, SKILLS.md, CLAUDE.md and so on)
all the markdown .github/* files that are clearly meta-data for GitHub and which we exclude from released sources
We also make sure all those files are excluded from the official source releases and distribution packages we prepare.
[1] https://lists.apache.org/thread/j1tn63r2lf13v3d1tnnqff8fkcl4nx53
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.