Trademark policy
The MIT licence covers the code. The Spark name, the wordmark and the symbol are not part of that grant. This page is the short version of the rule: keep the mark pointing at this project, and a fork keeps its own identity.
You may, without asking
- Refer to Spark by name, link to this site or the repository, and write about it.
- Say that your project is “built on Spark”, “works with Spark” or “compatible with Spark”, as long as it is true.
- Use screenshots of the app in articles, reviews, documentation and talks.
- Fork the code, modify it and run or share it privately.
- Keep the logo inside an unmodified copy of the app, exactly as distributed here.
You may not
- Present a fork, a build or a service as the official Spark, or imply that it is endorsed by this project.
- Use the Spark name or logo as the icon, name or branding of your own application.
- Use the mark in a way that suggests a certification, an audit or a guarantee that does not exist.
- Register the name or a confusingly similar mark as a trademark, a domain or a package name.
If you distribute a fork
Pick another name and another icon, and say clearly what it is based on — for example “Acme, a fork of Spark”. The MIT licence already requires you to keep the copyright notice; this is the same idea applied to the name.
No certified seal
Spark checks the SHA-256 of a package archive before extracting it. It does not verify a signature, and it does not audit the code of a community extension. Nothing on this site, and no badge in the app, should be read as “certified”. A community package is code you chose to trust.
Questions
Open an issue on the repository and describe the use. Small, non-commercial references are almost always fine.