In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, 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.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information without explicit permission
As a student-focused learning community, we strive to empower learners while avoiding dependency. Here's how we balance helping with fostering independence:
- Providing hints and guidance rather than complete solutions
- Explaining concepts and pointing to documentation
- Asking questions that lead to discovery ("Have you considered...?")
- Sharing resources for learning the fundamentals
- Pair programming where both participants contribute
- Giving complete code solutions to assignments
- Doing the work for someone else
- Providing answers without explanation of the process
- Creating dependencies on specific individuals
- Undermining the learning process by shortcutting challenges
Remember: The goal is learning, not just completion. We celebrate the journey of discovery and growth.
In our educational environment, feedback is a gift that helps us all grow. We prioritize feedback that is specific, actionable, and kind.
- Be Specific: Reference exact code, behavior, or content rather than generalizations
- Be Actionable: Suggest concrete improvements or next steps
- Be Kind: Assume good intent and focus on the work, not the person
- Be Timely: Provide feedback when it can be most helpful
- Be Respectful: Consider the skill level and context of the recipient
- "Consider refactoring this function to be more testable by separating concerns"
- "The variable name could be more descriptive to improve code readability"
- "Have you thought about edge cases like empty inputs or null values?"
- "This approach works, but you might explore using the built-in method for better performance"
- Vague criticisms like "this is bad" or "this is wrong"
- Personal attacks or questioning someone's competence
- Feedback without suggestions for improvement
- Public criticism that could embarrass or discourage
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.