potiuk opened a new pull request, #73067:
URL: https://github.com/apache/airflow/pull/73067

   …(#73065)
   
   The source tarball is what a consumer of an Apache Airflow release reads for 
licensing, and its root LICENSE was bare Apache-2.0 with no subcomponents 
section. Since the provider registry landed it has also shipped two web fonts 
that are not ours and not Apache-2.0: JetBrains Mono and Plus Jakarta Sans, 
both under the SIL Open Font License 1.1, vendored as woff2 and loaded through 
@font-face. The OFL requires the copyright notice and licence to travel with 
the font, so redistributing them with no notice anywhere in the tree left the 
tarball own licensing incomplete.
   
   The licence texts are the ones published by each upstream project, at the 
versions recorded in the woff2 name tables. They sit next to the component they 
cover, matching how airflow-core and the fab and google providers keep their 
third-party texts, and the root LICENSE gains the subcomponents section that 
airflow-core/LICENSE already carries so the pointer is where a reader looks 
first.
   (cherry picked from commit 5b28f1facec396135a071ae6904a4489da57a2de)
   
   
   Generated-by: Claude Opus 5
   Claude-Session: https://claude.ai/code/session_012zrnHJHPchB83FtwrYRf5q
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
https://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to