Get in touch

Before you write

Two places answer most things faster than a person can: the guide, which covers every screen and setting, and the questions people ask, which covers the rest. Inside the app, Help holds the same words, and its search finds them.

What makes a bug report useful

The more of this a report carries, the sooner it can be fixed:

• What you did, what you expected, and what happened instead.
• Your system and the version of Tessera, which About shows.
• The pack or file it happened with, if it was one in particular.
• Anything the log says at that moment. Settings, Privacy and problems, opens it.

Help, then Report a problem, inside the app, fills most of that in for you and shows you exactly what it will send before anything leaves your computer.

Ideas, and what is likely

Tessera is written by one person, so it says no to features rather than half-doing them. Ideas are still worth raising: several things in it started as somebody's note in Discussions. What is being worked on, and what has been ruled out for now, is written down in the repository and in the changelog.

When you will hear back

Usually within a few days, sometimes sooner, occasionally longer when life is busy. An issue that nobody has answered has not been ignored: it is in the list, and every one gets read. A security report is looked at first.

Press, licensing and reuse

Tessera is free software under GPL-3.0-or-later: you may write about it, record it, fork it and ship it under the same terms. The screenshots on this site may be used to write about the app, and the assets in them are Kenney's, under CC0. For anything else, write to hello@rejowan.com.

Following along

New versions appear on the changelog and in its RSS feed. The repository carries the code, the issues and the wiki. Nothing needs an account to read.