chore(license): relicense FSB from BSL 1.1 to MIT - #115
Conversation
Replace the Business Source License 1.1 text with the standard MIT license and update every license claim in the repo: SPDX fields in both package.json/package-lock.json pairs, the README and mcp README badges, showcase footers and privacy copy, the extension help panel, and the llms.txt/llms-full.txt crawler sources. Advertise the canonical LICENSE URL in the SoftwareApplication JSON-LD on the home and agents pages, and extend the crawler smoke and showcase build smoke to assert that metadata in prerendered HTML (en plus all 5 locales) and in the generated AEO files.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 10a9621a7b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| <h3>Open Source</h3> | ||
| <p><span [attr.translate]="'no'">FSB</span> is fully open source under the <span [attr.translate]="'no'">BSL 1.1</span> License. You can audit every line of code to verify these privacy claims. The source code is available on <a href="https://github.com/lakshmanturlapati/FSB" target="_blank" rel="noopener" [attr.translate]="'no'">GitHub</a>.</p> | ||
| <p><span [attr.translate]="'no'">FSB</span> is fully open source under the <span [attr.translate]="'no'">MIT</span> License. You can audit every line of code to verify these privacy claims. The source code is available on <a href="https://github.com/lakshmanturlapati/FSB" target="_blank" rel="noopener" [attr.translate]="'no'">GitHub</a>.</p> |
There was a problem hiding this comment.
When users expand this historical policy, it now says the March 2026 version was MIT-licensed even though that release used BSL 1.1. The archive explicitly promises to preserve the policy “as it stood in March 2026,” so changing this line—and its localized XLIFF targets—rewrites the historical legal posture rather than documenting the current relicensing. Keep BSL 1.1 in this archived component while using MIT on the current policy page.
Useful? React with 👍 / 👎.
| The above copyright notice and this permission notice shall be included in all | ||
| copies or substantial portions of the Software. |
There was a problem hiding this comment.
When a release is built with npm run package:extension, scripts/package-extension.mjs zips only extension/, while the new license notice remains at the repository root and no license file exists under extension/; the changed control-panel copy provides only an external link, not this notice. The newly adopted grant expressly requires the copyright and permission notice to accompany copies or substantial portions, so the distributable extension archive does not satisfy its stated license. Copy the root license into the packaged tree or explicitly add it to the archive.
Useful? React with 👍 / 👎.
The Concierge page landed on main after this branch forked, so its footer still advertised "BSL 1.1 License" while its own body copy already said MIT. Convert that link and its six XLIFF entries. Also add the canonical LICENSE URL to the Concierge SoftwareApplication JSON-LD, matching home and agents. The crawler smoke now carries the node selector per route on MARKETING_ASSERTIONS instead of branching on path, so the license assertion covers /, /agents, and /concierge; the build smoke asserts the same across en and all 5 locales.
|
Merged Re-verified after the merge: |
The package now declares "license": "MIT", but npm packed 11 files and none of them was a license: `files` is a whitelist that omits it and there was no mcp/LICENSE for npm to pick up automatically. MIT's only condition is that the copyright and permission notice accompany copies, so anyone installing from npm got the SPDX claim without the notice. Copy the root LICENSE into mcp/; the `files` whitelist needs no change because npm always packs a root-level LICENSE. Also fix the one layer reference in showcase-build-smoke that survived the three-to-four renumbering: the build moved to layer 3, and SKIP_BUILD=1 leaves the new AEO asserts in layer 2 running unconditionally.
1 participant
Replaces the Business Source License 1.1 with the standard MIT license and updates every license claim in the repo — SPDX fields in both
package.json/lockfile pairs, the README and MCP README badges, showcase footers, privacy copy, the extension help panel, and thellms.txt/llms-full.txtcrawler sources, plus the six XLIFF catalogs for the three translated license strings.The home and agents pages now advertise the canonical LICENSE URL in their
SoftwareApplicationJSON-LD, and both the crawler smoke and the showcase build smoke assert that metadata in prerendered HTML (en and all five locales) as well as in the generated AEO files.Verified locally:
ng extract-i18nis byte-identical to the committedmessages.xlf, the translation drift and quality gates pass,tests/showcase-build-smoke.test.jsis 94/94 withSKIP_BUILD=1, andsmoke:crawler:localis 135/135.