Keep to the Code 📜🏴‍☠️¶

This be Plundarr's code of conduct. Around here, the Code be more than guidelines. It be the map, the compass, and the plank avoidin' manual.

The Articles ⚓¶

All hands aboard this repository agree to:

Treat other sailors with respect, patience, and good faith.
Welcome bug reports, questions, pull requests, and tiny cursed config discoveries.
Keep disagreements focused on code, docs, behavior, and reproducible facts.
Help protect secrets, credentials, generated config files, metadata, and private logs.
Remember that everyone starts somewhere, even if that somewhere be face-down in Docker Compose YAML.

Mutiny Most Foul ☠️¶

The following gets tossed overboard:

Harassment, insults, slurs, threats, stalking, or unwanted attention.
Publicly posting private data, secrets, credentials, tokens, or generated configs.
Deliberately wasting maintainer time with spam, bad-faith arguments, or cursed nonsense.
Turning technical disagreement into personal cannon fire.
Encouraging unsafe changes that would expose users, credentials, or networks.

Keep Yer Secrets Below Deck 🧭¶

Plundarr touches credentials and generated config. Do not post real:

Usernames or passwords.
Private keys.
Generated config files.
Live metadata files.
Container logs that contain secrets or network details ye would rather not hand to strangers.

[!WARNING] 🧨 If ye find a security problem, do not open a public issue with exploit details. Follow the security policy and keep the cursed treasure map private.

Enforcement 🪝¶

I, the mostly solo captain of this tiny vessel, may remove comments, close issues, lock threads, block users, or refuse contributions that break the Code.

This is not a court of pirate law with powdered wigs and dramatic candles. It is a small open source repo. Be decent, be clear, and the seas stay friendly.

Attribution 📚¶

This code of conduct is custom for Plundarr, inspired by the general spirit of healthy open source communities and the ancient wisdom: keep to the Code, lest ye meet the plank.