Skip to content

TRADEMARK.md

Latest commit

 

History

History
74 lines (54 loc) · 3.3 KB

TRADEMARK.md

File metadata and controls

74 lines (54 loc) · 3.3 KB
Raw

VeriWorkly Trademark Policy

Short version: the code is yours under MIT. The name and the logo are not. Fork freely, ship under your own name.

Why this file exists

Our LICENSE is the MIT License, and it covers everything in this repository — source code, document templates, portfolio templates, assets. MIT is a copyright licence. It says nothing about trademarks, and it grants none.

That distinction is easy to miss. People reasonably assume that an MIT repository hands over the whole project including its identity, so this file states the boundary explicitly rather than leaving it to be inferred from a clause that is silent.

What is not covered by the MIT License

  • The name VeriWorkly, and confusingly similar names.
  • The VeriWorkly wordmark and logo, in any colour or arrangement.
  • The veriworkly.com domain and its subdomains.
  • Brand assets in apps/site/public/ and the brand kit: logo files, the icon set built around the mark, and the specific brand colour and type pairings presented as the VeriWorkly identity.

These remain ours. They are not licensed to you, and no permission to use them is implied by your rights in the code.

What you may do without asking

  • Use the code, for anything, including commercially. That is what MIT says and we mean it.
  • Run a fork or a self-hosted instance for yourself, your team, or your users.
  • Say what your project is based on, accurately and descriptively: "a fork of VeriWorkly", "built on VeriWorkly", "compatible with VeriWorkly". Nominative use like this is fine and we welcome it.
  • Write about us — reviews, comparisons, tutorials, criticism. You do not need our permission to name us, and you certainly do not need it to be negative about us.
  • Keep the attribution notice required by the MIT License itself, which is a copyright notice and not a trademark use.

What you need to change if you fork

If you publish, distribute, or host a modified version, please:

  1. Give it a different name. Not "VeriWorkly", and not something a user would confuse with it.
  2. Replace the logo and wordmark with your own.
  3. Do not use our domain or register a confusingly similar one.
  4. Do not imply endorsement. Saying you are built on VeriWorkly is accurate. Saying you are official, endorsed, certified, or partnered is not, unless we have agreed it in writing.

The apps/site/public/ brand assets and the brand kit are the fastest thing to miss when rebranding — they are the files to swap first.

The one thing we actually care about

A user landing on a fork should never be unsure whether they are looking at VeriWorkly. That is the whole point of this policy. Everything above follows from it, and if something you want to do satisfies that test, it is very likely fine.

Asking

If you want to use the name or logo in a way this file does not cover — a conference talk, a integration listing, a partnership — just ask. We are not precious about it, and we would rather say yes to a specific request than have people guess.

Contact: grievance@veriworkly.com

Related

  • LICENSE — the MIT License covering the code and templates.
  • LICENSING.md — what MIT covers here, in detail.
  • CONTRIBUTING.md — including the DCO sign-off we ask for.