diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md index 2ab25ff..2156288 100644 --- a/docs/REPO_LICENSE_TRACKING.md +++ b/docs/REPO_LICENSE_TRACKING.md @@ -211,6 +211,11 @@ This file now also preserves the current truth that future models must not lose: - that checklist governs both browser-delivered `MPL` code and any public commercial website, store, checkout, release, or download surface that sells or delivers a build containing those `MPL` lanes + - that checklist now also separates the three cumulative HyperTwist delivery + cases explicitly: + - browser-delivered online use + - public store, checkout, release, and download pages + - bundled executable, installer, desktop package, or mobile package The twenty-three permissive live lanes are: diff --git a/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md b/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md index fd84026..ad98169 100644 --- a/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md +++ b/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md @@ -35,6 +35,13 @@ website or marketplace page that sells, lists, checks out, or delivers a downloadable build containing `MPL`-covered code, even when that website is not itself serving `MPL`-covered browser JavaScript to the visitor. +These obligations are cumulative, not mutually exclusive. A single HyperTwist +release may need to satisfy all of the following at once: + +- browser-delivered online use +- commercial product, store, checkout, or download pages +- bundled executable, installer, desktop package, or mobile package + ## What HyperTwist is relying on today For the current live lanes: @@ -85,6 +92,95 @@ What still does apply today: - if a future HyperTwist website later delivers browser code containing `MPL`-covered material, the website notice branch becomes active at that time +## Three HyperTwist deployment cases + +This section is the operational default for future release engineering. Use it +even if the current checked repo has not yet activated every case. + +### Case A. Browser-delivered online HyperTwist + +This case applies if HyperTwist serves browser code to end users and that +browser code contains `MPL`-covered material or a bundle containing it. + +How to include the licenses: + +- maintain a public `Open Source Notices` or `Legal` page on the website +- identify `cubing/cubing.js` and `coqui-ai/TTS` package code by name on that + page +- include the full `MPL-2.0` text there or provide a stable direct link to it +- include a stable source-availability link for the exact corresponding + `MPL`-covered source used by the deployed browser build +- if `coqui-ai/TTS` models, voices, or payloads are also shipped to users, + include or link their separate artifact-license disclosures on the same legal + surface + +How to present the licenses: + +- place a visible `Legal`, `Licenses`, or `Open Source Notices` link in the + website footer, account menu, or app settings +- if HyperTwist is a logged-in web app, expose the same notices from an + in-product settings/help/about surface after login +- do not rely on a source repo alone as the only place where users can find the + notices +- do not bury the legal surface behind an unstable or private-only URL + +### Case B. Public product page, store page, checkout flow, or download page + +This case applies if HyperTwist sells, licenses, lists, or distributes a build +through a public website, store, marketplace, checkout flow, release page, or +download page, even if the page itself does not serve `MPL` browser code. + +How to include the licenses: + +- add a stable link from the product page, pricing page, checkout page, release + page, store page, and download page to a public `Open Source Notices` or + `Legal` page +- that public legal page must include or link the full `MPL-2.0` text +- that public legal page must include the corresponding source-availability + location for the exact shipped build +- if `coqui-ai/TTS` models, voices, or payloads ship with the downloadable + build, that same public legal surface must include or link the separate + artifact-license disclosures + +How to present the licenses: + +- the legal/notices link should be visible before or at the moment the user + obtains the build +- if the marketplace allows only a single legal link, point it to the stable + HyperTwist `Open Source Notices` page rather than scattering component links +- if HyperTwist controls the checkout confirmation page or delivery email, add + the same legal/notices link there as well +- release notes for the shipped build should repeat the legal/notices link and + source-availability link + +### Case C. Bundled executable, installer, desktop package, or mobile package + +This case applies if HyperTwist ships a native executable, installer, desktop +bundle, archive, or mobile application package containing `MPL`-covered code. + +How to include the licenses: + +- include `ThirdPartyNotices.txt` or an equivalent bundled notices file in the + shipped package +- include `licenses/MPL-2.0.txt` or another bundled full copy of the + `MPL-2.0` license text +- include a source-availability statement naming where recipients can obtain + the exact corresponding `MPL`-covered source for that shipped build +- if HyperTwist modified any `MPL`-covered upstream files directly, publish + those modified files under `MPL` +- if `coqui-ai/TTS` models, voices, or payloads are shipped, include separate + artifact-level notice handling for them + +How to present the licenses: + +- expose an in-product `Open Source Notices`, `Licenses`, or `Legal` screen +- desktop default: `Help > About > Open Source Notices` or equivalent +- mobile default: `Settings > About > Open Source Notices` or equivalent +- keep the notices reachable after installation without requiring the user to + locate the source repository manually +- if the installer supports a `Licenses` or `Third-Party Notices` step or file + link, include it there too + ## Scenario matrix ### 1. Internal-only use inside the organization