From a1fd2d5a0577412b261f5d8f34ede9decb57a03b Mon Sep 17 00:00:00 2001 From: multipleof4 Date: Mon, 14 Sep 2026 21:15:24 -0700 Subject: [PATCH] Add license agreement for software usage and reuse Added a comprehensive license agreement outlining usage, ownership, and reuse conditions for the software. --- LICENSE | 85 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..f99d431 --- /dev/null +++ b/LICENSE @@ -0,0 +1,85 @@ +1. Scope + +The copyright holders offering software, source code, assets, or other content +under these terms ("we") grant the permissions below to every individual, team, +company, organization, and other entity ("you"). "Work" means the software, +source code, assets, and other content we offer under these terms. + +2. Using the product and owning your output + +You may use the customer-facing software or product for any purpose, including +commercial purposes, without payment, acknowledgment, or a copy of these terms. +This includes installing, running, accessing, and self-hosting it, and compiling +it solely to run it. + +Whatever you create through ordinary use of the product is yours. We claim no +ownership of your output and impose no payment, acknowledgment, or licensing +conditions on it. You may use, sell, share, or license it however you choose. +Merely copying or extracting the underlying codebase or assetbase is reuse +under section 3. + +3. Reusing code or assets + +Subject to section 4, you have worldwide, nonexclusive permission to copy, +modify, combine, publish, distribute, sublicense, sell, and otherwise reuse any +or all of the Work, for any purpose, in source or other forms. + +4. Finding common ground + +If you reuse the codebase or assetbase, you are responsible for satisfying one +of the following conditions when you begin that reuse: + +- If you cannot reasonably afford a monetary payment, give a simple + acknowledgment of the original software or repository in an appropriate + place, such as your README, source code, website, or documentation. A name + mention or a link is enough. No particular wording or placement is required. + +- If you can afford a monetary payment, sponsor the original + repository through its Sponsor button. You alone decide the minimum + reasonable amount you can afford, considering the circumstances of the entity + reusing the Work. Sponsorship may be one-time or monthly. If you pay any + positive amount, acknowledgment and links are optional. + +An entity may satisfy this condition through someone acting on its behalf. + +5. Final settlement + +Any positive amount successfully paid through that sponsorship route fully +and permanently satisfies the reuse condition for the entity making it or on +whose behalf it is made. Your chosen amount is accepted as sufficient, +regardless of your financial means. +We will not challenge its adequacy, request financial evidence, or demand a +larger amount. A record of the completed payment is sufficient proof; no +separate approval or agreement is needed. + +The first completed monthly payment is enough. Later payments are optional, +and you may cancel recurring sponsorship without losing your permissions. + +Likewise, an appropriate acknowledgment fully satisfies the condition for an +entity using the acknowledgment option. + +Once satisfied, the condition covers all reuse by that entity of the Work +offered under these terms in the same original repository, including later +versions. No payment or acknowledgment is required again for additional uses, +copies, releases, or products. The permissions granted are then irrevocable +for that Work. + +6. Choosing another license + +After satisfying section 4, you may distribute or sublicense the Work, +modified or unmodified, under any license you choose. You do not have to include +these terms, keep this license, or require anyone else to follow it. These +terms require no retained copyright or license notices; the acknowledgment +option in section 4 is the only acknowledgment requirement. + +Recipients of the Work you distribute under another license follow that +license and owe us no payment or acknowledgment under these terms for that +Work. Relicensing grants permissions; it does not transfer ownership of +the original Work. + +7. Warranty + +To the extent permitted by law, the Work is provided "as is," without any +warranty, including merchantability, fitness for a particular purpose, or +noninfringement. We are not liable for any claim, loss, or damages arising from +the Work or its use.