This code applies to everyone who takes part in OpenVibe's developer spaces: the OpenVibers repositories on GitHub (issues, pull requests, discussions, reviews), OpenVibe.Codes, and any chat or call about building on OpenVibe. The products themselves (Live, Chat, Community and the rest) have their own rules for viewers and streamers; this code is about how we work together on the platform and the apps built on it.
What we expect
- Be respectful. Disagree with ideas, not with people. Assume the other person is acting in good faith until they show otherwise.
- Be clear and specific. Say what you saw, what you expected and what you propose. A short, concrete report helps more than a long complaint.
- Accept review. Code review is about the change, not about you. Reviewers explain what needs to change and why.
- Credit other people's work. Say where code, ideas or text came from, and respect their licenses.
- Keep secrets and personal data out of public places. Never post credentials, tokens, private keys or someone else's personal information in an issue, a pull request or a log.
- Report security problems privately (see Contributing), not in a public issue.
What is not acceptable
- Harassment, threats or intimidation, in public or in private messages.
- Insults, slurs or demeaning comments about a person or a group, including about gender, sexual orientation, disability, ethnicity, nationality, religion, age, appearance or experience level.
- Sexual content or attention that is not welcome, and any sexual content involving minors.
- Publishing someone's private information (doxxing), or threatening to.
- Deliberately disrupting discussions, reviews or releases, or repeatedly pushing a point after a maintainer has asked you to stop.
- Using OpenVibe's developer tools to attack other developers, users or services, for example publishing a release that is designed to harm the people who install it.
Reporting
If someone breaks this code, or you are not sure whether something is acceptable, tell the maintainers privately at [email protected]. Include links or screenshots if you have them. You do not need to have been the target to report.
Reports are read by the maintainers and kept confidential. Nobody who reports in good faith will be punished for it. If the report is about a maintainer, that maintainer takes no part in handling it.
What happens next
Maintainers decide what to do based on what happened, its impact and whether it has happened before. The steps, from mildest to most serious, are described in the moderation policy:
- A private note explaining what was wrong.
- A public or private warning, with a time-limited restriction if needed (for example, no comments on one issue for a week).
- A temporary ban from the repositories and developer spaces.
- A permanent ban.
Threats of violence, sexual content involving minors and doxxing may lead straight to a permanent ban and, where the law requires it, a report to the authorities.
You can ask for a decision to be reviewed; the moderation policy explains how.
Open questions for the owner
- Confirm the reporting address (the draft uses [email protected]) or name another one.
- Decide whether to adopt a published code (for example the Contributor Covenant) instead of this text.