LoopX Name And Marks

This is lightweight community guidance for using the LoopX name, logos, and other project identifiers. For practical examples aimed at open-source projects and commercial products, see the Brand Guide For External Use. This page is not legal advice.

The repository does not claim that LoopX or its logos are registered trademarks in any jurisdiction, and this document does not determine a legal owner. Any future registration or ownership statement requires a separate, explicit decision by the relevant legal holder based on jurisdiction and actual use.

Descriptive Use

You may use the LoopX name to identify the project accurately, including:

• discussing, reviewing, teaching, or criticizing LoopX;
• saying that software works with, extends, or is built on LoopX;
• describing a modified distribution as a fork of LoopX, while giving it a distinct primary name;
• linking to the official repository or showing an unmodified project mark to identify the project in that link.

These uses should be truthful and should not imply sponsorship, certification, or endorsement by the LoopX project or its maintainers.

Avoid Confusing Use

Please do not use the LoopX name or marks:

• as the primary name of an unrelated product, company, hosted service, package, domain, or social account;
• in a way that makes a modified distribution look like an official LoopX release;
• with terms such as "official", "certified", or "approved" without explicit maintainer permission;
• in a confusingly similar logo or visual identity that obscures who operates or maintains the offering.

Forks must retain the notices required by the applicable software license and may accurately state their relationship to LoopX. A materially modified distribution should use its own primary name and make the lack of official project endorsement clear.

Copyright License And Project Identity

The Apache License 2.0 grants copyright and patent permissions for the code and documentation subject to its terms. Historical MIT terms are preserved in LICENSE-MIT. Neither software license grants permission to misrepresent the source of a distribution or imply project endorsement.

For a proposed use that may look official, open a GitHub issue before launch. Do not put credentials, private evidence, or embargoed security details in that issue. Ask a maintainer for a private contact path without including the sensitive details.

Changes to this guidance require maintainer review under Governance.