# Trademark policy

The names **revl** and **truc**, and the revl logo (`assets/logo.svg`,
`assets/banner.svg`), are trademarks of Thomas
Moussajee. They are not registered; the claim is by use. The software licenses
in this repository ([LICENSING.md](LICENSING.md)) grant copyright permissions
only. They grant no right to the names or the logo.

The point of this policy is short: you may fork the code, you may not fork the
name. Someone who picks up a project called "revl" should get this project, or
something this project stands behind.

## You may, without asking

- Use the name to refer to this project, its compiler, its gate, or its
  language, truthfully: "written in revl", "checked by the revl gate",
  "targets revl 2.0", "a revl backend for X".
- Redistribute unmodified releases of revl under the name revl, including
  through package registries, as long as the release is the one published here.
- Describe a fork or derivative as "a fork of revl" or "based on revl", provided
  your product, package, binary, service and repository carry a different name
  and do not use the logo.
- Write, teach, review, benchmark or criticise revl by name.
- Use "revl" in a compatibility claim for a tool you built, as long as the tool
  is not itself named revl and the claim is accurate.

## You may not, without written permission

- Name a modified version, a fork, a hosted service, a product, a company, a
  domain, a package on any registry, or a model or agent product "revl", "truc",
  or anything confusingly similar ("revl-pro", "revlang", "revl.ai", "rvl gate").
- Use the revl logo for anything that is not this project.
- Present a modified compiler or gate as revl, or imply that a verdict from a
  modified gate is a revl verdict.
- Imply endorsement, affiliation or certification by this project.

A published conformance result (`docs/conformance.md`, `tools/conformance_cert.py`)
is the only thing this project certifies. "Conformant with revl" may be claimed
only for a result produced by the unmodified certification tooling.

## Asking

Open an issue titled "trademark:" on <https://github.com/inso1337/revl/issues>
describing the intended use. Permission, when given, is for the use described
and can be withdrawn if the use changes.

## Relation to the licenses

Nothing here narrows what the AGPL-3.0 or the MIT license lets you do with the
code. You can exercise every right those licenses grant under a name of your
own.