How We Vibe — Community Code of Conduct

Asking for help (Discord and chat)

Questions are welcome. At the same time, members are expected to do their own legwork first: read docs and error messages, search the web, check issues and forums for your tools, and try small experiments. Please do not treat the community as a substitute for research—exhaust other reasonable venues before posting a vague or “do it for me” ask.

When you do ask, share what you tried, what you expected, and what happened instead. That keeps responses fast, kind, and useful for the next person who reads the thread. The home page covers this under Questions welcome—effort expected and How to ask a question (goal, stuck point, what you tried, smallest useful signal).

Our standards

We are building a space that is:

Examples of behaviour that contributes to a positive environment include:

Examples of unacceptable behaviour include:

Beginners and “vibecoding”

How We Vibe is intentionally friendly to people who are just starting out. There are no stupid questions—only questions that skip the basics everyone is expected to try first. Experienced members are asked to explain, link resources, and celebrate small wins—not to gatekeep tools, stacks, or definitions of “real” coding. Beginners are asked to meet us halfway with curiosity and a bit of homework before opening a thread.

Enforcement

Community moderators (or organisers designated on Discord) may take any action they deem appropriate for misconduct, including warnings, temporary removal from channels, removal from events, or a permanent ban from community spaces. Serious violations may be referred to venue staff or local authorities when relevant.

If you experience or witness behaviour that breaks this Code of Conduct, please contact the moderation team on Discord (use the channel or process announced there), or email conduct@howwevibe.example. Reports will be handled with discretion; we will not retaliate against good-faith reporting.

Scope

This policy applies when you are participating in How We Vibe spaces or representing the community in public (for example, as a speaker or organiser). It does not cover private disputes unrelated to the community, though patterns of harm may still be considered if they spill into our spaces.

Attribution and changes

This text was written for How We Vibe and draws on common practices from open-source and meetup communities (including ideas similar to the Contributor Covenant), adapted for a casual coding community rather than a software repository.

We may update this document as the community grows. Material changes will be announced in Discord and reflected by the “Last updated” date above.