Hackathon Code of Conduct

Standard

The OpenCoven Beta Hackathon is intended to be a focused, respectful environment for builders, testers, maintainers, and newcomers.

Participants must:

• treat people with respect;
• criticize ideas and code rather than people;
• assume good faith while still reporting concrete concerns;
• give credit accurately;
• protect private data and credentials;
• follow maintainer instructions in issues and PRs;
• avoid repetitive mentions, pressure, or review demands;
• disclose conflicts and material reused work;
• keep competition disagreements factual.

Unacceptable conduct

The following is not permitted in Hackathon spaces or event-related activity:

• harassment, threats, stalking, or intimidation;
• discriminatory or demeaning language;
• sexual harassment or unwanted sexual attention;
• doxxing or publishing private information;
• personal attacks;
• deliberate disruption, spam, or review harassment;
• retaliation against a reporter or reviewer;
• plagiarism or false authorship claims;
• fabricated bugs or manipulation of event records;
• public disclosure of unpatched security vulnerabilities;
• malicious code, credential theft, or unauthorized access.

Scope

This Code applies to:

• the event Discord;
• GitHub repositories, issues, PRs, discussions, and reviews;
• demos and livestreams;
• direct messages related to the event;
• public posts made in an official Hackathon capacity;
• interactions with judges, maintainers, and other participants.

Reporting

Report conduct concerns privately to the event administrators or Discord moderation team.

Include only what is necessary:

• what happened;
• when and where it happened;
• relevant links or screenshots;
• people involved;
• immediate safety or confidentiality concerns.

Do not post sensitive conduct reports publicly.

Security vulnerabilities must be reported through the affected repository’s private security process, not through the conduct channel.

Enforcement

Depending on severity and context, the Organizers may:

• issue guidance or a warning;
• remove content;
• restrict channel access;
• require a change in interaction pattern;
• invalidate a bonus claim;
• disqualify an entry;
• remove a participant from the event;
• refer a matter to GitHub, Discord, a provider, or appropriate authorities.

The Organizers should protect reporter privacy where practical and avoid publishing confidential details.

Good-faith technical disagreement

Disagreement about architecture, scope, severity, scoring, or maintainability is not itself misconduct. Participants and reviewers should remain specific, professional, and evidence-based.