Relicense under FSL-1.1-Apache-2.0#45
Conversation
WalkthroughThe LICENSE file has been entirely replaced. The previous Apache License 2.0 text has been removed and substituted with the Functional Source License, Version 1.1. The new license includes sections covering License Grant, Permitted Purpose, Patents, Redistribution, Disclaimer, and Trademarks. A Grant of Future License section specifies that the code will be made available under Apache License 2.0 effective on the second anniversary of initial availability. The copyright line has been updated to reflect 2025–2026. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@LICENSE`:
- Around line 44-45: Update the "Grant of Future License" clause to replace the
phrase "second anniversary of the Software's initial availability" with a
concrete calendar date and/or a clear definition of "initial availability"
(e.g., "the date of first public release of this repository, defined as the date
the initial public tag/release was published") so downstream users have an
unambiguous trigger; modify the text in the Grant of Future License section to
state the exact conversion date (or the exact event definition) and, if keeping
an event-based trigger, add a precise definition of "initial availability" and
how it is determined (e.g., by repository release tag or distribution artifact).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| Grant of Future License | ||
| An additional Apache License, Version 2.0 becomes effective on the second anniversary of the Software's initial availability. After that date, users may alternatively use the Software under the Apache License, Version 2.0. |
There was a problem hiding this comment.
Clarify the Apache-2.0 conversion trigger with an explicit date.
“Second anniversary of initial availability” is legally ambiguous for downstream redistribution/compliance (e.g., per release, per repo, per artifact). Please add a concrete conversion date (and optionally define what “initial availability” means) to avoid conflicting interpretations.
Suggested wording
Grant of Future License
-An additional Apache License, Version 2.0 becomes effective on the second anniversary of the Software's initial availability. After that date, users may alternatively use the Software under the Apache License, Version 2.0.
+An additional Apache License, Version 2.0 becomes effective on the second anniversary of the Software's initial availability.
+For clarity, the Apache License, Version 2.0 conversion date is: YYYY-MM-DD.
+After that date, users may alternatively use the Software under the Apache License, Version 2.0.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Grant of Future License | |
| An additional Apache License, Version 2.0 becomes effective on the second anniversary of the Software's initial availability. After that date, users may alternatively use the Software under the Apache License, Version 2.0. | |
| Grant of Future License | |
| An additional Apache License, Version 2.0 becomes effective on the second anniversary of the Software's initial availability. | |
| For clarity, the Apache License, Version 2.0 conversion date is: YYYY-MM-DD. | |
| After that date, users may alternatively use the Software under the Apache License, Version 2.0. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@LICENSE` around lines 44 - 45, Update the "Grant of Future License" clause to
replace the phrase "second anniversary of the Software's initial availability"
with a concrete calendar date and/or a clear definition of "initial
availability" (e.g., "the date of first public release of this repository,
defined as the date the initial public tag/release was published") so downstream
users have an unambiguous trigger; modify the text in the Grant of Future
License section to state the exact conversion date (or the exact event
definition) and, if keeping an event-based trigger, add a precise definition of
"initial availability" and how it is determined (e.g., by repository release tag
or distribution artifact).
Summary