**By using the software and services we provide, you agree to our [Terms of Service](https://photoprism.app/terms), including our [Privacy Policy](https://photoprism.app/privacy) and the following Code of Conduct. It explains the "dos and don’ts" when interacting with other community members.**
Not everyone has experience with Open Source communities and knows what is acceptable. The following guidelines and examples are intended to provide a quick overview in such cases and help avoid the most common pitfalls:
(a) Do not feel entitled to free software, support, or advice, especially if you are not a contributor, [sponsor](https://photoprism.app/membership), or paying customer. Don't ask contributors to report to you and [meet deadlines](https://docs.photoprism.app/developer-guide/code-quality/#go-slow-before-you-go-fast) as if they work for you or owe you something.
(b) Honor **Rule #3**, [read the docs](https://docs.photoprism.app) and [determine the cause of your problem](https://docs.photoprism.app/getting-started/troubleshooting/) before opening invalid bug reports, starting a public "shitstorm", or insulting other community members in our chat rooms. Aside from being annoying for everyone, it also keeps our team from working on features and improvements that users like you are waiting for.
(c) Comments and messages that violate **Rule #1** are generally unacceptable, whether public or private. If you are having a bad day and want to offend someone, please go somewhere else. To avoid embarrassing situations, we also recommend that you wait until the worst is over when you've had too much coffee.
We encourage all community members to resolve problems on their own whenever possible. Serious and persistent violations [may be reported](https://photoprism.app/contact) to us.
In the event of violations such as disrespectful, abusive, harassing, or otherwise unacceptable behavior, these rules will be enforced as necessary to protect everyone's well-being and to ensure that our discussion forums, chat rooms, and other infrastructure can be used as intended.
Initial warnings may be issued in the form of a [snarky comment](https://www.urbandictionary.com/define.php?term=snarky). In serious cases, we will provide a link to this Code of Conduct and make sure offenders don't have to read between the lines.
Getting a simple **\*plonk\***[^1] in response finally signals that we have lost hope and you're being ignored according to **Rule #2**. This old tradition from Usenet days is as time-saving as it is clear. It is not meant in a disrespectful way.
[^1]: \*plonk\* including variants such as "Plonk." stands for the metaphorical sound of a user hitting the bottom of the kill file. It was first used in [Usenet forums](https://en.everybodywiki.com/Plonk_(Usenet)), a worldwide distributed discussion system and precursor to the Web.
