You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2025/11/26 01:37:00 UTC
[jira] [Commented] (YUNIKORN-3151) Remove extra text from license
[ https://issues.apache.org/jira/browse/YUNIKORN-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040749#comment-18040749 ]
Wilfred Spiegelenburg commented on YUNIKORN-3151:
-------------------------------------------------
Committed all changes, found a file that is missed in the release repo. The copy of the file that we add into the source build has not been updated and should still be fixed.
Opening a new Jira for the NOTICE file updates that we need to do and we can fix the LICENSE file in the release repo as part of that jira
> Remove extra text from license
> ------------------------------
>
> Key: YUNIKORN-3151
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3151
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Hsien-Cheng(Ryan) Huang
> Assignee: Dennis Huang
> Priority: Major
> Labels: pull-request-available
>
> The Apache 2.0 license on the website shows that it ends after "END OF TERMS AND CONDITIONS" https://www.apache.org/licenses/LICENSE-2.0
> 387383537-f56c8594-5c32-41d5-a5b7-f4a587125ca2
> This text exists because it's been mistakenly copied and pasted from https://www.apache.org/licenses/LICENSE-2.0.txt where it includes placeholder text and the intent seems to be reproducing the application instructions as seen on https://www.apache.org/licenses/LICENSE-2.0 rather than as text that's intended to be included in the license.
> The text removed in this PR diverges slightly from the text on https://www.apache.org/licenses/LICENSE-2.0#apply
> How to apply the Apache License to your work
> Include a copy of the Apache License, typically in a file called LICENSE, in your work, and consider also including a NOTICE file that references the License.
> To apply the Apache License to specific files in your work, attach the following boilerplate declaration, replacing the fields enclosed by brackets "[]" with your own identifying information. (Don't include the brackets!) Enclose the text in the appropriate comment syntax for the file format. We also recommend that you include a file or class name and description of purpose on the same "printed page" as the copyright notice for easier identification within third-party archives.
> The text on the website ⬆️ seems to indicate that placing the Apache 2.0 license text in a LICENSE is sufficient for a project. The text given in the text file ⬇️ does not mention a LICENSE file and instead seems to imply that the full text of the Apache 2.0 license is not required, but use the "boilerplate" after swapping out the placeholders.
> Looking at other high profile projects that use the Apache 2.0 license it looks like their understanding matches mine, here's Rust https://github.com/rust-lang/rust/blob/fda68927475070696fcc9d1f5c9c990f0e1af87a/LICENSE-APACHE. Here's a discussion from 5 years ago on whether to remove the appendix from there rust-lang/rust#67734. And here's an ASF project that merged a similar change:
> Remove extra text from license wicket#1078
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org