Contents

• Code of Conduct
  • Our Pledge
  • Where This Applies
  • Our Standards
  • Responsible Disclosure Is Not a Conduct Violation
  • Enforcement Responsibilities
  • Reporting
  • Enforcement Guidelines
    • 1. Correction
    • 2. Warning
    • 3. Temporary Ban
    • 4. Permanent Ban
  • Attribution

Code of Conduct

Our Pledge

We as members, contributors, and maintainers of pg_vault_tde pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, colour, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Where This Applies

This Code of Conduct applies to every space the project uses, and to anyone taking part in them: this GitHub repository (issues, pull requests, code review, discussions, commit messages, and security advisories), the project wiki, project mailing threads, and any conference talk, workshop, or chat channel where someone is representing pg_vault_tde.

It applies equally to external contributors and to Miriade employees working on the project. Being a maintainer, a sponsor, or a long-standing contributor grants no exemption — if anything, it raises the standard we are held to.

Note that the canonical repository is mirrored internally (see CONTRIBUTING.md); conduct in the internal review process is covered by this document just as public conduct is.

Our Standards

Examples of behaviour that contributes to a positive environment:

• Being respectful of differing opinions, viewpoints, and experiences.
• Being considerate: your work is used by others, and their work matters to you.
• Giving and gracefully accepting constructive feedback. Review the code, not the person — “this function leaks the DEK on the error path” is useful; “you clearly don’t understand crypto” is not.
• Being direct without being unkind. Technical disagreement is expected and welcome; a database encryption extension is not improved by people who feel unable to say “I think this is wrong.”
• Assuming good faith. Most misunderstandings on a project spanning several languages and time zones are misunderstandings, not malice. Ask before you conclude.
• Accepting responsibility, apologising to those affected by our mistakes, and learning from the experience.
• Focusing on what is best not just for us as individuals, but for the overall community and the users who run this software in production.

Examples of unacceptable behaviour:

• The use of sexualised language or imagery, and sexual attention or advances of any kind.
• Trolling, insulting or derogatory comments, and personal or political attacks.
• Public or private harassment, including sustained disruption of discussion.
• Publishing others' private information, such as a physical or email address, without their explicit permission.
• Dismissing or belittling a contributor on the basis of their experience level, their employer, their English fluency, or the tooling they use.
• Deliberately misgendering someone, or persistently using a name they have asked not to be called.
• Advocating for, or encouraging, any of the above.
• Other conduct which could reasonably be considered inappropriate in a professional setting.

Responsible Disclosure Is Not a Conduct Violation

Reporting a security flaw in good faith through the channels described in SECURITY.md is welcome and protected, however uncomfortable the finding is for the maintainers. Publicly disclosing an unfixed vulnerability before the coordinated date, on the other hand, endangers users and will be treated as a conduct matter as well as a security one.

Enforcement Responsibilities

Project maintainers are responsible for clarifying and enforcing our standards of acceptable behaviour, and will take appropriate and fair corrective action in response to any behaviour they deem inappropriate, threatening, offensive, or harmful.

Maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Reporting

If you experience or witness unacceptable behaviour, or have any other concerns, report it to the maintainers at supportodb@miriade.it with pg_vault_tde conduct in the subject line.

Include what happened, where, when, and links if the incident is on GitHub. You do not need to have the whole picture, and you do not need to be the target of the behaviour to report it.

All complaints will be reviewed and investigated promptly and fairly. All maintainers are obliged to respect the privacy and security of the reporter of any incident. Reports are shared only with those who need them to resolve the matter; if a report concerns a maintainer, that maintainer is excluded from handling it.

We aim to acknowledge a report within 3 working days and to reach an outcome within 15 working days, telling the reporter what action was taken.

Retaliation against anyone who reports in good faith is itself a violation of this Code of Conduct, and is treated as a serious one.

Enforcement Guidelines

Maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from maintainers, providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behaviour.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html, and is used under the Creative Commons Attribution 4.0 International licence.

It also draws on the PostgreSQL Code of Conduct, whose emphasis on respectful, professional technical disagreement we have tried to carry over — this project is part of the PostgreSQL community and holds itself to that community’s standards.

Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.