We as members, contributors, maintainers, and leaders pledge to make participation in 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, color, 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.
Examples of behavior that contributes to a positive environment for our community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing 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
- Respecting repository policies, licensing terms, intellectual property rights, confidentiality obligations, and data classification requirements
- Using AI-assisted tools responsibly, transparently, and under meaningful human supervision
- Being transparent about the use of AI-assisted tools when project or organizational policies require disclosure
- Reporting security concerns, suspected misuse, ethical concerns, or policy violations through the appropriate channels
Examples of unacceptable behavior include:
- The use of sexualized 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
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Sharing confidential, sensitive, personal, client, project, partner, or company-sensitive information with unauthorized systems, tools, services, or people
- Using repository content for AI training, fine-tuning, evaluation, automated data collection, scraping, crawling, indexing, or bulk extraction in ways that violate applicable licenses, access controls, confidentiality obligations, or other binding agreements
- Submitting pull requests, issues, commits, reviews, comments, or other contributions created by a fully autonomous AI agent without meaningful human review and accountability
- Misrepresenting AI-generated or AI-assisted work as fully human-authored when disclosure is required by project or organizational policy
- Intentionally bypassing security, compliance, governance, repository controls, access controls, or review processes
- Other conduct which could reasonably be considered inappropriate in a professional setting
Contributors may use approved AI-assisted tools where this is allowed by project and organizational policy. AI-assisted work must remain under the control and responsibility of a human contributor.
The following principles apply:
- A human contributor remains responsible for the quality, correctness, security, licensing, and suitability of any contribution, regardless of whether AI was used.
- AI-generated or AI-assisted output must be reviewed before it is submitted.
- Agentic AI may not take autonomous action without supervision, limits, and authorization.
- Every contribution must have an accountable human owner. Automated tools that are configured and operated by a named contributor, such as dependency update or security scanning bots, may open pull requests and issues on that contributor's behalf.
- No contribution may be merged without review and approval by an accountable human. Automated approval of automated contributions is not permitted.
- Contributions from automated systems with no identifiable human owner will be closed, and the associated account, token, or integration may be blocked.
- Deltares contributors must use only AI tools and accounts approved for Deltares work.
- Contributors must not provide confidential, personal, client, project, partner, or company-sensitive information to unauthorized AI tools.
- Contributors must not submit protected third-party material, generated code, or generated content without checking applicable license terms and usage rights.
- Use of AI must be disclosed where required by project or organizational policy, especially for external publications, reports, legal documents, quality documents, audit-relevant material, or substantial generated content.
- Maintainers may ask a contributor to state which parts of a contribution were AI-generated where this is relevant to review, licensing, or provenance.
Requirements above that depend on organizational policy or approved tooling apply to Deltares employees and contracted partners. All contributors, internal and external, are bound by the requirements on human accountability, review before submission, confidentiality, licensing, and disclosure.
AI can support contributors, but it does not replace professional judgment, review, responsibility, or accountability.
Repository content may not be used for training, fine-tuning, evaluating, benchmarking, or improving machine learning or artificial intelligence models without explicit written permission from Deltares.
Automated scraping, crawling, indexing, mirroring, bulk extraction, or automated collection of repository content for AI, data mining, commercial reuse, or dataset creation is not permitted unless explicitly authorized.
This restriction applies to source code, documentation, issues, discussions, pull requests, comments, wiki content, metadata, and other repository material.
This section does not limit or withdraw any right granted under the license that applies to a given repository or to this Code of Conduct. Where the two differ, the applicable license governs.
Users, contributors, organizations, bots, crawlers, and automated systems must respect repository access controls, licensing terms, copyright, confidentiality obligations, security requirements, and applicable metadata or policy notices.
Community leaders and repository maintainers are responsible for clarifying and enforcing our standards of acceptable behavior. They will take appropriate and fair corrective action in response to behavior that they deem inappropriate, threatening, offensive, harmful, or contrary to this Code of Conduct.
Community leaders and repository maintainers have the right and responsibility to remove, edit, reject, close, or block comments, commits, code, wiki edits, issues, pull requests, reviews, discussions, automated activity, and other contributions that are not aligned to this Code of Conduct.
Where appropriate, they will communicate reasons for moderation or enforcement decisions.
This Code of Conduct applies within all community and repository spaces.
This includes, but is not limited to:
- Repositories
- Issues
- Pull requests
- Discussions
- Code reviews
- Wiki pages
- Documentation
- Releases
- Project boards
- Chat channels and other collaboration spaces connected to the project
This Code of Conduct also applies when an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address, posting via an official social media account, presenting at an online or offline event, or acting as an appointed representative of the project or organization.
The provisions on responsible AI use, automated access, crawling, scraping, and AI training apply to both human users and automated systems interacting with repository content.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at github-owners@deltares.nl. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. 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.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
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.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, 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.
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.
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.