Code of Conduct¶
← Project README · Contributing · Security policy · Privacy notice · Documentation hub
We as contributors, maintainers, and community members pledge to make participation in European Tech Opportunities 2027 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, socioeconomic 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.
Expected behavior¶
Examples of behavior that contributes to a positive community include:
- demonstrating empathy and kindness toward other people;
- respecting differing opinions, viewpoints, and experiences;
- giving and gracefully accepting constructive feedback;
- accepting responsibility, apologizing to those affected by mistakes, and learning from the experience;
- focusing on what is best for the community and the project;
- respecting the project's safety, source-authorization, privacy, and responsible-operation boundaries.
Unacceptable behavior¶
Examples of unacceptable behavior include:
- sexualized language or imagery, sexual attention, or advances of any kind;
- trolling, insulting or derogatory comments, and personal or political attacks;
- public or private harassment;
- publishing another person's private information without explicit permission;
- pressuring contributors to bypass source policies, authorization interlocks, security controls, or responsible disclosure;
- other conduct that could reasonably be considered inappropriate in a professional setting.
Scope¶
This Code of Conduct applies in all project spaces, including issues, pull requests, reviews, community interactions, and project-related private communication. It also applies when an individual officially represents the project in public spaces.
Reporting conduct issues¶
Report abusive, harassing, or otherwise unacceptable behavior privately to the maintainer at simonesiega1@gmail.com. Include links, dates, context, and supporting material only when safe to do so. Do not collect additional private information or continue an unsafe interaction merely to document it.
Reports will be assessed as fairly and confidentially as reasonably possible. The maintainer will make a reasonable effort to acknowledge a complete report, explain any immediate safety steps, and communicate an outcome; no fixed response-time guarantee is provided. Information may be shared only when needed to investigate, enforce this policy, protect participants, or comply with law.
Good-faith reporters and participants in an investigation must not be retaliated against. Knowingly false or bad-faith reports may themselves violate this Code of Conduct; a report that cannot be substantiated is not, by itself, a false report.
If a report concerns the project maintainer or cannot safely be reported by email, use GitHub's Report Abuse process. Do not send a conduct report through a public issue or pull request.
Note
Security vulnerabilities follow a separate process. Use the Security policy for private vulnerability disclosure.
Enforcement responsibilities¶
Project maintainers are responsible for clarifying and enforcing acceptable behavior. They may remove, edit, or reject comments, commits, code, issues, and other contributions that are inconsistent with this Code of Conduct.
When safe and appropriate, maintainers will communicate the rule involved, the action taken, its duration, and any conditions for return without exposing confidential report details.
Maintainers who receive a report must avoid conflicts of interest, protect confidential information, consider the context and impact of the behavior, document the enforcement rationale privately, and apply proportionate consequences consistently.
A maintainer who is the subject of a report must not make the enforcement decision where another appropriate reviewer is available. Reports concerning the sole maintainer should use GitHub's independent Report Abuse process.
Enforcement guidelines¶
Maintainers will use these Community Impact Guidelines when determining consequences.
1. Correction¶
Community impact: Use of inappropriate language or other behavior considered unprofessional or unwelcome.
Consequence: A private written warning explaining the violation and why the behavior 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 behavior. The individual may have no interaction with the people involved, including unsolicited contact with those enforcing the Code of Conduct, for a specified period. 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 behavior.
Consequence: A temporary ban from interaction or public communication with the community for a specified period. Violating the ban may lead to a permanent ban.
4. Permanent ban¶
Community impact: A pattern of violating community standards, harassment of an individual, aggression toward or disparagement of classes of individuals, or another severe violation.
Consequence: Permanent removal from project community interaction.
Attribution¶
This Code of Conduct is adapted from the Contributor Covenant, version 2.1.
The Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.