Skip to content

TRADEMARKS.md

Latest commit

 

History

History
53 lines (46 loc) · 3 KB

TRADEMARKS.md

File metadata and controls

53 lines (46 loc) · 3 KB
Raw

PDFOxide Trademark Policy

"PDFOxide" (the product name), "pdf_oxide" (the package/crate name), and any associated PDFOxide logo (the "Marks") are trademarks of Yury Fedoseev (the "Owner"). Common casings and near-variants used on package registries (e.g. PdfOxide, pdfoxide) are treated as the same Marks. The source code is open source under MIT OR Apache-2.0; the Marks are not. Owning the code license does not grant any right to use the Marks.

This policy exists so users can always trust that something called "PDFOxide" (or distributed as the pdf_oxide package) is the genuine project — the open-source license covers the code, this policy covers the name and brand.

You may, without asking

  • State that your product "uses PDFOxide", is "built on PDFOxide", or is "compatible with PDFOxide" — accurate, descriptive references (nominative use). The same applies to the pdf_oxide package name.
  • Use the Marks in blog posts, talks, tutorials, and comparisons, as long as you don't imply endorsement or official status.
  • Redistribute unmodified official releases under their open-source license using the PDFOxide / pdf_oxide name.
  • Package and redistribute the software for a distribution or package manager (e.g. a Linux distro, Homebrew, conda-forge) under the pdf_oxide / PDFOxide name, including the minimal patches needed to build, package, or security-fix it for that platform — provided the result stays functionally equivalent to the corresponding official release and you don't imply it is a different product. Larger functional forks still need a new name.

You may not, without written permission

  • Use the Marks (or a confusingly similar name/logo) as the name of your own product, service, company, app, domain, or social/package-registry account.
  • Use the Marks in a way that suggests your product is official, endorsed by, or affiliated with PDFOxide when it is not.
  • Distribute a modified version under the PDFOxide or pdf_oxide name (fork it under a different name; you keep the code rights under the open-source license, but not the name).
  • Alter the logo, or use the Marks in a way that is misleading, that falsely implies endorsement or affiliation, or that is otherwise unlawful. (Accurate criticism or comparison that names the Marks is fine.)

Forks and derivatives

The open-source license lets you fork and modify the code freely. If you distribute a modified version, please give it a different name and make clear it is not the official PDFOxide. You may still say it is "a fork of PDFOxide" or "derived from PDFOxide".

Questions / permission

For any use not clearly covered above, or to request permission, contact yfedoseev@gmail.com. We aim to be permissive for good-faith community use and strict only about uses that could confuse users about what the genuine project is.

This policy may be updated over time. It does not modify the terms of the open-source code licenses (MIT OR Apache-2.0).