Legal

Trademarks

Guidelines for using Xeno ES project names and logos.

Ownership

The following names and their associated logos are trademarks of Xeno ES (Xeno Enterprise Systems), a division of Xeno Interactions:

  • Abora
  • Beta OS
  • Xeno ES / Xeno Enterprise Systems
  • Xeno Tech (shorthand for Xeno ES)
  • Xeno Interactions

Project Logos

Abora logo

Abora

The Abora name and logo represent the Abora Linux operating system.

Beta OS logo

Beta OS

The Beta OS name and logo represent the Beta OS educational Linux distribution.

Calgamij logo

Calgamij

The Calgamij name and logo represent the Calgamij desktop environment.

Permitted Use

You may use the project names and logos in the following ways:

  • Referring to the projects -- e.g. "This guide covers installing Abora" or "Built for Beta OS."
  • Reviews and commentary -- articles, blog posts, videos, and educational content about the projects.
  • Community content -- forum posts, tutorials, and social media discussion about the projects.
  • Unmodified redistribution -- sharing official ISO images or source code with proper attribution.

Restricted Use

You may not use the trademarks in ways that:

  • Imply endorsement, sponsorship, or official affiliation with Xeno ES without permission
  • Use the names or logos for modified distributions without clearly indicating the modifications
  • Incorporate the trademarks into your own product names, company names, or domain names
  • Use the logos in a way that alters their proportions, colors, or overall appearance
  • Use the trademarks in any misleading, defamatory, or illegal context

Modified Distributions

If you create a modified version of Abora, Beta OS, or Calgamij (which the GPL-3.0 license allows), you must use a different name and logo for your derivative. You may state that your project is "based on Abora" or "derived from Beta OS" for clarity, but you may not use the original names or logos as your own.

Questions

If you are unsure whether your intended use is permitted, please reach out through our project's community channels or open an issue on the relevant repository. We are happy to clarify.