We as members, contributors and maintainers pledge to make participation in the WSL Container Manager project 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, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive and healthy community.
Examples of behaviour that contributes to a positive environment:
- Being kind to people who are new. Nobody is born knowing Deno, Win32 FFI, or the difference
between
4Gand4GBin a.wslconfig. Someone asking an obvious question is someone who cared enough to ask. - Demonstrating empathy toward other people.
- Being respectful of differing opinions, viewpoints and experiences.
- Giving and gracefully accepting constructive feedback. Reviews in this project ask direct,
technical questions — "which CLI verb backs this?", "what happens without
wslc?". That directness is about the code, never about the person. Offer it that way, and read it that way. - Accepting responsibility, apologising to those affected by our mistakes, and learning from the experience.
- Focusing on what is best for the community and for the people who use this software.
Examples of unacceptable behaviour:
- 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.
- Publishing others' private information — a physical or email address, for instance — without their explicit permission.
- Dismissing or belittling someone for their level of experience, their operating system, their toolchain, or their English.
- Other conduct which could reasonably be considered inappropriate in a professional setting.
This project has strong opinions and states them plainly. It refuses to invent commands. It insists on two typechecks. It will not show you a number it could not measure.
Disagreeing with those opinions is welcome and is not a conduct issue. Argue the technical
case — bring the --help output, bring the failing test, bring the reasoning. That is how the
volume feature got fixed: a previous revision's claim that "wslc documents no volume-create
verb" turned out to be flatly wrong, and someone checking the binary rather than trusting the
comment is what corrected it.
What is a conduct issue is making it personal, being contemptuous about someone's setup or skill level, or wearing people down through persistence rather than convincing them through argument.
Be hard on the problem, easy on the person.
Project maintainers are responsible for clarifying and enforcing our standards of acceptable behaviour, and will take appropriate and fair corrective action in response to any behaviour they deem inappropriate, threatening, offensive or harmful.
Maintainers have the right and responsibility to remove, edit or reject comments, commits, code, wiki edits, issues and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces — the GitHub repository, its issues, pull requests, discussions and reviews — and also applies when an individual is officially representing the project in public spaces.
Instances of abusive, harassing or otherwise unacceptable behaviour may be reported to the maintainers at:
All complaints will be reviewed and investigated promptly and fairly. All maintainers are obligated to respect the privacy and security of the reporter of any incident.
If your report concerns a maintainer, and you would rather not send it to that person, say so in the report and it will be handled by someone else where the project's size allows.
Maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community impact — use of inappropriate language, or other behaviour deemed unprofessional or unwelcome.
Consequence — a private, written warning from the maintainers, providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested.
Community impact — a violation through a single incident or series of actions.
Consequence — a warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community impact — a serious violation of community standards, including sustained inappropriate behaviour.
Consequence — a temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
Community impact — demonstrating a pattern of violation of community standards, including sustained inappropriate behaviour, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence — a permanent ban from any sort of public interaction within the community.
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.