Our purpose

KODE Ń VIBE should be a place where developers in Kenya and beyond can ask honest questions, share unfinished work and disagree about technical choices without being humiliated or targeted. Experience, education, county, language, device access and employment status do not determine whether someone deserves basic respect.

Where this code applies

This code applies to participation in KODE Ń VIBE's website features and public repository, and when someone officially represents the community in another space. It covers text, code, project links, issue comments, reviews, images and other contributions.

The current website is a static prototype. Some community-looking interactions remain only in the user's browser and do not reach a moderation system. Public reports can use GitHub; private concerns can use the published community email.

Expected behaviour

  • Give feedback that is specific, actionable and proportionate to the person's request.
  • Ask before rewriting someone else's work or moving a conversation to a different channel.
  • Credit collaborators, tutorials, libraries, datasets and prior art.
  • Respect names, pronouns, accessibility needs and reasonable communication boundaries.
  • Use plain language where possible and explain unavoidable jargon.
  • Correct mistakes openly and accept a clear “no” without pressure.
  • Protect credentials, personal data and confidential employer or client information.

Unacceptable behaviour

The following is not welcome:

  • harassment, threats, stalking, intimidation or sustained unwanted contact;
  • discrimination or demeaning remarks based on identity, origin, disability, age, education, economic situation or experience level;
  • sexual attention, sexualised content or sharing private material without consent;
  • doxxing, publishing personal data, or pressuring someone to reveal private identity or financial details;
  • impersonation, plagiarism, fabricated credentials or misleading claims of partnership;
  • malware, credential theft, spam, scams, exploit links or instructions aimed at systems without authorisation;
  • retaliation against someone who raises a concern in good faith.

Share projects responsibly

Only share a project, asset or dataset that you have permission to publish. Describe your own contribution accurately. Do not expose API keys, private repositories, client material, production credentials or personal records in a demo.

For critique, distinguish a defect from a preference. “The label is not connected to the input” is testable; “this design is bad” is not useful. If you discover a security weakness, avoid public exploit details and follow the reporting guidance below.

Reporting a concern

Email kodenvibe@gmail.com with the relevant URL, what happened, when it happened and the outcome you are requesting.

Keep the report private. Include only the information needed to explain the concern. Never send passwords, OTPs, identity documents or unnecessary sensitive records.

If there is an immediate threat to someone's safety, use the appropriate local emergency service or the safety tools of the platform where the incident occurred. KODE Ń VIBE reporting is not an emergency-response channel.

How concerns may be handled

Where the relevant controls exist, maintainers may ask for clarification, edit or remove content, close a thread, reject a contribution, restrict participation, or refer conduct to the platform hosting it. The response should consider severity, evidence, pattern, impact and willingness to repair harm.

This prototype does not promise a response time, confidential case system, appeal panel or technical ability to enforce every measure. Before live community submissions launch, KODE Ń VIBE should publish named moderation responsibility, retention rules and an appeal process.

Source and updates

This policy is informed by widely used open-community practices, including the Contributor Covenant, and has been written specifically for the present KODE Ń VIBE prototype. It is not presented as an unmodified copy of another code.

Material revisions should update the review date and explain new reporting or enforcement capabilities plainly.