Skip to content

Relicense under FSL-1.1-Apache-2.0#45

Merged
gmegidish merged 1 commit into
mainfrom
chore-update-license
May 24, 2026
Merged

Relicense under FSL-1.1-Apache-2.0#45
gmegidish merged 1 commit into
mainfrom
chore-update-license

Conversation

@gmegidish
Copy link
Copy Markdown
Member

Summary

  • Replace Apache 2.0 license with Functional Source License 1.1 (ALv2 future license)
  • Copyright 2025-2026 Mobile Next HQ, Inc.
  • Converts to Apache 2.0 on the second anniversary of initial availability

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 22, 2026

Walkthrough

The 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)
Check name Status Explanation
Title check ✅ Passed The title 'Relicense under FSL-1.1-Apache-2.0' directly and concisely summarizes the main change: replacing the Apache 2.0 license with the Functional Source License 1.1 with an Apache 2.0 future license.
Description check ✅ Passed The description clearly explains the license replacement change, including the specific license types, copyright attribution, and the conversion timeline, which aligns with the file changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore-update-license

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3c0c839b-8dab-475d-8aaa-e1b9c7c0c154

📥 Commits

Reviewing files that changed from the base of the PR and between 9562f3a and b0f1967.

📒 Files selected for processing (1)
  • LICENSE

Comment thread LICENSE
Comment on lines +44 to +45
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.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

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.

Suggested change
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).

@gmegidish gmegidish merged commit 5f17f66 into main May 24, 2026
6 checks passed
@gmegidish gmegidish deleted the chore-update-license branch May 24, 2026 14:02
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