Python Study Guide is an independent, public, collaborative, and multilingual educational project. We want learners and contributors to be able to participate without intimidation, humiliation, discrimination, or harassment.
This code of conduct applies to everyone who interacts with the project, regardless of experience level, role, identity, language, location, or contribution size.
Community members are expected to:
- communicate with patience, respect, and technical honesty;
- welcome questions asked in good faith;
- explain corrections without belittling the person who made a mistake;
- distinguish facts, recommendations, preferences, and uncertainty;
- give constructive feedback focused on the work;
- respect privacy, authorship, licenses, and contribution credit;
- use English, Brazilian Portuguese, or Spanish without treating one language as a measure of intelligence or ability;
- help maintain a learning environment where beginners can make mistakes safely.
The following behavior is not acceptable:
- harassment, threats, intimidation, stalking, or sustained disruption;
- discriminatory, hateful, sexualized, humiliating, or demeaning language or imagery;
- personal attacks, insults, mockery, or hostile gatekeeping;
- publishing or requesting private, confidential, identifying, or proprietary information without permission;
- impersonation, plagiarism, deceptive attribution, or intentional misrepresentation of another person's work;
- pressuring someone to disclose personal information, credentials, employment details, or private project material;
- knowingly submitting malicious code, unsafe instructions, fabricated evidence, or misleading technical claims;
- retaliation against someone who reports a concern in good faith.
Disagreement is allowed. Disrespect is not.
This policy applies to project spaces and project-related interactions, including:
- issues, pull requests, reviews, commits, and repository discussions;
- project documentation, examples, translations, and code;
- public communication made while representing the project;
- private communication sent specifically to coordinate project work or report conduct concerns.
Do not open a public issue containing private information, harassment details, names of affected people, screenshots, or material that could expose another person.
Use a private contact method published on the maintainer's GitHub profile, when one is available.
If no private contact method is available, open the Private contact request form. The form exists only to establish a private channel. Include no incident details, names, evidence, screenshots, or other sensitive information in the public request.
In the eventual private report, include only what is safe and relevant:
- what happened;
- where and when it happened;
- links, screenshots, or other evidence;
- whether the situation is ongoing;
- any immediate safety or privacy concern.
Reports will be handled as privately as reasonably possible. Absolute confidentiality cannot be guaranteed when information must be shared to investigate, protect someone, or comply with applicable law.
The maintainer may take proportionate action, including:
- a private clarification or correction request;
- removal or editing of harmful content;
- a formal warning;
- temporary participation restrictions;
- permanent removal from project spaces;
- escalation to GitHub or appropriate authorities when necessary.
Decisions should consider context, impact, intent, repetition, cooperation, and the safety of affected people. Good-faith mistakes should normally be addressed through education and correction. Serious or repeated abuse may require immediate restriction.
Good-faith reports will not be punished merely because evidence is incomplete or a violation is not confirmed. Reports made knowingly to harass, retaliate, expose private information, or manipulate moderation may themselves violate this policy.
The maintainer is responsible for applying this policy consistently, documenting significant moderation decisions when appropriate, and avoiding public disclosure of sensitive report details.
Participation in Python Study Guide means agreeing to follow this code of conduct.