Skip to content

pyde-net/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Code of Conduct

Our pledge

We as members, contributors, and leaders pledge to make participation in the Pyde 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, caste, color, 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.

Our standards

Examples of behaviour that contributes to a positive environment:

  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologising to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behaviour:

  • The use of sexualized 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, such as a physical or email address, without their explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Engineering-specific conduct

Pyde is a technical project with strong engineering opinions. The following are explicitly acceptable and not violations of this policy, even when they may feel uncomfortable:

  • Direct technical criticism of code, design, or arguments (we prefer honest pushback over polite avoidance)
  • Disagreement with proposals, including PIPs, where the disagreement is substantive and technical
  • Asking contributors to justify design decisions with evidence
  • Pointing out engineering anti-patterns, hardening gaps, or performance problems

What separates technical critique from a CoC violation is the target and intent: critique the work, not the person; aim to improve, not to dominate.

Enforcement responsibilities

Project maintainers are responsible for clarifying and enforcing this Code of Conduct. They will take appropriate and fair corrective action in response to any behaviour they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies within all community spaces — issue trackers, PR threads, PIP discussions, project Discord/Slack (when they exist), real-life events held under the Pyde banner — and also applies when an individual is officially representing the project in public spaces.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported to the project maintainers at conduct@pyde.network (or info@pyde.network). 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.

Enforcement guidelines

Maintainers will follow these guidelines in determining consequences for violations:

1. Correction

Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome.

Consequence: A private, written warning, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved for a specified period. This includes avoiding interactions in community spaces as well as external channels. Violating these terms may lead to a temporary or permanent ban.

3. Temporary ban

Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any interaction or public communication with the community for a specified period. No public or private interaction with the people involved is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent ban

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.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at contributor-covenant.org/version/2/1.

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 contributor-covenant.org/faq.

About

Org-default community files for pyde-net — landing page, contribution guide, security policy, code of conduct

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors