// code-of-conduct

The room is safe.
So is the question.

CNSPK is built on one promise: defense in depth, hospitality on top. This Code of Conduct applies to everyone in every CNSPK space — online and in person. Read it once. It's short, it's real, and we enforce it.

$ this is the bharosa we run on · v1.0 · last reviewed 2026

// 01

Our pledge

We — members, contributors, mentors, and organisers of Cloud Native Security Pakistan — pledge to make participation in the chapter a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, religion or sect, sexual identity and orientation, language, or which city your kubectl points at.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. The most valuable question in any room is the first one — we protect the people brave enough to ask it.

// 02

Expected behaviour

Examples of behaviour that builds a healthy CNSPK:

  • Show empathy and kindness toward other people. Assume good faith before you assume malice.
  • Be respectful of differing opinions, viewpoints, and experiences — especially across seniority and background.
  • Give and gracefully accept constructive feedback. Critique the code, the config, or the idea — not the person.
  • Take responsibility, apologise to those affected by our mistakes, and learn from the experience.
  • Focus on what is best not just for us as individuals, but for the overall community.
  • Help newcomers. Answer the basic question without condescension. Everyone was new to kubectl once.
  • Respect people's time: stay on topic, keep self-promotion to where it's welcome, and credit others' work.
// 03

Unacceptable behaviour

The following are not tolerated in any CNSPK space:

  • Sexualised language or imagery, and sexual attention or advances of any kind.
  • Trolling, insulting or derogatory comments, and personal or political attacks.
  • Public or private harassment, including sustained disruption of talks, labs, or discussions.
  • Publishing others' private information — physical or email address, workplace, or private messages — without their explicit permission ("doxxing").
  • Unsolicited direct messages to members you don't know. Ask in the room first. No cold DM recruiting or pitching.
  • Vendor pitches, MLM, "I have a course to sell," and recruiter spam posted outside designated channels.
  • Advocating for, or encouraging, any of the above behaviour.
  • Sharing real exploits, malware, or stolen data against systems you are not authorised to test. Security research stays ethical and legal — responsible disclosure only.
  • Other conduct which could reasonably be considered inappropriate in a professional setting.
// 04

Scope

This Code of Conduct applies within all CNSPK community spaces, and also applies when an individual is officially representing the community in public spaces. CNSPK spaces include — but are not limited to:

  • The WhatsApp community and any future Discord server.
  • The GitHub organisation — issues, pull requests, discussions, and reviews.
  • In-person meetups, labs, CTFs, and workshops.
  • CNCF chapter sessions and any event run under the CNSPK name.
  • Official social accounts (LinkedIn, X, Instagram, YouTube) and the hi@cloudnativesecurity.pk inbox.

Representing the community includes using an official email address, posting via an official social account, or acting as an appointed representative at an online or offline event.

// 05

Enforcement

Community organisers and Discord/WhatsApp moderators are responsible for clarifying and enforcing this Code of Conduct. They will take fair, proportionate corrective action in response to any behaviour they deem inappropriate, threatening, offensive, or harmful — and may remove, edit, or reject contributions that violate it, with an explanation when appropriate.

We follow a clear escalation ladder. The response matches the impact and whether the behaviour is repeated. Organisers may skip straight to a later step for severe or threatening behaviour.

Step 01

Correction

A private, written note from organisers explaining the violation and why it was inappropriate. A public apology may be requested. No lasting mark — most things end here.

Step 02

Warning

A formal warning with consequences for continued behaviour. No interaction with the people involved — including unsolicited contact with moderators — for a set period. Violating these terms escalates further.

Step 03

Timeout / quarantine

A temporary ban from any interaction or public communication with the community for a specified period. No public or private contact with the people involved is allowed during this time. Breaking it leads to a permanent ban.

Step 04

Permanent ban

A permanent ban from any kind of public interaction within the community, for demonstrating a pattern of violation, harassment of an individual, or aggression toward or disparagement of groups of people.

All organisers are obligated to respect the privacy and security of anyone who reports an incident. Organisers who do not follow or enforce this Code in good faith may face temporary or permanent repercussions as determined by other members of the chapter's leadership.

// 06

Reporting

If you experience or witness unacceptable behaviour — or have any other concern — please report it. Reports go to the chapter's conduct contact and are handled confidentially.

Report · confidential

How to report

Email the conduct team. Include what happened, who was involved, when and where, any screenshots or links, and whether you'd like to stay anonymous to the people involved.

conduct@cloudnativesecurity.pk

  • In a live WhatsApp room or Discord server, you can also message a named moderator directly — they can act immediately.
  • If your report involves an organiser or moderator, email the conduct address and ask that the named person be excluded from handling it.
  • We aim to acknowledge every report within 3 working days and will keep you informed of the outcome where appropriate.

We will not name a reporter to the person they reported without consent. Retaliation against anyone who reports in good faith is itself a violation of this Code.

// 07

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, and draws on the CNCF Code of Conduct. The enforcement ladder is based on the Contributor Covenant's Community Impact Guidelines.

CNSPK is affiliated with the Cloud Native Computing Foundation as a recognised chapter; participants in CNCF events are also subject to the CNCF Code of Conduct. For answers to common questions, see the Contributor Covenant FAQ.