Skip to content

COMPLIANCE.md

Latest commit

 

History

History
50 lines (39 loc) · 2.34 KB

COMPLIANCE.md

File metadata and controls

50 lines (39 loc) · 2.34 KB
Raw

Complying with the Basis license

This guide exists because we've encountered a couple of instances of users of the Basis framework stripping or otherwise omitting the Basis license notice. We take license compliance seriously.

Basis is released under the MIT License. You may use, copy, modify, merge, publish, distribute, sublicense, and sell it, including in closed-source and commercial projects. In exchange, the license imposes one condition. It is easy to fulfill, but it is NOT optional:

Every copy you distribute must include the Basis copyright notice and license text. This applies to builds of your client, not just source code. "We forgot" is not an exemption; it is still a violation.

This applies to any substantial portion of Basis, not just the full framework: if you extract, port, or adapt a component, system, or script from Basis, include the Basis notice (and any third-party notices that component depends on) just as a full client would. If you're unsure whether what you've taken counts, include the notice.

How to comply

  • Keep the "Third-Party Licenses" screen in your client, reachable from normal UI (settings, about, or credits). If you rebuild or reskin the UI, carry it over. This is what we expect of every Basis-based client.
  • Keep third-party notices intact. Basis bundles libraries whose licenses also require attribution, and their notices are part of that screen. If you add dependencies, add their notices too.
  • If you redistribute source, keep LICENSE at the repository root and leave existing copyright headers intact.
  • You may add your own copyright notice for your changes. You may not remove ours.

Non-compliance

The rights MIT grants you are conditional on preserving the notice. If you distribute Basis without it, you are not licensed to distribute it at all. That is copyright infringement, no matter how heavily you've modified Basis or how the notice went missing.

When we find a non-compliant distribution, we will contact you and expect the notice restored in a prompt update.

Please be advised that omitting copyright notices can entitle not just Basis but the authors of any bundled library that requires attribution to file takedown notices against your project. Stripping license notices is not a gray area.

Questions about compliance? Reach out to dooly or yewnyx on our Discord.