Tactility/LICENSE.md
Ken Van Hoeylandt 2a2558b29a
Remove old HAL components and refactored GPS-related code (#583)
- Added generic GPS/GNSS support with device detection, configuration, and persistent settings.
- Improved device and module lifecycle management.
- Added flexible filesystem locking support for displays and storage.
- Improved display-idle and keyboard backlight handling.
- Updated architecture, driver, module, testing, and licensing documentation.
- Removed old HAL device and related code.
2026-07-25 17:20:17 +02:00

3.1 KiB

License Grant

Definitions

"external apps" or "external applications" refers to applications that are built with the TactilitySDK. These applications are not part of the Tactility operating system's main firmware.

"end-users" refers to people who install and/or use Tactility software on their devices.

Summary

The main firmware projects (Firmware/, Tactility/) are licensed under GPL v3.0

Most drivers have an Apache License v2.0, with exceptions such as Drivers/gps-generic-module/. Licensing may also differ for subprojects intended for use in external applications.

Specific aren't generally used directly in external app projects, but if they are, make sure to check their licenses.

All projects under Modules/ have an Apache License v2.0.

Overview

Below is an overview of the licenses of some of the subprojects.

Project License
Tactility GNU Public License v3.0
TactilityC Apache License v2.0
TactilityFreeRTOS Apache License v2.0
TactilityKernel Apache License v2.0
Tests GNU Public License v3.0
Devices/* GNU Public License v3.0
Drivers/* (varies)
Modules/* Apache License v2.0
DevicetreeCompiler Apache License v2.0
Platforms/* Apache License v2.0

Subprojects and directories in this project can contain license files.

The presence of such a license file indicates that this license applies to all the files and folders that are contained by the folder at the level where the license file resides.

The Tactility logo copyrights are owned by Ken Van Hoeylandt.

Logo usage is permitted in these scenarios:

  • News, blog posts, articles and documentation that write about the official Tactility project.
  • Firmwares built with unmodified source code from the official repository can be redistributed with the Tactility logo.
  • Personal use for local builds that contain Tactility source code (original or modified), and aren't re-distributed online.

Logo usage is forbidden in all other scenarios unless an exception was granted by the author. For other usages or exceptions, contact me.

Practical examples:

  • A blog post about Tactility can use screenshots and the logo itself when writing about Tactility
  • A developer who forked Tactility to merge new features or fixes to the official Tactility repository is allowed to make builds with the logo, as long as these builds are not re-distributed to end-users.

Third Party Notices

Third-party licenses and copyrights are listed in THIRD-PARTY-NOTICES.md.

FAQ

  • Q: Can I build closed source applications?
  • A: If the applications were built with the Tactility SDK, then they can have a proprietary license. Applications inside the Tactility firmware can't be released with a proprietary license.