Code of conduct
Français · Reference · Published, partly reviewed by a person · Applies from: 4.2.5
The rule everyone follows in the project's spaces: issues, pull requests, discussions, reviews. The repository's
CODE_OF_CONDUCT.md is the English text; this page is its reference in both languages.
Audience, context, and the statuses of what this page rests on
Audience: player, admin, author, contributor · Context: engine repository
What is expected
quest'n'click is a small project with one maintainer. Everyone who opens an issue, a pull request or a discussion is expected to be respectful:
- no harassment;
- no insults;
- no discrimination;
- no publishing of someone else's private information.
Disagreement is welcome when it is about the code, the content or the decision, and stays polite.
Reporting a breach
One channel, private: the repository's report form, the Security tab, Report a vulnerability (https://github.com/wanoo/quest-n-click/security/advisories/new). It is meant for vulnerabilities, but only the maintainer sees what you write there, so it takes a conduct report too: say in its title that it is one. Any GitHub account can use it, a collaborator or not. Reports are read, answered, and kept private.
Limit ·
no-report-addressThe project publishes no email address for reports, and GitHub has no private messages between accounts. If the Security tab offers no "Report a vulnerability" button, open an issue that says only "I need a private channel for a conduct report", with no detail: the maintainer opens a private advisory and adds you to it.
What follows a breach
- A first breach gets a warning.
- A repeated or serious one gets a ban from the project's spaces.
- The maintainer's own conduct is held to the same rule: tell them.
Where it comes from
This is a short, specific version of the Contributor Covenant 2.1 idea, written for a project this size.
Related identifiers
- Security policy (vulnerabilities go there, not here).
- Governance, Welcome.