Community Code of Conduct

Haptique community spaces exist so people can build, support, test, and improve local-first home experiences together. This code applies in official Haptique spaces, including GitHub repositories, Kitchen registry reviews, support-led community spaces, events, and any other Haptique-managed discussion channel.

Expected Conduct

• Be respectful of different backgrounds, skill levels, languages, locations, and workflows.
• Assume good intent, but accept moderator direction when an interaction is causing harm.
• Keep technical debates focused on the work, not on the person.
• Search existing docs, issues, and discussions before asking for help.
• Share enough context for others to help: product version, device type, logs with secrets removed, and what you already tried.
• Step away when a thread becomes heated.

Serious Violations

Serious violations may lead to immediate removal from official Haptique community spaces.

Harassment

Do not harass, intimidate, stalk, repeatedly target, or shame another person. This includes harmful comments about identity, appearance, disability, race, ethnicity, religion, gender, sexual orientation, age, nationality, or similar personal traits.

Threats

Threats of violence, doxxing, retaliation, or exposure of private information are not allowed.

Hate And Dehumanizing Conduct

Explicit racism, sexism, homophobia, transphobia, ableism, religious hostility, or other dehumanizing conduct is not allowed. Mistakes can happen in normal discussion, but continuing after correction or attacking the person who raised the concern can become a conduct issue.

Sexual Or Exploitative Content

Sexualized images, sexual comments, unwanted romantic attention, or exploitative content are not allowed in Haptique community spaces.

Other Violations

These behaviors may lead to a moderator warning, timeout, content removal, or loss of access. Repeated violations may lead to a ban.

Personal Attacks

Do not insult, mock, belittle, or exclude people. Critique code, design, docs, or behavior directly without attacking the person behind it.

Disruptive Arguments

Do not repeatedly derail threads, reopen settled moderation decisions, or push the same argument after moderators have asked you to stop.

Unwanted Contact

Do not direct-message, tag, or repeatedly ping maintainers, moderators, developers, or community members for general support unless they invited that contact. Use the normal support, issue, or discussion path.

Spam And Self-Promotion

Do not post unrelated promotions, invite links, affiliate links, or repeated promotional content. Sharing a relevant integration, driver, guide, or tool is welcome when it is part of a real contribution to the Haptique community.

Unsafe Or Misleading Guidance

Do not present untested instructions, destructive commands, secret-handling steps, or device-reprovisioning advice as safe. Be clear when something is experimental or unverified.

Private Information

Do not post another person's private information. Do not post your own secrets, license files, tokens, private keys, home addresses, or device credentials in public threads.

Discouraged Conduct

These patterns may not trigger formal enforcement on the first occurrence, but moderators may step in when they harm the community.

• Reposting the same support request across multiple places in a short period.
• Asking others to do all investigation without showing what you tried.
• Treating maintainers or community developers as on-demand support staff.
• Repeatedly campaigning for the same feature after a decision or roadmap answer.
• Turning product feedback into personal criticism.

Reporting

Report conduct concerns through the most direct official channel available for the space where the issue happened.

• GitHub: flag the issue, discussion, pull request, or comment if the repository supports moderation.
• Haptique support: use support.haptique.io for reports that need private handling.
• Security concerns: do not post vulnerability details publicly. Contact Haptique support privately and mark the report as security-sensitive.

Include links, screenshots, timestamps, and usernames when available. Reports will be handled with as much confidentiality as practical.

Enforcement

Moderators and Haptique staff may remove content, ask participants to stop, issue warnings, apply temporary timeouts, close threads, or remove access to official community spaces.

A verified serious violation may result in immediate removal. A verified lower-severity violation usually receives a warning or timeout first, but repeated violations or refusal to follow moderator direction may result in removal.

Moderation decisions are based on the behavior, the surrounding context, prior history, and the risk to the community.

Appeals

If you believe a moderation action was made in error, contact Haptique support with the account name, channel, approximate date, and a brief explanation. Haptique will review the appeal and provide a final decision.

Credits

This policy was written for Haptique and informed by established community moderation patterns, including Obsidian's community code of conduct and the Recurse Center code of conduct.