Licence

Every original file in Ubiquitty’s repository is licensed under the Apache License 2.0: the terminal engine, the platform layer and renderers, libubiquittycore, the macOS, iOS, Linux and wscons applications, the host daemon, the ubq agent, the editor clients, the documentation, the tests and the tooling. The licence texts control; each file’s SPDX-License-Identifier header states what applies to it, and the licensing guide explains the policy.

What Apache-2.0 allows

Any use, including in commercial and competing products. Keep the licence and notices (LICENSE, NOTICE), mark the files you modify, and accept the licence’s patent-termination condition. Embedding the engine in a paid application, shipping the renderer in a closed-source app, running the host daemon for other people, or writing your own Sync client or server needs nothing beyond those conditions.

Other licences

• The Emacs client keeps its separate MIT licence.
• The code of conduct is an adaptation of Contributor Covenant 2.1 under CC-BY-4.0.
• Third-party components keep their own licences, listed in third-party-notices.md. Bundled fonts, Unicode data and themes keep their upstream terms.

Name and icon

“Ubiquitty” and its logo and icon are trademarks; the licence grants no rights to them. The trademark policy allows factual references, such as “works with Ubiquitty”, and redistribution of unmodified releases. A fork or a modified build must use a different name and icon; it may say truthfully that it is based on Ubiquitty.

Contributing

You keep copyright in your work and license your original contribution under Apache-2.0, the licence it is distributed under. Record that once per pull request by checking the contribution-terms box in the pull request template, or by posting the statement from the contribution terms. There is no contributor licence agreement, no copyright assignment and no per-commit sign-off.